"Howard C. Berkowitz" wrote:

> >I'm serious. Is there any reason why MPLS cannot be transported directly
on
> >fiber,
> >perhaps even in time slots? Have the GMPLS and IPO WGs addressed this
issue?
> >
> >-- TT
>
> That's exactly what those two working groups are doing, and other
> groups in the IETF sub-IP area are doing for other media such as
> cable TV.  Complementing this is the IEEE 802.17 (IIRC) work on
> resilient packet rings as an alternative to SONET.

Thanks for the reference. I subscribed to the 802.17 list. It's always good
to know
what's happening in the sub-IP areas even if I'm not working with it daily.

> >N.B. That's duct tape, not scotch tape. The author knew his stuff, both
> >white and
> >black. Mr. Waitzman's care in selecting the more robust concatenation
method
> >is
> >appreciated even to this day.
>
> I always wonder if he had generalized to amphibious avian carriers,
> would it instead have been duck tape?

IIRC the RFC does not specifically address the application of the avian
transport system to aquatic environments. However, one could safely
extrapolate to an affirmative answer to your question. I've had lengthy
discussions with individuals in the construction trades who claim that
the original designation of that type of tape was derived from the
sound, which resembles the audible signaling of family Anatidae, produced
when the tape is rapidly separated from the storage medium (spooling
device). In any case, the RFC illustrates the virtually unlimited
adaptability of the Internet and helps us place it in the larger historical
context. There is a logical progression of transport technologies from
avian to electrical to optical. Furthermore, if it is true that history
repeats itself, the RFC has explained not only the past but also the future
of telecommunication.

-- TT




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=42435&t=42214
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to