SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : LAST MILE TECHNOLOGIES - Let's Discuss Them Here -- Ignore unavailable to you. Want to Upgrade?


To: justone who wrote (9606)12/9/2000 12:31:43 PM
From: Frank A. Coluccio  Respond to of 12823
 
Justone,

The topics and issues you've raised are fascinating (at least to me, since I enjoy delving into historical precedents in these areas), but they ignore several other compelling aspects about the 'Net that are just as important as its roots. And those are, constant innovation and experimentation to push the limits of performance and reach, especially end-to-endness, while maintaining the original precepts that were laid down in several seminal-like doctra over thirty years ago. They also do not do justice to the fact that Ethernet, through 802.xx adaptations and translations, was made a part of public domain some twenty years ago. Although, you do begin to mention the roles that IEEE played in Ethernet's evolution.

Since I'm already late for a lunch appointment, I'll have to return to this later, but I wanted to say thanks for bringing some of these points to the board, and for giving me the opportunity to decide on what is more important: Getting in a post on a topic that I hold near and close, or making it on time for a mostly unwanted (hope no one I know in the 'real world' is reading this) lunch appointment.

Allow me to leave you with some interesting papers that I've posted on the Coluccio board, which speak to all of these issues, and might best be carried forward over there, since, I think that you will agree with me, these topics transcend the last mile. Here is fine too, but I can assure you that it will begin to take excursions into places that have nothing to do uniquely with LM interests.

Message 14978993

FAC



To: justone who wrote (9606)12/9/2000 10:41:33 PM
From: Frank A. Coluccio  Read Replies (1) | Respond to of 12823
 
Hello Justone,

After re-reading your post, perhaps it does belong here, after all.

If you think back to the original thick net (802.5) Ethernet, every station was connected to the "cloud" (actually, to the thick coaxial cable) via an AUI cable and an external transceiver. That is, an attachment unit interface cable that extended to a transceiver device that mounted directly onto the coax through a vampire tap.

The distance limit on this AUI might have been 50 meters, say. Not exactly sure anymore, but that's not important. 50 m sounds about right. Why not 1500 meters? The fact is, however, that it was a short extension from the PC or terminal to the coax, which represented the cloud, and that the station was not a part of the cloud. Rather, it was attached to it.

If I take a form of Ethernet (shared or switched, makes no matter) and extend it to the residence over a twisted pair, or coax, or wireless, or fiber optic link, I have the same thing. The only thing that changes is the relative distance of the attachment, and maybe some sublayers within the physical layer. I can extend this same thinking to a neighborhood hub, or switch for that matter, and make my attachment even shorter. Maybe as short as the one that was originally used on thick coax in the office.

Now, if I want to be completely free to enter this ether at any point on the cloud I can do so. Why not? Are you suggesting that a service order and the installation of a medium to the side of my home, which must necessarily follow, is anti-ethernet?

The fact that it is switched v. shared is another area where I feel it is inconsequential today, especially when we use Layer 3 switching, where we resolve to an IP address that is being advertised by my very own end point (even if I do have to go through a DHCP or a NAT occasionally).

You reach a conclusion, which I can partially agree with, except that I don't think you've followed through all the way on certain issues:

Justone:

"Finally, I can't agree with your point:"

FAC:

"Which, when you look at what a switched port is, is nothing radically different in principle, although the newer ports are backed up with a lot more intelligence and speed, with some of them looking at the upper layers for instructions, to boot..."

Justone:

"It is clear from the above quotes from the 1976 papers, that the authors believed there as a radical difference between shared access and point to point links with switching. I believe this patented difference made Meltcale famous and a multi-millionaire from the royalties."

I almost view this as a non sequitur, except that I think I know where you're coming from. My first impulse is to ask, How could the early pioneers of Ethernet, and the greater 'Net, twenty-five years ago have taken such a negative position as you suggest against switched Ethernet, if switched Ethernet didn't come into play until the Nineties?

Unless, of course, you are drawing an analogy to the PSTN type of switched, which is in another league altogether, and therefore doesn't belong.

BTW, this is one of the reasons I like to view historical readings such as you've presented. The volumetric and timeliness requirements of those laboratory folks at that stage of the Internet's growth were almost quaint by today's standards, wouldn't you agree? Their notions about store and forward, for example? How does this play against today's caching models, where information is not only stored, but updated from time to time, sometimes on cue, to keep it fresh? Another example of how the 'Net is both evolving, on the one hand, and devolving, on the other, at the same time.

And their expectations of what the network could, or should, deliver, were also limited by the developments of the day, just as ours are today.
--------------

I just read a great piece by Judy Estrin (ex-Precept, then ex-Cisco, and now head of Packet Design), btw, where she devotes a part of her interview to the potential evils of MPLS, when it is taken to places where, in her opinion, it oughtn't oughta be. And for some of the same reasons that you have cited, centering on the tensions between switched and end to end, shared. Briefly, she cites how initially MPLS was viewed as a means of reconciling the mapping of ATM and IP to one another, but how since those early days it's been viewed as a panacea for all ills. Great stuff. It's in the January Cook Report on Internet, if you can get your hands on a copy.

FAC



To: justone who wrote (9606)12/10/2000 1:41:50 AM
From: Frank A. Coluccio  Respond to of 12823
 
ps - I initially failed to see what you meant by the following, but after re-reading it, I retract my rebuttal on the bolded part, below:

This salability is the big advantage of shared systems. Unless you design a network for
ubiquitous access, you will probably rollout residences on a almost random basis- you don't
know where you must tap the network until you get the work order. HFC and ethernet do
this well.


As an aside, and if I'm not mistaken, earlier cable TV data systems, what we now call cable modem sytems, actually did use a more compliant form of Ethernet prior to DOCSIS' more recent predecessors, until shortcomings involving classic segmentation rules and the distances involved became more apparent.