🚀 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?
> 
We wrote the 802.1d SRT supplement with the idea that Source Routing would
be supported on FDDI at some point. But it is not currently supported,
meaning that the frame formats for Source Routing are not part of the FDDI
standard. (802 can't make requirements of FDDI, which is ANSI.)


-- 
Rich Seifert                    Networks and Communications Consulting
seifert@netcom.com              (408) 996-0922
                                (408) 996-2860 FAX
"... specialists in Local Area Networks and Data Communications systems"