ISO/IEC 10589:1992/Cor 1:1993
(Corrigendum)Information technology — Telecommunications and information exchange between systems — Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473) — Technical Corrigendum 1
Information technology — Telecommunications and information exchange between systems — Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473) — Technical Corrigendum 1
Amends subclauses 7.1.3, 7.1.3.2, 7.1.4, 7.2.9.2, 7.2.10.3, 7.2.10.4, 7.2.12.4 (renumbered from 7.2.12.3), 7.3.9, 7.3.15.2, 7.4.3.2, 7.4.3.3, 8.2.4 (renumbered from 8.2.3), 8.4.8, 9.9, 11.2.1.1, 11.2.4, 11.2.5.7, 11.2.5.8, adds new subclauses 7.1.3.1, 7.2.12.2, 7.2.12.3, 7.3.4.6, 8.2.3.
Technologies de l'information — Communication de données et échange d'informations entre systèmes — Protocole intra-domaine de routage d'un système intermédiaire à un système intermédiaire à utiliser conjointement avec le protocole fournissant le service de réseau en mode sans connexion (ISO 8473) — Rectificatif technique 1
General Information
Relations
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 10589:1992
TECHNICAL CORRIGENDUM 1
Published 1993-05-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION”MEX~YHAPO~HAR OPTAHM3AUMfl l-lo CTAH~APTl43ALUfWl*ORGANlSATlON INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELE~TROTECHNICAL COMMISSION~ME))~IYHAPOJ~HAR ~~EKTPOTEXHM~ECKAR KOMII~CC~W COMMISSION ~LECTROTE~HNIOUE INTERNATIONALE
Information technology - Telecommunications and
information exchange between systems - Intermediate
system to Intermediate system intra-domain routeing
information exchange protocol for use in conjunction with
the protocol for providing the connectionless-mode Network
Service (IS0 8473)
TECHNICAL CORRIGENDUM 1
Technologies de /‘information - Communication de donnkes et &change d’informations entre syst&mes - Protocole intra-
domaine de routage d’un systhme intermhdiaire & un syst&me intermgdiaire & utiliser conjointement avec le protocole
fournissant le sewice de rbseau en mode sans connexion (IS0 8473)
RECTlFlCATIF TECHNIQUE I
Technical corrigendum 1 to International Standard ISO/IEC 10589:1992 was prepared by Joint Technical Committee lSO/IEC
JTC 1, Information technology.
Page 1 I
Subclause 7.1.3
Add the following paragraph and new subclause 7.1.3.1 before the existing text:
This clause first defines how the NPAI corresponding to NSAP addresses and Network Entity titles of systems deployed
in a routeing domain is constructed and second how the NPAI is structured for use by the protocol.
7.1.3.1 Construction of NPAI from network addresses
NPAI is derived from NSAP addresses and NETS according to lSO/IEC 8348/Add.2. The NETS and NSAP addresses are
obtained from the appropriate addressing authorities.
Ref. No. lSO/IEC 10589:1992/Cor.1:1993 (E)
UDC 681.3521.39
Descriptors : data processing, information interchange, network interconnection, open systems interconnection, telecommunications, data
transmission, network layer, communication procedure, control procedures, protocols.
0 ISO/IEC 1993
Printed in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 10589:1992/Cor.1:1993 (E)
For these addresses to be correctly interpreted by the protocol in this International Standard it is mandatory that the
routeing domain authority ensure that whenever the Network address includes a DSP whose syntax is decimal digits,
then:
- if the IDI is in the IS0 DCC or E.164 format, the decimal syntax DSP must be an odd number of digits;
- for the other IDI formats the decimal syntax DSP must be an even number of decimal digits.
Add new subclause heading 7.1.3.2, followed by the existing text of 7.1.3:
7.1.3.2 Structure of the NPAI
After the existing text of 7.1.3, insert the following note:
guarantee that there will be no pad at the end of
NOTE -The SEL field is always the last octet of the NPAI, since the rules enforced in 7.1.3.1
the NPAI.
Subclause 7.1.4
Add the following text to the end of the first sentence of subclause 7.1.4:
. . . and the rules stated above in 7.1.3.1
Replace the text of NOTE 5 with:
it is necessary to refer to the structure of the NPAI presented in 7.1.1 and 7.1.3.2,
NOTE 5 To interpret correctly the requirements given below,
and to the concept of manual area addresses defined in 7.1.5.
Page 16
Subclause 7.2.9.2
Replace the first paragraph with:
When executing the level 2 decision process for each supported metric, level 2 IS shall ascertain whether or not it can
reach any destinations outside its area using that metric. The IS considers itself attached if either:
a) it can reach at least one other area using the corresponding routeing metric, or
b) it has at least one enabl ed reachable add ress prefix with the corresponding metric defined.
Otherwise the IS considers itself not attached.
If the IS discovers that it is not attached and attachedFlag was previously True, it shall:
Replace the paragraph immediately below NOTE 13 with:
If the IS discovers that it is attached and attachedFlag was previously False, it shall:
Page 78
Subclause 7.2.10.3
Add the following paragraph at the beginning of the subclause:
For systems which do not implement partition repair, the value of partitionAreaAddresses is identical to the value
computed for areaAddresses as described in 7.2.11. For systems which do implement partition repair, the value of
partitionAreaAddresses is determined as follows.
Subclause 7.2.10.4
Replace the text of item d) 1) with:
Ensure that the header of the encapsulating PDU indicates routeing by the default metric. Routeing by the default metric
may be indicated either by including a QoS parameter with its bits set in accordance with Table 1, or by carrying no QoS
parameter at all [see 7.4.2 item a)].
Page 19
Add a new subclause between 7.2.12.2 and 7.2.12.3 as follows:
7.2.12.3 If an Intermediate system takes part in level 2 routeing and the IS determines (by looking at the area address)
that the destination is reachable within its area, then the destination will be reached either by level 1 or level 2 routeing,
as follows:
a) level 1 routeing is always based on internal metrics;
---------------------- Page: 2 ----------------------
ISO/IEC 10589:1992/Cor.1:1993 (E)
a level 2 route, if it exists, shall preferred over a level 1 route that traverses a virtual link. Qtherwi se, the level 1
b)
route shall be preferred;
in the area, routes on which the requested QOS i is su pported are a lways preferred to
d amongst routes (f any)
routes on which the req uested QoS is not supported;
d) amongst routes in the area of the same QoS, the shortest routes are preferred. For determination of the shortest
path, if a route with specific QoS support is available, then the specified QoS metric is used, otherwise the default
metric is used.
and renumbe
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.