draft-ietf-mpls-crldp-unnum-08.txt   draft-ietf-mpls-crldp-unnum-09.txt 
Network Working Group Kireeti Kompella Network Working Group Kireeti Kompella
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: April 2003 Yakov Rekhter Expiration Date: April 2003 Yakov Rekhter
Juniper Networks Juniper Networks
Alan Kullberg Alan Kullberg
NetPlane Systems NetPlane Systems
Signalling Unnumbered Links in CR-LDP Signalling Unnumbered Links in CR-LDP
draft-ietf-mpls-crldp-unnum-08.txt draft-ietf-mpls-crldp-unnum-09.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 3, line 6 skipping to change at page 3, line 6
Consider an (unnumbered) link between LSRs A and B. LSR A chooses an Consider an (unnumbered) link between LSRs A and B. LSR A chooses an
idenfitier for that link. So is LSR B. From A's perspective we refer idenfitier for that link. So is LSR B. From A's perspective we refer
to the identifier that A assigned to the link as the "link local to the identifier that A assigned to the link as the "link local
identifier" (or just "local identifier"), and to the identifier that identifier" (or just "local identifier"), and to the identifier that
B assigned to the link as the "link remote identifier" (or just B assigned to the link as the "link remote identifier" (or just
"remote identifier"). Likewise, from B's perspective the identifier "remote identifier"). Likewise, from B's perspective the identifier
that B assigned to the link is the local identifier, and the that B assigned to the link is the local identifier, and the
identifier that A assigned to the link is the remote identifier. identifier that A assigned to the link is the remote identifier.
In the context of this document the term "Router ID" refers to the
"Router Address" as defined in [OSPF-TE], or "Traffic Engineering
Router ID" as defined in [ISIS-TE].
This section is equally applicable to the case of unnumbered This section is equally applicable to the case of unnumbered
component links (see [LINK-BUNDLE]). component links (see [LINK-BUNDLE]).
6. Unnumbered Forwarding Adjacencies 6. Unnumbered Forwarding Adjacencies
If an LSR that originates an LSP advertises this LSP as an unnumbered If an LSR that originates an LSP advertises this LSP as an unnumbered
Forwarding Adjacency in IS-IS or OSPF (see [LSP-HIER]), or the LSR Forwarding Adjacency in IS-IS or OSPF (see [LSP-HIER]), or the LSR
uses the Forwarding Adjacency formed by this LSP as an unnumbered uses the Forwarding Adjacency formed by this LSP as an unnumbered
component link of a bundled link (see [LINK-BUNDLE]), the LSR MUST component link of a bundled link (see [LINK-BUNDLE]), the LSR MUST
allocate an identifier to that Forwarding Adjacency (just like for allocate an identifier to that Forwarding Adjacency (just like for
skipping to change at page 3, line 30 skipping to change at page 3, line 34
to the identifier that the LSR allocated to the Forwarding Adjacency. to the identifier that the LSR allocated to the Forwarding Adjacency.
If the REQUEST message contains the LSP_TUNNEL_INTERFACE_ID TLV, then If the REQUEST message contains the LSP_TUNNEL_INTERFACE_ID TLV, then
the tail-end LSR MUST allocate an identifier to that Forwarding the tail-end LSR MUST allocate an identifier to that Forwarding
Adjacency (just like for any other unnumbered link). Furthermore, Adjacency (just like for any other unnumbered link). Furthermore,
the MAPPING message for the LSP MUST contain an the MAPPING message for the LSP MUST contain an
LSP_TUNNEL_INTERFACE_ID TLV, with the LSR's Router ID set to the LSP_TUNNEL_INTERFACE_ID TLV, with the LSR's Router ID set to the
tail-end's Router ID, and the Interface ID set to the identifier tail-end's Router ID, and the Interface ID set to the identifier
allocated by the tail-end LSR. allocated by the tail-end LSR.
For the purpose of processing the ERO and the Interface ID TLV, an For the purpose of processing the Explicit Route TLV and the
unnumbered Forwarding Adjacency is treated as an unnumbered (TE) link Interface ID TLV, an unnumbered Forwarding Adjacency is treated as an
or an unnumbered component link as follows. The LSR that originates unnumbered (TE) link or an unnumbered component link as follows. The
the Adjacency sets the link local identifier for that link to the LSR that originates the Adjacency sets the link local identifier for
value that the LSR allocates to that Forwarding Adjacency, and the that link to the value that the LSR allocates to that Forwarding
link remote identifier to the value carried in the Interface ID field Adjacency, and the link remote identifier to the value carried in the
of the Reverse Interface ID TLV (for the definition of Reverse Interface ID field of the Reverse Interface ID TLV (for the
Interface ID TLV see below). The LSR that is a tail-end of that definition of Reverse Interface ID TLV see below). The LSR that is a
Forwarding Adjacency sets the link local identifier for that link to tail-end of that Forwarding Adjacency sets the link local identifier
the value that the LSR allocates to that Forwarding Adjacency, and for that link to the value that the LSR allocates to that Forwarding
the link remote identifier to the value carried in the Interface ID Adjacency, and the link remote identifier to the value carried in the
field of the Forward Interface ID TLV (for the definition of Forward Interface ID field of the Forward Interface ID TLV (for the
Interface ID see below). definition of Forward Interface ID see below).
6.1. LSP_TUNNEL_INTERFACE_ID TLV 6.1. LSP_TUNNEL_INTERFACE_ID TLV
The LSP_TUNNEL_INTERFACE ID TLV has Type to be determined by IETF The LSP_TUNNEL_INTERFACE ID TLV has Type to be determined by IETF
consensus and length 8. The format is given below. consensus and length 8. The format is given below.
Figure 1: LSP_TUNNEL_INTERFACE_ID TLV Figure 1: LSP_TUNNEL_INTERFACE_ID TLV
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
skipping to change at page 4, line 27 skipping to change at page 4, line 27
| LSR's Router ID | | LSR's Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID (32 bits) | | Interface ID (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This TLV can optionally appear in either a REQUEST message or a This TLV can optionally appear in either a REQUEST message or a
MAPPING message. In the former case, we call it the "Forward MAPPING message. In the former case, we call it the "Forward
Interface ID" for that LSP; in the latter case, we call it the Interface ID" for that LSP; in the latter case, we call it the
"Reverse Interface ID" for the LSP. "Reverse Interface ID" for the LSP.
7. Signalling Unnumbered Links in EROs 7. Signalling Unnumbered Links in Explicit Route TLV
A new Type of ER-Hop TLV of the Explicit Route Object (ERO) is used A new Type of ER-Hop TLV of the Explicit Route TLV is used to specify
to specify unnumbered links. This Type is called Unnumbered unnumbered links. This Type is called Unnumbered Interface ID, and
Interface ID, and has the following format: has the following format:
Figure 2: Unnumbered Interface ID Figure 2: Unnumbered Interface ID
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|0| Type = 0x0805 | Length = 12 | |0|0| Type = 0x0805 | Length = 12 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L| Reserved | |L| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 22 skipping to change at page 5, line 22
follows. The LSR must have information about the identifiers assigned follows. The LSR must have information about the identifiers assigned
by its neighbors to the unnumbered links between the neighbors and by its neighbors to the unnumbered links between the neighbors and
the LSR. The LSR uses this information to find a link with tuple the LSR. The LSR uses this information to find a link with tuple
<Router ID, local identifier> matching the tuple <IP Address, <Router ID, local identifier> matching the tuple <IP Address,
Interface ID> carried in the IF_INDEX TLV. If the matching tuple is Interface ID> carried in the IF_INDEX TLV. If the matching tuple is
found, the match identifies the link for which the LSR has to perform found, the match identifies the link for which the LSR has to perform
label allocation. label allocation.
Otherwise, the LSR SHOULD return an error. Otherwise, the LSR SHOULD return an error.
7.2. Processing the ERO 7.2. Processing the Unnumbered Interface ID ER-Hop TLV
The Unnumbered Interface ID ER-Hop is defined to be a part of a The Unnumbered Interface ID ER-Hop is defined to be a part of a
particular abstract node if that node has the Router ID that is equal particular abstract node if that node has the Router ID that is equal
to the Router ID field in the Unnumbered Interface ID ER-Hop, and if to the Router ID field in the Unnumbered Interface ID ER-Hop, and if
the node has an (unnumbered) link or an (unnumbered) Forwarding the node has an (unnumbered) link or an (unnumbered) Forwarding
Adjacency whose local identifier (from that node's point of view) is Adjacency whose local identifier (from that node's point of view) is
equal to the value carried in the Interface ID field of the equal to the value carried in the Interface ID field of the
Unnumbered Interface ID ER-Hop. Unnumbered Interface ID ER-Hop.
With this in mind, the ERO processing in the presence of the With this in mind, the Explicit Route TLV processing in the presence
Unnumbered Interface ID ER-Hop follows the rules specified in section of the Unnumbered Interface ID ER-Hop follows the rules specified in
4.8.1 of [CR-LDP]. section 4.8.1 of [CR-LDP].
As part of the ERO processing, or to be more precise, as part of the As part of the Explicit Route TLV processing, or to be more precise,
next hop selection, if the outgoing link is unnumbered, the REQUEST as part of the next hop selection, if the outgoing link is
message that the node sends to the next hop MUST include the IF_ID unnumbered, the REQUEST message that the node sends to the next hop
TLV, with the IP address field of that TLV set to the Router ID of MUST include the IF_ID TLV, with the IP address field of that TLV set
the node, and the Interface ID field of that TLV set to the to the Router ID of the node, and the Interface ID field of that TLV
identifier assigned to the link by the node. set to the identifier assigned to the link by the node.
8. IANA Considerations 8. IANA Considerations
RFC3036 [LDP] defines the LDP TLV name space. RFC3212 [CD-LDP] RFC3036 [LDP] defines the LDP TLV name space. RFC3212 [CD-LDP]
further subdivides the range of RFC 3036 from that TLV space for TLVs further subdivides the range of RFC 3036 from that TLV space for TLVs
associated with the CR-LDP in the range 0x0800 - 0x08FF. associated with the CR-LDP in the range 0x0800 - 0x08FF.
Following the policies outlined in [IANA], TLV types in this range Following the policies outlined in [IANA], TLV types in this range
are allocated through an IETF Consensus action. are allocated through an IETF Consensus action.
skipping to change at page 7, line 26 skipping to change at page 7, line 26
[LMP] Lang, J., Mitra, K., et al., "Link Management Protocol (LMP)", [LMP] Lang, J., Mitra, K., et al., "Link Management Protocol (LMP)",
draft-ietf-ccamp-lmp-03.txt (work in progress) draft-ietf-ccamp-lmp-03.txt (work in progress)
[GMPLS-ISIS] Kompella, K., Rekhter, Y., Banerjee, A. et al, "IS-IS [GMPLS-ISIS] Kompella, K., Rekhter, Y., Banerjee, A. et al, "IS-IS
Extensions in Support of Generalized MPLS", draft-ietf-isis-gmpls- Extensions in Support of Generalized MPLS", draft-ietf-isis-gmpls-
extensions-11.txt (work in progress) extensions-11.txt (work in progress)
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", draft-ietf-ccamp-ospf- Extensions in Support of Generalized MPLS", draft-ietf-ccamp-ospf-
gmpls-extensions-07.txt (work in progress) gmpls-extensions-07.txt (work in progress)
[OSPF-TE] Katz, D., Yeung, D., Kompella, K., "Traffic Engineering
Extensions to OSPF Version 2", draft-katz-yeung-ospf-traffic-07.txt
(work in progress)
[ISIS-TE] Li, T., Smit, H., "IS-IS extensions for Traffic
Engineering", draft-ietf-isis-traffic-03.txt (work in progress)
12. Author Information 12. Author Information
Kireeti Kompella Kireeti Kompella
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
e-mail: kireeti@juniper.net e-mail: kireeti@juniper.net
Yakov Rekhter Yakov Rekhter
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/