draft-ietf-ccamp-lsp-hierarchy-bis-04.txt   draft-ietf-ccamp-lsp-hierarchy-bis-05.txt 
Network Working Group K. Shiomoto (Ed.) Network Working Group K. Shiomoto (Ed.)
Internet Draft NTT Internet Draft NTT
Updates: 3477, 4206 A. Farrel (Ed.) Updates: 3477, 4206 A. Farrel (Ed.)
Proposed Category: Proposed Standard Old Dog Consulting Proposed Category: Proposed Standard Old Dog Consulting
Created: October 15, 2008 Created: October 16, 2008
Expires: April 15, 2008 Expires: April 16, 2009
Procedures for Dynamically Signaled Procedures for Dynamically Signaled
Hierarchical Label Switched Paths Hierarchical Label Switched Paths
draft-ietf-ccamp-lsp-hierarchy-bis-04.txt draft-ietf-ccamp-lsp-hierarchy-bis-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 2, line 13 skipping to change at page 2, line 13
component link of a TE link bundle and to identify the bundle. component link of a TE link bundle and to identify the bundle.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1. Introduction and Problem Statement ............................. 1 1. Introduction and Problem Statement ............................. 3
1.1. Background ................................................... 1.1. Background ................................................... 4
1.1.1. Hierarchical LSPs .......................................... 1.1.1. Hierarchical LSPs .......................................... 4
1.1.2. LSP Stitching Segments ..................................... 1.1.2. LSP Stitching Segments ..................................... 4
1.1.3. Private Links .............................................. 1.1.3. Private Links .............................................. 4
1.1.4. Routing Adjacencies ........................................ 1.1.4. Routing Adjacencies ........................................ 4
1.1.5. Forwarding Adjacencies ..................................... 1.1.5. Forwarding Adjacencies ..................................... 5
1.1.5. Client/Server Networks ..................................... 1.1.6. Client/Server Networks ..................................... 5
1.1.6. Link Bundles ............................................... 1.1.7. Link Bundles ............................................... 5
1.2. Desired Function ............................................. 1.2. Desired Function ............................................. 6
1.3. Existing Mechanisms .......................................... 1.3. Existing Mechanisms .......................................... 6
1.3.1. LSP Setup .................................................. 1.3.1. LSP Setup .................................................. 6
1.3.2. Routing Adjacency Establishment and Link State Advertisement 1.3.2. Routing Adjacency Establishment and Link State Advertisement 6
1.3.3. TE Link Advertisement ...................................... 1.3.3. TE Link Advertisement ...................................... 6
1.3.4. Configuration and Management Techniques .................... 1.3.4. Configuration and Management Techniques .................... 7
1.3.5. Signaled Unnumbered FAs .................................... 1.3.5. Signaled Unnumbered FAs .................................... 7
1.3.6. Establishing Numbered FAs Through Signaling and Routing .... 1.3.6. Establishing Numbered FAs Through Signaling and Routing .... 8
1.4. Overview of Required Extensions .............................. 1.4. Overview of Required Extensions .............................. 9
1.4.1. Efficient Signaling of Numbered FAs ........................ 1.4.1. Efficient Signaling of Numbered FAs ........................ 9
1.4.2. LSPs for Use as Private Links .............................. 1.4.2. LSPs for Use as Private Links .............................. 9
1.4.3. Signaling an LSP For use in Another Network ................ 1.4.3. Signaling an LSP For use in Another Network ................ 9
1.4.4. Signaling an LSP for Use in a Link Bundle .................. 1.4.4. Signaling an LSP for Use in a Link Bundle .................. 9
1.4.5. Support for IPv4 and IPv6 .................................. 1.4.5. Support for IPv4 and IPv6 ................................. 10
1.4.6. Backward Compatibility ..................................... 1.4.6. Backward Compatibility .................................... 10
2. Overview of Solution ........................................... 2. Overview of Solution .......................................... 10
2.1. Common Approach for Numbered and Unnumbered Links ............ 2.1. Common Approach for Numbered and Unnumbered Links ........... 10
2.2. LSP Usage Indication ......................................... 2.2. LSP Usage Indication ........................................ 10
2.3. IGP Instance Identification .................................. 2.3. IGP Instance Identification ................................. 10
2.4. Link Bundle Identification ................................... 2.4. Link Bundle Identification .................................. 11
2.5. Backward Compatibility ....................................... 2.5. Backward Compatibility ...................................... 11
3. Mechanisms and Protocol Extensions ............................. 3. Mechanisms and Protocol Extensions ............................ 11
3.1. LSP_TUNNEL_INTERFACE_ID Object ............................... 3.1. LSP_TUNNEL_INTERFACE_ID Object .............................. 11
3.1.1. Existing Definition and Usage .............................. 3.1.1. Existing Definition and Usage ............................. 11
3.1.2. Unnumbered Links with Action Identification ................ 3.1.2. Unnumbered Links with Action Identification ............... 12
3.1.3. IPv4 Numbered Links with Action Identification ............. 3.1.3. IPv4 Numbered Links with Action Identification ............ 14
3.1.4. IPv6 Numbered Links with Action Identification ............. 3.1.4. IPv6 Numbered Links with Action Identification ............ 15
3.2. Target IGP Identification TLV ................................ 3.2. Target IGP Identification TLV ............................... 16
3.3. Component Link Identification TLV ............................ 3.3. Component Link Identification TLV ........................... 17
3.3.1. Unnumbered Component Link Identification ................... 3.3.1. Unnumbered Component Link Identification .................. 18
3.3.2. Numbered Component Link Identification ..................... 3.3.2. IPv4 Numbered Component Link Identification ............... 18
3.3.3. IPv6 Numbered Component Link Identification ............... 18
3.4. Link State Advertisement ..................................... 3.4. Link State Advertisement .................................... 19
3.5. Message Formats .............................................. 3.5. Message Formats ............................................. 20
3.6. Error Cases and Non-Acceptance ............................... 3.6. Error Cases and Non-Acceptance .............................. 20
3.7. Backward Compatibility ....................................... 3.7. Backward Compatibility ...................................... 21
4. Security Considerations ........................................ 4. Security Considerations ....................................... 22
5. IANA Considerations ............................................ 5. IANA Considerations ........................................... 23
5.1. New Class Types .............................................. 5.1. New Class Types ............................................. 23
5.2. Hierarchy Actions ............................................ 5.2. Hierarchy Actions ........................................... 23
5.3. New Error Codes and Error Values ............................. 5.3. New Error Codes and Error Values ............................ 24
6. Acknowledgements ............................................... 6. Acknowledgements .............................................. 24
7. References ..................................................... 7. References .................................................... 24
7.1. Normative References ......................................... 7.1. Normative References ........................................ 24
7.2. Informative References ....................................... 7.2. Informative References ...................................... 25
8. Editors' Addresses ............................................. 8. Editors' Addresses ............................................ 27
9. Authors' Addresses ............................................. 9. Authors' Addresses ............................................ 27
1. Introduction and Problem Statement 1. Introduction and Problem Statement
[RFC4206] defines how to set up Label Switched Paths (LSPs) in [RFC4206] defines how to set up Label Switched Paths (LSPs) in
Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering
(TE) networks to be used as hierarchical Label Switched Paths (TE) networks to be used as hierarchical Label Switched Paths
(H-LSPs). (H-LSPs).
[RFC4201] describes how to collect together TE links between the same [RFC4201] describes how to collect together TE links between the same
pair of nodes and advertise them as a single TE link called a link pair of nodes and advertise them as a single TE link called a link
skipping to change at page 5, line 22 skipping to change at page 5, line 22
control plane that advertises the TE links from which the LSP is control plane that advertises the TE links from which the LSP is
constructed. The LSP itself is called an FA-LSP. constructed. The LSP itself is called an FA-LSP.
Thus, an H-LSP or S-LSP may form an FA such that it is advertised as Thus, an H-LSP or S-LSP may form an FA such that it is advertised as
a TE link in the same instance of the routing protocol as was used to a TE link in the same instance of the routing protocol as was used to
advertise the TE links that the LSP traverses. advertise the TE links that the LSP traverses.
As observed in [RFC4206] the nodes at the ends of an FA would not As observed in [RFC4206] the nodes at the ends of an FA would not
usually have a routing adjacency. usually have a routing adjacency.
1.1.5. Client/Server Networks 1.1.6. Client/Server Networks
An LSP may be created in one network and used as a link (sometimes An LSP may be created in one network and used as a link (sometimes
called a virtual link) in another networks [RFC5212]. In this case called a virtual link) in another networks [RFC5212]. In this case
the networks are often referred to as server and client networks the networks are often referred to as server and client networks
respectively. respectively.
The server network LSP is used as an H-LSP or an S-LSP as described The server network LSP is used as an H-LSP or an S-LSP as described
above, but does not form an FA because the client and server networks above, but does not form an FA because the client and server networks
run separate instances of the control plane routing protocols. run separate instances of the control plane routing protocols.
The virtual link may be used in the client network as a private link The virtual link may be used in the client network as a private link
or may be advertised in the client network IGP. Additionally, the or may be advertised in the client network IGP. Additionally, the
link may be used in the client network to form a routing adjacency link may be used in the client network to form a routing adjacency
and/or as a TE link. and/or as a TE link.
1.1.6. Link Bundles 1.1.7. Link Bundles
[RFC4201] recognizes that a pair of adjacent routers may have a large [RFC4201] recognizes that a pair of adjacent routers may have a large
number of TE links that run between them. This can be a considerable number of TE links that run between them. This can be a considerable
burden to the operator who may need to configure them, and to the IGP burden to the operator who may need to configure them, and to the IGP
that must distribute information about each of them. A TE link bundle that must distribute information about each of them. A TE link bundle
is defined by [RFC4201] as a TE link that is advertised as an is defined by [RFC4201] as a TE link that is advertised as an
aggregate of multiple TE links that could have been advertised in aggregate of multiple TE links that could have been advertised in
their own right. All TE links that are collected into a TE link their own right. All TE links that are collected into a TE link
bundle have the same TE properties. bundle have the same TE properties.
skipping to change at page 18, line 44 skipping to change at page 18, line 44
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | | IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv4 Address IPv4 Address
The IPv4 address that is assigned to this component link within The IPv4 address that is assigned to this component link within
the bundle. the bundle.
3.3.2. IPv6 Numbered Component Link Identification 3.3.3. IPv6 Numbered Component Link Identification
If the component link is identified with an IPv6 address, the IPv6 If the component link is identified with an IPv6 address, the IPv6
Numbered Component Link Identifier TLV is used. The TLV is formatted Numbered Component Link Identifier TLV is used. The TLV is formatted
as described in Section 3.1.2. The Type field has the value 4, and as described in Section 3.1.2. The Type field has the value 4, and
the Value field has the following content: the Value field has the following content:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
skipping to change at page 26, line 53 skipping to change at page 26, line 53
[OSPF-TI] Lindem, A., Roy, A., and Mirtorabi, S., "OSPF Transport [OSPF-TI] Lindem, A., Roy, A., and Mirtorabi, S., "OSPF Transport
Instance Extensions", draft-acee-ospf-transport-instance, Instance Extensions", draft-acee-ospf-transport-instance,
work in progress. work in progress.
[OSPFv2-MI] Lindem, A., Roy, A., and Mirtorabi, S., "OSPF Multi- [OSPFv2-MI] Lindem, A., Roy, A., and Mirtorabi, S., "OSPF Multi-
Instance Extensions", draft-acee-ospf-multi-instance, work Instance Extensions", draft-acee-ospf-multi-instance, work
in progress. in progress.
[PCE-LAYER] Oki, E. (Ed.), "PCC-PCE Communication and PCE Discovery [PCE-LAYER] Oki, E. (Ed.), "PCC-PCE Communication and PCE Discovery
Requirements for Inter-Layer Traffic Engineering", draft- Requirements for Inter-Layer Traffic Engineering",
ietf-pce-inter-layer-req, (work in progress). draft-ietf-pce-inter-layer-req, work in progress.
8. Editors' Addresses 8. Editors' Addresses
Kohei Shiomoto Kohei Shiomoto
NTT Network Service Systems Laboratories NTT Network Service Systems Laboratories
3-9-11 Midori 3-9-11 Midori
Musashino, Tokyo 180-8585 Musashino, Tokyo 180-8585
Japan Japan
Phone: +81 422 59 4402 Phone: +81 422 59 4402
Email: shiomoto.kohei@lab.ntt.co.jp Email: shiomoto.kohei@lab.ntt.co.jp
 End of changes. 7 change blocks. 
64 lines changed or deleted 64 lines changed or added

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