Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!sdd.hp.com!hplabs!hpcc01!hpcuhb!hpda!hpcupt1!hpindwa!mtraynor
From: mtraynor@hpindwa.HP.COM (Michael Traynor)
Newsgroups: comp.dcom.lans
Subject: Source Routing Help?
Message-ID: <38470003@hpindwa.HP.COM>
Date: 9 Aug 90 22:46:09 GMT
Organization: Hewlett-Packard, Cupertino CA
Lines: 27

I'm looking for some information on Source Routing on Token Ring networks.
The IBM T/R Archictecture (at least my version) states that the routing
field is up to 18 bytes in length.  Other "standards" indicate a push to go
to 30 byte routing fields.

Does anyone know what the current and future direction is?  Does anyone
really support 30 byte fields?

Also, IBM states that each 2-byte pair in the routing field (except the
header) contains an n-bit bridge identifier and a (16-n)-bit ring
identifier.  Elsewhere, I have seen reference to a 4-bit (n=4) bridge
identifier and a 12-bit ring identifier.

What's the norm?  Is there a standard value for "n"?

Please send repsonses to me directly.

Thank you,

Mike Traynor
------------------------------------------------------------------------------
Information Networks Division		ARPA:    mtraynor@hpindps.cup.hp.com
19420 Homestead Road  MS 43UX		UUCP:    {..}!hplabs!hpindps!mtraynor
 Cupertino, CA 95014			AT&T:    (408) 447-3127
------------------------------------------------------------------------------
Any opinions expressed are my own and not necessarily those of my employer.
------------------------------------------------------------------------------