cmilono@netcom.COM (Carlo Milono) (05/29/91)
HELP! I was the original poster of the NSAP thread. I have gotten many responses, but I finally got one that has me very, very confused. It seems that the CSMA ES and IS addresses have been stable for some time; however, I am dealing with Token Ring and thought I had the problem licked until today. Here are the addresses in question - but there is a *new* standard that has yet to be logged as official...and the addresses have changed! 802.5 ESIS_ES ES address c0.00.00.08.00.00 03.00.00.10.00.00 NIST 1988, MAP/TOP, three vendors c0.00.00.00.40.00 NIST 1990 OSI Workshop (draft???) and cisco 03.00.00.00.02.00 802.5 ESIS_IS IS address c0.00.00.10.00.00 03.00.00.08.00.00 NIST 1988, MAP/TOP, three vendors c0.00.00.00.80.00 03.00.00.00.01.00 NIST 1990 OSI Workshop (draft???) and cisco I also understand that there are other standards bodies involved in Europe that adhere to the NIST 1988 and MAP/TOP agreements...and that the 1990 Workshop stuff is not yet written into the books. Where can I FTP a copy of both the 1988 NIST and 1990 NIST documents...why change addresses? I understand using the least-significant-bit of the MSByte - but these changes/differences are 'in the middle' of the address. Oh, help. Oh, help. -- +--------------------------------------------------------------------------+ | Carlo Milono | | Personal: cmilono@netcom.com or apple!netcom!cmilono | | Hobbes: "Life in the Great Suburban Outback is certainly fraught with | | peril." | | Calvin: "If you'd seen it, you'd have been scared too." | +--------------------------------------------------------------------------+
dougm@WARTHOG.NCSL.NIST.GOV (Doug Montgomery) (05/31/91)
>HELP! I was the original poster of the NSAP thread. I have gotten many >responses, but I finally got one that has me very, very confused. > >It seems that the CSMA ES and IS addresses have been stable for some time; >however, I am dealing with Token Ring and thought I had the problem licked >until today. > >Here are the addresses in question - but there is a *new* standard that has >yet to be logged as official...and the addresses have changed! I'm not sure what *new* standard you are refering too. Within the OIW these addresses have been agreed to for some time. I'm not sure if they are in the TA ISP for token ring, I thought that they were. Below is the relevant text from the OIW stable agreements. dougm +------------------------------------------------------------------------------+ | Doug Montgomery dougm@osi.ncsl.nist.gov | | National Institute of Standards and Technology | | Technology Building, B-217 Voice: +1-301-975-3630 | | Gaithersburg, MD 20899 USA Fax: +1-301-590-0932 | +------------------------------------------------------------------------------+ Part 3 - Network Layer March 1991 (Stable) 12.2.1.4 of ISO 10039; i) The multicast addresses corresponding to "All Intermediate Systems on the Network" (ALL_ISN) and "All End Systems on the Network" (ALL_ESN) shall default to the following on IEEE802.3 and IEEE802.4 subnetworks: 1) ALL_ESN = 09-00-2B-00-00-04, ALL_ISN = 09-00-2B-00- 00-05; 2) It is understood that the hexadecimal octets shown are transmitted onto the medium from left most octet to right most octet. Within each hexadecimal octet the least significant bit is transmitted first; j) The multicast addresses corresponding to "All Intermediate Systems on the Network" (ALL_ISN) and "All End Systems on the Network" (ALL_ESN) shall default to the following two functional addresses on IEEE802.5 subnetworks: 1) ALL_ESN = C000 0000 4000, ALL=ISN - C000 0000 8000; 2) It is understood that the hexadecimal octets shown are transmitted onto the medium from left most octet to right most octet. Within each hexadecimal octet the most significant bit is transmitted first; Editor's Note - Note that in the hexadecimal representation defined in ISO 10039, these addresses would be: 1) ALL_ESN = 03-00-00-00-02-00 2) ALL_ISN = 03-00-00-00-01-00 NOTE - This notation presents the octet values such that the least significant bit is that transmitted first. k) The Error Report flag shall be set to zero (0) for NPDUs sent as a result of invoking the QUERY Configuration Function. l) ISO 8473 PDUs multicast as a result of the Query Configuration function shall use the Network Layer Protocol ID (NLPID) assigned to ISO 8473. m) An ISO 8473 PDU received as a result of another ES having performed the Query Configuration function shall be processed as follows: 12