home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.dcom.lans.misc:705 comp.dcom.lans.ethernet:1789
- Path: sparky!uunet!hayes!croussel
- From: croussel@hayes.com
- Newsgroups: comp.dcom.lans.misc,comp.dcom.lans.ethernet
- Subject: Re: general Token Ring questions
- Message-ID: <5924.2aa1d372@hayes.com>
- Date: 31 Aug 92 08:08:18 EDT
- References: <1992Aug26.140644.14794@msuinfo.cl.msu.edu>
- Organization: Hayes Microcomputer Products, Norcross, GA
- Lines: 41
-
- In article <1992Aug26.140644.14794@msuinfo.cl.msu.edu>, craven@egr.msu.edu (Dean Craven) writes:
- > Hi,
- >
- > I have a few beginners questions about Token Ring.
- >
- > o in general, how do IEEE 802.5 and the IBM Token Ring Architecture Reference
- > differ? Is one a superset of the other, what was/is their evolution, etc?
- >
- 802.5 attempts to track IBM's implementation of token ring, and is still
- evolving. IBM has recently become more actively involved in resolving
- interoperability issues in the 802.5 document.
-
- > o is the definitive description of the token ring frame "Routing Information
- > Field" found in the IBM Token Ring manual or in an ISO/IEEE document?
- > IEEE 802.5 references something called "ISO/IEC DIS 10038" for details of
- > the RI field. What is this document about?
- >
- It depends. There is SR (IBM implemented, not an IEEE standard) and SRT
- (soon to be an IEEE standard). For SR, you must use the IBM TRAR. For
- SRT, the IEEE 802.5, and 802.1 documents.
-
- > o for existing token ring devices, what are common maximum frame sizes?
- In token-ring this is determined by the MaxTokenHoldTime. This works out
- to about 4K for 4M rings, 14K for 16M rings?
-
- >
- > o I have the IBM Token Ring Architecture Reference, IEEE 802.5, IEEE 802.1d,
- > IEEE 802.1m. What other documents should I have to understand token ring
- > and token ring bridging/source routing?
- >
- There is something being drafted now within 802.5 called RDE or "Route
- Determination Entity". It's how the committee wants end stations (PC's)
- to do route discovery in an SRT network. The document number is 802.5P.
-
- > Thanks.
- >
- > Dean Craven (craven@egr.msu.edu)
- --
- Chris Roussel internet: hayes!croussel@uunet.uu.net
- (404) 840-9200 (x.2147) uucp: ...uunet!hayes!croussel
- Hayes Microcomputer Products U.S.Mail: p.o.box 105203, Atlanta, GA 30348
-