🚀 go-pugleaf

In article <19921102.120905.916@almaden.ibm.com>, gator@vnet.ibm.com writes:
> In article <1992Oct31.014819.16180@netcom.com>, seifert@netcom.com (Rich
> Seifert) writes:
> 
> > Of course, there will be no connectivity to devices connected to the
> > backbone.  Neither Ethernet nor FDDI devices support source routing.
> > Let's just hope that it won't cause them to crash--The problem area is
> > when someone sends a frame to a multicast (or broadcast) with source
> > routing enabled.  The receiving Ethernet or FDDI station will see a
> > source address with the Routing Information Indicator set to one.  This
> > looks like a multicast source address, which is outlawed in Ethernet.
> 
> While it is a given that Ethernet does not support source routing, I
> beleive FDDI does. I am looking at the Source Routing Supplement to IEEE
> 802.1d (MAC Bridges) (Unapproved Draft) and it mentions SRT operation
> for FDDI several times. Could you please clarify what you mean?


Please notice that ANSI is not IEEE and IEEE is not ANSI.
(Unless your sufficiently cynical to have trouble telling the
difference among standards organizations.)

There is "support" and then there is also "support." Some old versions
of some documents from the ANSI X3T9.5 committee did mention source
routing.

Concretely, I think no stations on the FDDI rings last week at InterOP
sent out any source routed frames that they expected to be handled by
any other stations.


Vernon Schryver,  vjs@sgi.com