draft-ietf-ccamp-rfc5787bis-05.txt   draft-ietf-ccamp-rfc5787bis-06.txt 
INTERNET-DRAFT A. Malis, ed. INTERNET-DRAFT A. Malis, ed.
Obsoletes: 5787 (if approved) Verizon Communications Obsoletes: 5787 (if approved) Verizon Communications
Updates: 5786 A. Lindem, ed. Updates: 5786 A. Lindem, ed.
Intended Status: Proposed Standard Ericsson Intended Status: Proposed Standard Ericsson
Expires: January 21, 2013 D. Papadimitriou, ed. Expires: April 12, 2013 D. Papadimitriou, ed.
Alcatel-Lucent Alcatel-Lucent
July 20, 2012 October 9, 2012
ASON Routing for OSPFv2 Protocols ASON Routing for OSPFv2 Protocols
draft-ietf-ccamp-rfc5787bis-05.txt draft-ietf-ccamp-rfc5787bis-06.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 3, line 31 skipping to change at page 2, line 32
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. This document obsoletes RFC 5787 and updates RFC 5786. RFC 4258. This document obsoletes RFC 5787 and updates RFC 5786.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions Used in This Document . . . . . . . . . . . . 6 1.1. Conventions Used in This Document . . . . . . . . . . . . 5
2. Routing Areas, OSPF Areas, and Protocol Instances . . . . . . 6 2. Routing Areas, OSPF Areas, and Protocol Instances . . . . . . 5
3. Terminology and Identification . . . . . . . . . . . . . . . . 7 3. Terminology and Identification . . . . . . . . . . . . . . . . 6
4. Reachability . . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Reachability . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Link Attribute . . . . . . . . . . . . . . . . . . . . . . . . 8 5. Link Attribute . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Local Adaptation . . . . . . . . . . . . . . . . . . . . . 9 5.1. Local Adaptation . . . . . . . . . . . . . . . . . . . . . 8
5.2. Bandwidth Accounting . . . . . . . . . . . . . . . . . . . 9 5.2. Bandwidth Accounting . . . . . . . . . . . . . . . . . . . 8
6. Routing Information Scope . . . . . . . . . . . . . . . . . . 10 6. Routing Information Scope . . . . . . . . . . . . . . . . . . 9
6.1. Link Advertisement (Local and Remote TE Router ID 6.1. Link Advertisement (Local and Remote TE Router ID
Sub-TLV) . . . . . . . . . . . . . . . . . . . . . . . . . 10 Sub-TLV) . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.2. Reachability Advertisement (Local TE Router ID sub-TLV) . 11 6.2. Reachability Advertisement (Local TE Router ID sub-TLV) . 10
7. Routing Information Dissemination . . . . . . . . . . . . . . 12 7. Routing Information Dissemination . . . . . . . . . . . . . . 11
7.1 Import/Export Rules . . . . . . . . . . . . . . . . . . . . 12 7.1 Import/Export Rules . . . . . . . . . . . . . . . . . . . . 11
7.2 Loop Prevention . . . . . . . . . . . . . . . . . . . . . . 13 7.2 Loop Prevention . . . . . . . . . . . . . . . . . . . . . . 12
7.2.1 Inter-RA Export Upward/Downward Sub-TLVs . . . . . . . 13 7.2.1 Inter-RA Export Upward/Downward Sub-TLVs . . . . . . . 12
7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing . . 14 7.2.2 Inter-RA Export Upward/Downward Sub-TLV Processing . . 13
8. OSPFv2 Scalability . . . . . . . . . . . . . . . . . . . . . . 15 8. OSPFv2 Scalability . . . . . . . . . . . . . . . . . . . . . . 14
9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 9. Security Considerations . . . . . . . . . . . . . . . . . . . 14
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
10.1. Sub-TLVs of the Link TLV . . . . . . . . . . . . . . . . 16 10.1. Sub-TLVs of the Link TLV . . . . . . . . . . . . . . . . 15
10.2. Sub-TLVs of the Node Attribute TLV . . . . . . . . . . . 16 10.2. Sub-TLVs of the Node Attribute TLV . . . . . . . . . . . 15
10.3. Sub-TLVs of the Router Address TLV . . . . . . . . . . . 17 10.3. Sub-TLVs of the Router Address TLV . . . . . . . . . . . 16
11. Management Considerations . . . . . . . . . . . . . . . . . 17 11. Management Considerations . . . . . . . . . . . . . . . . . 17
11.1. Routing Area (RA) Isolation . . . . . . . . . . . . . . . 18 11.1. Routing Area (RA) Isolation . . . . . . . . . . . . . . . 17
11.2 Routing Area (RA) Topology/Configuration Changes . . . . . 18 11.2 Routing Area (RA) Topology/Configuration Changes . . . . . 17
12. Comparison to Requirements in RFC 4258 . . . . . . . . . . . 18 12. Comparison to Requirements in RFC 4258 . . . . . . . . . . . 17
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
13.1. Normative References . . . . . . . . . . . . . . . . . . 24 13.1. Normative References . . . . . . . . . . . . . . . . . . 23
13.2. Informative References . . . . . . . . . . . . . . . . . 25 13.2. Informative References . . . . . . . . . . . . . . . . . 24
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
14.1 RFC 5787 Acknowledgements . . . . . . . . . . . . . . . . . 26 14.1 RFC 5787 Acknowledgements . . . . . . . . . . . . . . . . . 25
Appendix A. ASON Terminology . . . . . . . . . . . . . . . . . . 27 Appendix A. ASON Terminology . . . . . . . . . . . . . . . . . . 26
Appendix B. ASON Routing Terminology . . . . . . . . . . . . . . 28 Appendix B. ASON Routing Terminology . . . . . . . . . . . . . . 27
Appendix C. Changes from RFC 5787 . . . . . . . . . . . . . . . . 29 Appendix C. Changes from RFC 5787 . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
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 6, line 22 skipping to change at page 5, line 22
The reader is assumed to be familiar with the terminology and The reader is assumed to be familiar with the terminology and
requirements developed in [RFC4258] and the evaluation outcomes requirements developed in [RFC4258] and the evaluation outcomes
described in [RFC4652]. described in [RFC4652].
General ASON terminology is provided in Appendix A. ASON routing General ASON terminology is provided in Appendix A. ASON routing
terminology is described in Appendix B. terminology is described in Appendix B.
2. Routing Areas, OSPF Areas, and Protocol Instances 2. Routing Areas, OSPF Areas, and Protocol Instances
An ASON routing area (RA) represents a partition of the data plane, An ASON routing area (RA) represents a partition of the transport
and its identifier is used within the control plane as the plane, and its identifier is used within the control plane as the
representation of this partition. representation of this partition.
RAs are hierarchically contained: a higher-level (parent) RA contains RAs are hierarchically contained: a higher-level (parent) RA contains
lower-level (child) RAs that in turn MAY also contain RAs. Thus, RAs lower-level (child) RAs that in turn MAY also contain RAs. Thus, RAs
contain RAs that recursively define successive hierarchical RA contain RAs that recursively define successive hierarchical RA
levels. Routing information may be exchanged between levels of the levels. Routing information may be exchanged between levels of the
RA hierarchy, i.e., Level N+1 and N, where Level N represents the RAs RA hierarchy, i.e., Level N+1 and N, where Level N represents the RAs
contained by Level N+1. The links connecting RAs may be viewed as contained by Level N+1. The links connecting RAs may be viewed as
external links (inter-RA links), and the links representing external links (inter-RA links), and the links representing
connectivity within an RA may be viewed as internal links (intra-RA connectivity within an RA may be viewed as internal links (intra-RA
skipping to change at page 7, line 24 skipping to change at page 6, line 24
components, and Signaling Communications Network (SCN) addresses. components, and Signaling Communications Network (SCN) addresses.
This section discusses the mapping between ASON routing identifiers This section discusses the mapping between ASON routing identifiers
and corresponding identifiers defined for GMPLS routing, and how and corresponding identifiers defined for GMPLS routing, and how
these support the physical (or logical) separation of transport plane these support the physical (or logical) separation of transport plane
entities and control plane components. GMPLS supports this entities and control plane components. GMPLS supports this
separation of identifiers and planes. separation of identifiers and planes.
In the context of OSPF Traffic Engineering (TE), an ASON transport In the context of OSPF Traffic Engineering (TE), an ASON transport
node corresponds to a unique OSPF TE node. An OSPF TE node is node corresponds to a unique OSPF TE node. An OSPF TE node is
uniquely identified by the TE Router Address TLV [RFC3630]. In this uniquely identified by the TE Router Address TLV [RFC3630]. In this
document, this TE Router Address is referred to as the TE Router ID, document, the TE Router Address is referred to as the TE Router ID.
which is in the ASON SCN name space. The TE Router ID should not be In GMPLS, TE router addresses are advertised as reachable in both the
confused with the OSPF Router ID which uniquely identifies an OSPF control and transport planes, see Section 4 below. Furthermore, the
router within an OSPF routing domain [RFC2328] and is in a name space TE Router ID should not be confused with the OSPF Router ID that
for control plane components. uniquely identifies an OSPF router within an OSPF routing domain
[RFC2328] and is in a name space for control plane components.
The Router Address top-level TLV definition, processing, and usage The Router Address top-level TLV definition, processing, and usage
are largely unchanged from [RFC3630]. This TLV specifies a stable are largely unchanged from [RFC3630]. This TLV specifies a stable
OSPF TE node IP address, i.e., the IP address is always reachable OSPF TE node IP address, i.e., the IP address is always reachable
when there is IP connectivity to the associated OSPF TE node. when there is IP connectivity to the associated OSPF TE node.
However, in the context of the OSPF ASON operation, the TE Router ID
is an identifier within the ASON SCN.
ASON defines a Routing Controller (RC) as an entity that handles ASON defines a Routing Controller (RC) as an entity that handles
(abstract) information needed for routing and the routing information (abstract) information needed for routing and the routing information
exchange with peering RCs by operating on the Routing Database (RDB). exchange with peering RCs by operating on the Routing Database (RDB).
ASON defines a Protocol Controller (PC) as an entity that handles ASON defines a Protocol Controller (PC) as an entity that handles
protocol-specific message exchanges according to the reference point protocol-specific message exchanges according to the reference point
over which the information is exchanged (e.g., E-NNI, I-NNI), and over which the information is exchanged (e.g., E-NNI, I-NNI), and
internal exchanges with the Routing Controller (RC) [RFC4258]. In internal exchanges with the Routing Controller (RC) [RFC4258]. In
this document, an OSPF router advertising ASON TE topology this document, an OSPF router advertising ASON TE topology
information will perform both the functions of the RC and PC. The information will perform both the functions of the RC and PC. The
OSPF routing domain comprises the control plane and each OSPF router OSPF routing domain comprises the control plane and each OSPF router
is uniquely identified by its OSPF Router ID [RFC2328]. is uniquely identified by its OSPF Router ID [RFC2328].
4. Reachability 4. Reachability
In ASON, reachability refers to the set of endpoints reachable in the In ASON, reachability information describes the set of endpoints that
transport plane by an associated ASON transport node. Reachable are reachable by the associated node in the transport plane.
entities are identified in the ASON SCN name space. Reachability information represents transport plane resources, e.g.,
an optical cross-connect interface, and uses transport plane
identifiers.
In order to advertise blocks of reachable address prefixes, a In order to advertise blocks of reachable address prefixes, a
summarization mechanism is introduced that is based on the techniques summarization mechanism is introduced that is based on the techniques
described in [RFC5786]. For ASON reachability advertisement, blocks described in [RFC5786]. For ASON reachability advertisement, blocks
of reachable address prefixes are advertised together with the of reachable address prefixes are advertised together with the
associated transport plane node. The transport plane node is associated transport plane node. The transport plane node is
identified in OSPF TE LSAs by its TE Router ID, as discussed in identified in OSPF TE LSAs by its TE Router ID, as discussed in
section 6. section 6.
In order to support ASON reachability advertisement, the Node In order to support ASON reachability advertisement, the Node
skipping to change at page 8, line 39 skipping to change at page 7, line 41
A router may support multiple transport nodes as discussed in section A router may support multiple transport nodes as discussed in section
6, and, as a result, may be required to advertise reachability 6, and, as a result, may be required to advertise reachability
separately for each transport node. As a consequence, it MUST be separately for each transport node. As a consequence, it MUST be
possible for the router to originate more than one TE LSA containing possible for the router to originate more than one TE LSA containing
the Node Attribute TLV when used for ASON reachability advertisement. the Node Attribute TLV when used for ASON reachability advertisement.
Hence, the Node Attribute TLV [RFC5786] advertisement rules are Hence, the Node Attribute TLV [RFC5786] advertisement rules are
relaxed. A Node Attribute TLV MAY appear in more than one TE LSA relaxed. A Node Attribute TLV MAY appear in more than one TE LSA
originated by the RC when the RC is advertising reachability originated by the RC when the RC is advertising reachability
information for a different transport node identified by the Local TE information for a different transport node identified by the Local TE
Router Sub-TLV (refer to section 6.1). Router Sub-TLV (refer to section 6.2).
As specified in [RFC3630], TE advertised router addresses are also
advertised as reachable in the control plane and are therefore also
valid identifiers in the ASON SCN name space.
5. Link Attribute 5. Link Attribute
With the exception of local adaptation (described below), the mapping With the exception of local adaptation (described below), the mapping
of link attributes and characteristics to OSPF TE Link TLV Sub-TLVs of link attributes and characteristics to OSPF TE Link TLV Sub-TLVs
is unchanged [RFC4652]. OSPF TE Link TLV Sub-TLVs are described in is unchanged [RFC4652]. OSPF TE Link TLV Sub-TLVs are described in
[RFC3630] and [RFC4203]. Advertisement of this information SHOULD be [RFC3630] and [RFC4203]. Advertisement of this information SHOULD be
supported on a per-layer basis, i.e., one TE LSA per unique switching supported on a per-layer basis, i.e., one TE LSA per unique switching
capability and bandwidth granularity combination. capability and bandwidth granularity combination.
skipping to change at page 11, line 33 skipping to change at page 10, line 33
of 0 is specified for the Local or Remote TE Router Identifier, the of 0 is specified for the Local or Remote TE Router Identifier, the
Link TLV will not be used for transport plane path computation. Link TLV will not be used for transport plane path computation.
Additionally, the condition SHOULD be logged for possible action by Additionally, the condition SHOULD be logged for possible action by
the network operator. the network operator.
Note: The Link ID sub-TLV identifies the other end of the link (i.e., Note: The Link ID sub-TLV identifies the other end of the link (i.e.,
Router ID of the neighbor for point-to-point links) [RFC3630]. When Router ID of the neighbor for point-to-point links) [RFC3630]. When
the Local and Remote TE Router ID Sub-TLV is present, it MUST be used the Local and Remote TE Router ID Sub-TLV is present, it MUST be used
to identify local and remote transport node endpoints for the link to identify local and remote transport node endpoints for the link
and the Link-ID sub-TLV MUST be ignored. In fact, when the Local and and the Link-ID sub-TLV MUST be ignored. In fact, when the Local and
Remote ID sub-TLV is specified, the Link-ID sub-TLV MAY be omitted. Remote TE Router ID sub-TLV is specified, the Link-ID sub-TLV MAY be
The Local and Remote ID sub-TLV, if specified, MUST only be specified omitted. The Local and Remote TE Router ID sub-TLV, if specified,
once. If specified more than once, instances preceding the first will MUST only be specified once. If specified more than once, instances
be ignored and condition SHOULD be logged for possible action by the other than the first will be ignored and condition SHOULD be logged
network operator. for possible action by the network operator.
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 the The Type field of the Local TE Router ID sub-TLV is assigned the
value 5 (see Section 10). The Length field takes the value 4. The value 5 (see Section 10). The Length field takes the value 4. The
Value field of this sub-TLV contains the Local TE Router Identifier Value field of this sub-TLV contains the Local TE Router Identifier
[RFC3630] encoded over 4 octets. 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 (5) | Length (4) | | Type (5) | Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local TE Router Identifier | | Local TE Router Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 28 skipping to change at page 11, line 28
Router ID advertised in the Router Address TLV. For consistency, Router ID advertised in the Router Address TLV. For consistency,
this sub-TLV MUST be included when OSPF is used for the advertisement this sub-TLV MUST be included when OSPF is used for the advertisement
of ASON information as described herein. If it is not included in a of ASON information as described herein. If it is not included in a
Node Attribute TLV or a value of 0 is specified for the Local TE Node Attribute TLV or a value of 0 is specified for the Local TE
Router Identifier, the Note Attribute TLV will not be used for Router Identifier, the Note Attribute TLV will not be used for
determining ASON SCN reachability. Additionally, the condition determining ASON SCN reachability. Additionally, the condition
SHOULD be logged for possible action by the network operator. SHOULD be logged for possible action by the network operator.
7. Routing Information Dissemination 7. Routing Information Dissemination
An ASON routing area (RA) represents a partition of the data plane, An ASON routing area (RA) represents a partition of the transport
and its identifier is used within the control plane as the plane, and its identifier is used within the control plane as the
representation of this partition. An RA may contain smaller RAs representation of this partition. An RA may contain smaller RAs
inter-connected by links. ASON RA levels do not map directly to OSPF inter-connected by links. ASON RA levels do not map directly to OSPF
areas. Rather, hierarchical levels of RAs are represented by separate areas. Rather, hierarchical levels of RAs are represented by separate
OSPF protocol instances. However, it is useful to align the RA OSPF protocol instances. However, it is useful to align the RA
identifiers and area ID in order to facilitate isolation of RAs as identifiers and area ID in order to facilitate isolation of RAs as
described in Section 11.1. described in Section 11.1.
Routing controllers (RCs) supporting multiple RAs disseminate Routing controllers (RCs) supporting multiple RAs disseminate
information downward and upward in this ASON hierarchy. The vertical information downward and upward in this ASON hierarchy. The vertical
routing information dissemination mechanisms described in this routing information dissemination mechanisms described in this
skipping to change at page 16, line 36 skipping to change at page 15, line 36
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 (TBDx) - Local and Remote TE Router ID sub-TLV (TBDx)
- Inter-RA Export Upward sub-TLV (TBDy) - Inter-RA Export Upward sub-TLV (TBDy)
- Inter-RA Export Downward sub-TLV (TBDz) - Inter-RA Export Downward sub-TLV (TBDz)
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 Inter-RA Export Upward sub-TLV and Note that the same values for the Inter-RA Export Upward sub-TLV and
the Inter-RA Export Downward Sub-TLV MUST be used when they appear in the Inter-RA Export Downward Sub-TLV MUST be used when they appear in
the Link TLV, Node Attribute TLV, and Router Address TLV. the Link TLV, Node Attribute TLV, and Router 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 (5) - Local TE Router ID sub-TLV (5)
- Inter-RA Export Upward sub-TLV (TBDy) - Inter-RA Export Upward sub-TLV (TBDy)
- Inter-RA Export Downward sub-TLV (TBDz) - Inter-RA Export Downward sub-TLV (TBDz)
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 Inter-RA Export Upward sub-TLV and Note that the same values for the Inter-RA Export Upward sub-TLV and
the Inter-RA Export Downward Sub-TLV MUST be used when they appear in the Inter-RA Export Downward Sub-TLV MUST be used when they appear in
the Link TLV, Node Attribute TLV, and Router Address TLV. the Link TLV, Node Attribute TLV, and Router 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:
o Types in the range 0-32767 are to be assigned via Standards o Types in the range 0-32767 are to be assigned via Standards
Action. Action.
o Type 0 in the aforementioned standards action range (0-32767)
is reserved.
o Types in the range 32768-32777 are for experimental use; these o Types in the range 32768-32777 are for experimental use; these
will not be registered with IANA, and MUST NOT be mentioned by will not be registered with IANA, and MUST NOT be mentioned by
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:
- Inter-RA Export Upward sub-TLV (TBDy) - Inter-RA Export Upward sub-TLV (TBDy)
- Inter-RA Export Downward sub-TLV (TBDz) - Inter-RA Export Downward sub-TLV (TBDz)
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.
Note that the same values for the Inter-RA Export Upward sub-TLV and Note that the same values for the Inter-RA Export Upward sub-TLV and
the Inter-RA Export Downward Sub-TLV MUST be used when they appear in the Inter-RA Export Downward Sub-TLV MUST be used when they appear in
the Link TLV, Node Attribute TLV, and Router Address TLV. the Link TLV, Node Attribute TLV, and Router 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
adjacencies and exchange reachability information (see Section 4.0) adjacencies and exchange reachability information (see Section 4.0)
with RCs in the same RC. Other mechanisms for RA isolation are with RCs in the same RA. Other mechanisms for RA isolation are
beyond the scope of this document. beyond the scope of this document.
11.2 Routing Area (RA) Topology/Configuration Changes 11.2 Routing Area (RA) Topology/Configuration Changes
The GMPLS Routing for ASON requirements [RFC4258] dictate that the The GMPLS Routing for ASON requirements [RFC4258] dictate that the
routing protocol MUST support reconfiguration and SHOULD support routing protocol MUST support reconfiguration and SHOULD support
architectural evolution. OSPF [RFC2328] includes support for the architectural evolution. OSPF [RFC2328] includes support for the
dynamic introduction or removal of ASON reachability information dynamic introduction or removal of ASON reachability information
through the flooding and purging of OSPF opaque LSAs [RFC5250]. Also, through the flooding and purging of OSPF opaque LSAs [RFC5250]. Also,
when an RA is partitioned or an RC fails, stale LSAs SHOULD NOT be when an RA is partitioned or an RC fails, stale LSAs SHOULD NOT be
skipping to change at page 28, line 38 skipping to change at page 27, line 38
the Transport Network defined in Recommendation G.805. the Transport Network defined in Recommendation G.805.
User Network Interface (UNI): interfaces are located between protocol User Network Interface (UNI): interfaces are located between protocol
controllers between a user and a control domain. Note: There is controllers between a user and a control domain. Note: There is
no routing function associated with a UNI reference point. no routing function associated with a UNI reference point.
Appendix B. ASON Routing Terminology Appendix B. ASON Routing Terminology
This document makes use of the following terms: This document makes use of the following terms:
Routing Area (RA): an RA represents a partition of the data plane, Routing Area (RA): an RA represents a partition of the transport
and its identifier is used within the control plane as the plane, and its identifier is used within the control plane as the
representation of this partition. Per [G.8080], an RA is defined representation of this partition. Per [G.8080], an RA is defined
by a set of sub-networks, the links that interconnect them, and by a set of sub-networks, the links that interconnect them, and
the interfaces representing the ends of the links exiting that RA. the interfaces representing the ends of the links exiting that RA.
An RA may contain smaller RAs inter-connected by links. The An RA may contain smaller RAs inter-connected by links. The
limit of subdivision results in an RA that contains two sub- limit of subdivision results in an RA that contains two sub-
networks interconnected by a single link. networks interconnected by a single link.
Routing Database (RDB): a repository for the local topology, network Routing Database (RDB): a repository for the local topology, network
topology, reachability, and other routing information that is topology, reachability, and other routing information that is
updated as part of the routing information exchange and may updated as part of the routing information exchange and may
 End of changes. 21 change blocks. 
66 lines changed or deleted 75 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/