draft-ietf-ccamp-rfc5787bis-00.txt   draft-ietf-ccamp-rfc5787bis-01.txt 
INTERNET-DRAFT A. Malis, ed. INTERNET-DRAFT A. Malis, ed.
Intended Status: Proposed Standard Verizon Communications Intended Status: Proposed Standard Verizon Communications
Expires: October 31, 2011 A. Lindem, ed. Expires: November 28, 2011 A. Lindem, ed.
Ericsson Ericsson
April 29, 2011 May 27, 2011
Updates to ASON Routing for OSPFv2 Protocols (RFC 5787bis) Updates to ASON Routing for OSPFv2 Protocols (RFC 5787bis)
draft-ietf-ccamp-rfc5787bis-00.txt draft-ietf-ccamp-rfc5787bis-01.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 2, line 31 skipping to change at page 2, line 31
Note that this work is scoped to the requirements and evaluation Note that this work is scoped to the requirements and evaluation
expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations expressed in RFC 4258 and RFC 4652 and the ITU-T Recommendations
current when those documents were written. Future extensions of current when those documents were written. Future extensions of
revisions of this work may be necessary if the ITU-T Recommendations revisions of this work may be necessary if the ITU-T Recommendations
are revised or if new requirements are introduced into a revision of are revised or if new requirements are introduced into a revision of
RFC 4258. RFC 4258.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions Used in This Document . . . . . . . . . . . . 5 1.1. Conventions Used in This Document . . . . . . . . . . . . 5
2. Routing Areas, OSPF Areas, and Protocol Instances . . . . . . . 5 2. Routing Areas, OSPF Areas, and Protocol Instances . . . . . . 5
3. Terminology and Identification . . . . . . . . . . . . . . . . 6 3. Terminology and Identification . . . . . . . . . . . . . . . . 6
4. Reachability . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Reachability . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Link Attribute . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Link Attribute . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Local Adaptation . . . . . . . . . . . . . . . . . . . . . 7 5.1. Local Adaptation . . . . . . . . . . . . . . . . . . . . . 7
5.2. Bandwidth Accounting . . . . . . . . . . . . . . . . . . . 8 5.2. Bandwidth Accounting . . . . . . . . . . . . . . . . . . . 8
6. Routing Information Scope . . . . . . . . . . . . . . . . . . . 8 6. Routing Information Scope . . . . . . . . . . . . . . . . . . 8
6.1. Link Advertisement (Local and Remote TE Router ID 6.1. Link Advertisement (Local and Remote TE Router ID
Sub-TLV) . . . . . . . . . . . . . . . . . . . . . . . . . 9 Sub-TLV) . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.2. Reachability Advertisement (Local TE Router ID sub-TLV) 10 6.2. Reachability Advertisement (Local TE Router ID sub-TLV) . 10
7. Routing Information Dissemination . . . . . . . . . . . . . . 11 7. Routing Information Dissemination . . . . . . . . . . . . . . 11
7.1 Import/Export Rules . . . . . . . . . . . . . . . . . . . 11 7.1 Import/Export Rules . . . . . . . . . . . . . . . . . . . . 11
7.2 Loop Prevention . . . . . . . . . . . . . . . . . . . . . 11 7.2 Loop Prevention . . . . . . . . . . . . . . . . . . . . . . 11
7.2.1 Inter-RA Export Upward/Downward Sub-TLVs . . . . . . 12 7.2.1 Inter-RA Export Upward/Downward Sub-TLVs . . . . . . . 12
7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing . 13 7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing . . 13
8. OSPFv2 Scalability . . . . . . . . . . . . . . . . . . . . . 13 8. OSPFv2 Scalability . . . . . . . . . . . . . . . . . . . . . . 13
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. Security Considerations . . . . . . . . . . . . . . . . . . . 14
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . 14 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10.1. Sub-TLVs of the Link TLV . . . . . . . . . . . . . . . 14 10.1. Sub-TLVs of the Link TLV . . . . . . . . . . . . . . . . 14
10.2. Sub-TLVs of the Node Attribute TLV . . . . . . . . . . 15 10.2. Sub-TLVs of the Node Attribute TLV . . . . . . . . . . . 15
10.3. Sub-TLVs of the Router Address TLV . . . . . . . . . . 15 10.3. Sub-TLVs of the Router Address TLV . . . . . . . . . . . 15
11. Management Considerations . . . . . . . . . . . . . . . . . 16 11. Management Considerations . . . . . . . . . . . . . . . . . 16
11.1. Routing Area (RA) Isolation . . . . . . . . . . . . . . 16 11.1. Routing Area (RA) Isolation . . . . . . . . . . . . . . . 16
11.2 Routing Area (RA) Topology/Configuration Changes . . . . 16 11.2 Routing Area (RA) Topology/Configuration Changes . . . . . 16
12. Comparison to Requirements in RFC 4258 . . . . . . . . . . . 16 12. Comparison to Requirements in RFC 4258 . . . . . . . . . . . 16
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
13.1. Normative References . . . . . . . . . . . . . . . . . 22 13.1. Normative References . . . . . . . . . . . . . . . . . . 22
13.2. Informative References . . . . . . . . . . . . . . . . 23 13.2. Informative References . . . . . . . . . . . . . . . . . 23
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24
Appendix A. ASON Terminology . . . . . . . . . . . . . . . . . . 25 Appendix A. ASON Terminology . . . . . . . . . . . . . . . . . . 25
Appendix B. ASON Routing Terminology . . . . . . . . . . . . . . 26 Appendix B. ASON Routing Terminology . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
1. Introduction 1. Introduction
The Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] The Generalized Multiprotocol Label Switching (GMPLS) [RFC3945]
protocol suite is designed to provide a control plane for a range of protocol suite is designed to provide a control plane for a range of
network technologies including optical networks such as time division network technologies including optical networks such as time division
multiplexing (TDM) networks including SONET/SDH and Optical Transport multiplexing (TDM) networks including SONET/SDH and Optical Transport
Networks (OTNs), and lambda switching optical networks. Networks (OTNs), and lambda switching optical networks.
The ITU-T defines the architecture of the Automatically Switched The ITU-T defines the architecture of the Automatically Switched
skipping to change at page 9, line 33 skipping to change at page 9, line 33
An OSPF router advertising on behalf of multiple transport nodes will An OSPF router advertising on behalf of multiple transport nodes will
require additional information to distinguish the link endpoints require additional information to distinguish the link endpoints
amongst the subsumed transport nodes. In order to unambiguously amongst the subsumed transport nodes. In order to unambiguously
specify the transport topology, the local and remote transport nodes specify the transport topology, the local and remote transport nodes
MUST be identified by TE router ID. MUST be identified by TE router ID.
For this purpose, a new sub-TLV of the OSPFv2 TE LSA top-level Link For this purpose, a new sub-TLV of the OSPFv2 TE LSA top-level Link
TLV is introduced that defines the Local and Remote TE Router ID. TLV is introduced that defines the Local and Remote TE Router ID.
The Type field of the Local and Remote TE Router ID sub-TLV is The Type field of the Local and Remote TE Router ID sub-TLV is
assigned a value TBD. The Length field takes the value 8. The Value assigned the value 26 (see Section 10). The Length field takes the
field of this sub-TLV contains 4 octets of the Local TE Router value 8. The Value field of this sub-TLV contains 4 octets of the
Identifier followed by 4 octets of the Remote TE Router Identifier. Local TE Router Identifier followed by 4 octets of the Remote TE
The value of the Local and Remote TE Router Identifier SHOULD NOT be Router Identifier. The value of the Local and Remote TE Router
set to 0. Identifier SHOULD NOT be set to 0.
The format of the Local and Remote TE Router ID sub-TLV is: The format of the Local and Remote TE Router ID sub-TLV is:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length (8) | | Type (26) | Length (8) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local TE Router Identifier | | Local TE Router Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remote TE Router Identifier | | Remote TE Router Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This sub-TLV MUST be included as a sub-TLV of the top-level Link TLV This sub-TLV MUST be included as a sub-TLV of the top-level Link TLV
if the OSPF router is advertising on behalf of one or more transport if the OSPF router is advertising on behalf of one or more transport
nodes having TE Router IDs different from the TE Router ID advertised nodes having TE Router IDs different from the TE Router ID advertised
in the Router Address TLV. Therefore, it MUST be included if the in the Router Address TLV. Therefore, it MUST be included if the
skipping to change at page 10, line 26 skipping to change at page 10, line 26
6.2. Reachability Advertisement (Local TE Router ID sub-TLV) 6.2. Reachability Advertisement (Local TE Router ID sub-TLV)
When an OSPF router is advertising on behalf of multiple transport When an OSPF router is advertising on behalf of multiple transport
nodes, the routing protocol MUST be able to associate the advertised nodes, the routing protocol MUST be able to associate the advertised
reachability information with the correct transport node. reachability information with the correct transport node.
For this purpose, a new sub-TLV of the OSPFv2 TE LSA top-level Node For this purpose, a new sub-TLV of the OSPFv2 TE LSA top-level Node
Attribute TLV is introduced. This TLV associates the local prefixes Attribute TLV is introduced. This TLV associates the local prefixes
(see above) to a given transport node identified by TE Router ID. (see above) to a given transport node identified by TE Router ID.
The Type field of the Local TE Router ID sub-TLV is assigned a value The Type field of the Local TE Router ID sub-TLV is assigned the
TBD. The Length field takes the value 4. The Value field of this value 5 (see Section 10). The Length field takes the value 4. The
sub-TLV contains the Local TE Router Identifier [RFC3630] encoded Value field of this sub-TLV contains the Local TE Router Identifier
over 4 octets. [RFC3630] encoded over 4 octets.
The format of the Local TE Router ID sub-TLV is: The format of the Local TE Router ID sub-TLV is:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length (4) | | Type (5) | Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local TE Router Identifier | | Local TE Router Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This sub-TLV MUST be included as a sub-TLV of the top-level Node This sub-TLV MUST be included as a sub-TLV of the top-level Node
Attribute TLV if the OSPF router is advertising on behalf of one or Attribute TLV if the OSPF router is advertising on behalf of one or
more transport nodes having TE Router IDs different from the TE more transport nodes having TE Router IDs different from the TE
Router ID advertised in the Router Address TLV. Therefore, it MUST Router ID advertised in the Router Address TLV. Therefore, it MUST
be included if the OSPF router is advertising on behalf of multiple be included if the OSPF router is advertising on behalf of multiple
transport nodes. transport nodes.
skipping to change at page 12, line 14 skipping to change at page 12, line 14
information upward or downward into an upper or lower level RA in the information upward or downward into an upper or lower level RA in the
ASON hierarchy. For example, without loop prevention mechanisms, this ASON hierarchy. For example, without loop prevention mechanisms, this
could happen when the RC advertising routing information downward in could happen when the RC advertising routing information downward in
the hierarchy is not the same one that advertises routing information the hierarchy is not the same one that advertises routing information
upward in the hierarchy. upward in the hierarchy.
7.2.1 Inter-RA Export Upward/Downward Sub-TLVs 7.2.1 Inter-RA Export Upward/Downward Sub-TLVs
The Inter-RA Export Sub-TLVs can be used to prevent the re- The Inter-RA Export Sub-TLVs can be used to prevent the re-
advertisement of OSPF TE routing information into an RA which advertisement of OSPF TE routing information into an RA which
previously advertised that information. The type value TBD will previously advertised that information. The type value 28 (see
Section 10) will indicate that the associated routing information has
been exported downward. The type value 27 (see Section 10) will
indicate that the associated routing information has been exported indicate that the associated routing information has been exported
downward. The type value TBD will indicate that the associated upward. While it is not required for routing information exported
routing information has been exported upward. While it is not downward, both Sub-TLVs will include the Routing Area (RA) ID from
required for routing information exported downward, both Sub-TLVs the which the routing information was exported. This RA is not
will include the Routing Area (RA) ID from the which the routing necessarily the RA originating the routing information but RA from
information was exported. This RA is not necessarily the RA which the information was immediately exported.
originating the routing information but RA from which the information
was immediately exported.
These additional Sub-TLVs MAY be included in TE LSAs that include any These additional Sub-TLVs MAY be included in TE LSAs that include any
of the following top-level TLVs: of the following top-level TLVs:
- Router Address top-level TLV - Router Address top-level TLV
- Link top-level TLV - Link top-level TLV
- Node Attribute top-level TLV - Node Attribute top-level TLV
The Type field of the Inter-RA Export Upward and Inter-RA Export The Type field of the Inter-RA Export Upward and Inter-RA Export
Downward sub-TLVs are respectively assigned the values TBD1 and TBD2. Downward sub-TLVs are respectively assigned the values 27 and 28 (see
The Length of the Associated RA ID TLV is 4 octets. The Value field Section 10). The Length field in these Sub-TLVs takes the value 4.
in these sub-TLVs contains the associated RA ID. The RA ID value must The Value field in these sub-TLVs contains the associated RA ID. The
be a unique identifier for the RA within the ASON routing domain. RA ID value must be a unique identifier for the RA within the ASON
routing domain.
The format of the Inter-RA Export Upward and Inter-RA Export Downward The format of the Inter-RA Export Upward and Inter-RA Export Downward
Sub-TLVs is graphically depicted below: Sub-TLVs is graphically depicted below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Upward/Downward Type | Length (4) | | Upward/Downward Type (27/28) | Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Associated RA ID | | Associated RA ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing 7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing
TE LSAs MAY be imported or exported downward or upward in the ASON TE LSAs MAY be imported or exported downward or upward in the ASON
routing hierarchy. The direction and advertising RA ID are advertised routing hierarchy. The direction and advertising RA ID are advertised
in an Inter-RA Export Upward/Downward Sub-TLV. They MUST be retained in an Inter-RA Export Upward/Downward Sub-TLV. They MUST be retained
and advertised in the receiving RA with the associated routing and advertised in the receiving RA with the associated routing
skipping to change at page 14, line 39 skipping to change at page 14, line 39
OSPF link-state advertisement, and thereby provide much stronger OSPF link-state advertisement, and thereby provide much stronger
integrity protection for the OSPF routing domain. integrity protection for the OSPF routing domain.
10. IANA Considerations 10. IANA Considerations
This document is classified as Standards Track. It defines new sub- This document is classified as Standards Track. It defines new sub-
TLVs for inclusion in OSPF TE LSAs. According to the assignment TLVs for inclusion in OSPF TE LSAs. According to the assignment
policies for the registries of code points for these sub-TLVs, values policies for the registries of code points for these sub-TLVs, values
must be assigned by IANA [RFC3630]. must be assigned by IANA [RFC3630].
This draft requests early allocation of IANA code points in
accordance with [RFC4020]. [NOTE TO RFC Editor: this paragraph and
the RFC 4020 reference can be removed during RFC editing].
The following subsections summarize the required sub-TLVs. The following subsections summarize the required sub-TLVs.
10.1. Sub-TLVs of the Link TLV 10.1. Sub-TLVs of the Link TLV
This document defines the following sub-TLVs of the Link TLV This document defines the following sub-TLVs of the Link TLV
advertised in the OSPF TE LSA: advertised in the OSPF TE LSA:
- Local and Remote TE Router ID sub-TLV - Local and Remote TE Router ID sub-TLV (26)
- Associated RA ID sub-TLV - Inter-RA Export Upward sub-TLV (27)
- Inter-RA Export Upward sub-TLV - Inter-RA Export Downward sub-TLV (28)
- Inter-RA Export Downward sub-TLV
Codepoints for these Sub-TLVs should be allocated from the "Types for Codepoints for these Sub-TLVs should be allocated from the "Types for
sub-TLVs of TE Link TLV (Value 2)" registry standards action range (0 sub-TLVs of TE Link TLV (Value 2)" registry standards action range (0
- 32767) [RFC3630]. - 32767) [RFC3630].
Note that the same values for the Associated RA ID sub-TLV, Inter-RA Note that the same values for the Inter-RA Export Upward sub-TLV and
Export Upward sub-TLV, and Inter-RA Export Downward Sub-TLV MUST be the Inter-RA Export Downward Sub-TLV MUST be used when they appear in
used when they appear in the Link TLV, Node Attribute TLV, and Router the Link TLV, Node Attribute TLV, and Router Address TLV.
Address TLV.
10.2. Sub-TLVs of the Node Attribute TLV 10.2. Sub-TLVs of the Node Attribute TLV
This document defines the following sub-TLVs of the Node Attribute This document defines the following sub-TLVs of the Node Attribute
TLV advertised in the OSPF TE LSA: TLV advertised in the OSPF TE LSA:
- Local TE Router ID sub-TLV - Local TE Router ID sub-TLV (5)
- Associated RA ID sub-TLV - Inter-RA Export Upward sub-TLV (27)
- Inter-RA Export Upward sub-TLV - Inter-RA Export Downward sub-TLV (28)
- Inter-RA Export Downward sub-TLV
Codepoints for these Sub-TLVs should be assigned from the "Types for Codepoints for these Sub-TLVs should be assigned from the "Types for
sub-TLVs of TE Node Attribute TLV (Value 5)" registry standards sub-TLVs of TE Node Attribute TLV (Value 5)" registry standards
action range (0 - 32767) [RFC5786]. action range (0 - 32767) [RFC5786].
Note that the same values for the Associated RA ID sub-TLV, Inter-RA Note that the same values for the Inter-RA Export Upward sub-TLV and
Export Upward sub-TLV, and Inter-RA Export Downward Sub-TLV MUST be the Inter-RA Export Downward Sub-TLV MUST be used when they appear in
used when they appear in the Link TLV, Node Attribute TLV, and Router the Link TLV, Node Attribute TLV, and Router Address TLV.
Address TLV.
10.3. Sub-TLVs of the Router Address TLV 10.3. Sub-TLVs of the Router Address TLV
The Router Address TLV is advertised in the OSPF TE LSA [RFC3630]. The Router Address TLV is advertised in the OSPF TE LSA [RFC3630].
Since this TLV currently has no Sub-TLVs defined, a "Types for sub- Since this TLV currently has no Sub-TLVs defined, a "Types for sub-
TLVs of Router Address TLV (Value 1)" registry must be defined. TLVs of Router Address TLV (Value 1)" registry must be defined.
The registry guidelines for the assignment of types for sub-TLVs of The registry guidelines for the assignment of types for sub-TLVs of
the Router Address TLV are as follows: the Router Address TLV are as follows:
skipping to change at page 16, line 6 skipping to change at page 16, line 5
RFCs. RFCs.
o Types in the range 32778-65535 are not to be assigned at this o Types in the range 32778-65535 are not to be assigned at this
time. Before any assignments can be made in this range, there time. Before any assignments can be made in this range, there
MUST be a Standards Track RFC that specifies IANA MUST be a Standards Track RFC that specifies IANA
Considerations that covers the range being assigned. Considerations that covers the range being assigned.
This document defines the following sub-TLVs for inclusion in the This document defines the following sub-TLVs for inclusion in the
Router Address TLV: Router Address TLV:
- Associated RA ID sub-TLV - Inter-RA Export Upward sub-TLV (27)
- Inter-RA Export Upward sub-TLV - Inter-RA Export Downward sub-TLV (28)
- Inter-RA Export Downward sub-TLV
Codepoints for these Sub-TLVs should be allocated from the "Types for Codepoints for these Sub-TLVs should be allocated from the "Types for
sub-TLVs of Router Address TLV (Value 1)" registry standards action sub-TLVs of Router Address TLV (Value 1)" registry standards action
range (0 - 32767). range (0 - 32767).
Note that the same values for the Associated RA ID sub-TLV, Inter-RA Note that the same values for the Inter-RA Export Upward sub-TLV and
Export Upward sub-TLV, and Inter-RA Export Downward Sub-TLV MUST be the Inter-RA Export Downward Sub-TLV MUST be used when they appear in
used when they appear in the Link TLV, Node Attribute TLV, and Router the Link TLV, Node Attribute TLV, and Router Address TLV.
Address TLV.
11. Management Considerations 11. Management Considerations
11.1. Routing Area (RA) Isolation 11.1. Routing Area (RA) Isolation
If the RA Identifier is mapped to the OSPF Area ID as recommended in If the RA Identifier is mapped to the OSPF Area ID as recommended in
section 2.0, OSPF [RFC2328] implicitly provides isolation. On any section 2.0, OSPF [RFC2328] implicitly provides isolation. On any
intra-RA link, packets will only be accepted if the area-id in the intra-RA link, packets will only be accepted if the area-id in the
OSPF packet header matches the area ID for the OSPF interface on OSPF packet header matches the area ID for the OSPF interface on
which the packet was received. Hence, RCs will only establish which the packet was received. Hence, RCs will only establish
skipping to change at page 23, line 22 skipping to change at page 23, line 22
[RFC5786] Aggarwal, R. and K. Kompella, "Advertising a Router's [RFC5786] Aggarwal, R. and K. Kompella, "Advertising a Router's
Local Addresses in OSPF TE Extensions", RFC 5786, March Local Addresses in OSPF TE Extensions", RFC 5786, March
2010. 2010.
13.2. Informative References 13.2. Informative References
[RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with [RFC2154] Murphy, S., Badger, M., and B. Wellington, "OSPF with
Digital Signatures", RFC 2154, June 1997. Digital Signatures", RFC 2154, June 1997.
[RFC4020] Kompella, K. and A. Zinin, "Early IANA Allocation of
Standards Track Code Points", BCP 100, RFC 4020,
February 2005.
[RFC4258] Brungard, D., Ed., "Requirements for Generalized Multi- [RFC4258] Brungard, D., Ed., "Requirements for Generalized Multi-
Protocol Label Switching (GMPLS) Routing for the Protocol Label Switching (GMPLS) Routing for the
Automatically Switched Optical Network (ASON)", RFC Automatically Switched Optical Network (ASON)", RFC
4258, November 2005. 4258, November 2005.
[RFC4652] Papadimitriou, D., Ed., Ong, L., Sadler, J., Shew, S., [RFC4652] Papadimitriou, D., Ed., Ong, L., Sadler, J., Shew, S.,
and D. Ward, "Evaluation of Existing Routing Protocols and D. Ward, "Evaluation of Existing Routing Protocols
against Automatic Switched Optical Network (ASON) against Automatic Switched Optical Network (ASON)
Routing Requirements", RFC 4652, October 2006. Routing Requirements", RFC 4652, October 2006.
 End of changes. 20 change blocks. 
85 lines changed or deleted 87 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/