Diff: draft-ietf-mpls-crldp-unnum-06.txt - draft-ietf-mpls-crldp-unnum-07.txt

	draft-ietf-mpls-crldp-unnum-06.txt	draft-ietf-mpls-crldp-unnum-07.txt

	Network Working Group Kireeti Kompella	Network Working Group Kireeti Kompella
	Internet Draft Juniper Networks	Internet Draft Juniper Networks

	Expiration Date: December 2002 Yakov Rekhter	Expiration Date: January 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-06.txt	draft-ietf-mpls-crldp-unnum-07.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 1, line 37	skipping to change at page 1, line 37
	material or to cite them other than as ``work in progress.''	material or to cite them other than as ``work in progress.''

	The list of current Internet-Drafts can be accessed at	The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt	http://www.ietf.org/ietf/1id-abstracts.txt

	The list of Internet-Draft Shadow Directories can be accessed at	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.	http://www.ietf.org/shadow.html.

	2. Abstract	2. Abstract


	Current signalling used by MPLS TE doesn't provide support for	Current signalling used by Multi-Protocol Label Switching Traffic
	unnumbered links. This document defines procedures and extensions to	Engineering (MPLS TE) doesn't provide support for unnumbered links.
	CR-LDP, one of the MPLS TE signalling protocols, that are needed in	This document defines procedures and extensions to Constraint-Routing
	order to support unnumbered links.	Label Distribution Protocol (CR-LDP), one of the MPLS TE signalling
		protocols, that are needed in order to support unnumbered links.

	3. Overview	3. Overview

	Supporting MPLS TE over unnumbered links (i.e., links that do not	Supporting MPLS TE over unnumbered links (i.e., links that do not
	have IP addresses) involves two components: (a) the ability to carry	have IP addresses) involves two components: (a) the ability to carry
	(TE) information about unnumbered links in IGP TE extensions (ISIS or	(TE) information about unnumbered links in IGP TE extensions (ISIS or
	OSPF), and (b) the ability to specify unnumbered links in MPLS TE	OSPF), and (b) the ability to specify unnumbered links in MPLS TE
	signalling. The former is covered in [GMPLS-ISIS, GMPLS-OSPF]. The	signalling. The former is covered in [GMPLS-ISIS, GMPLS-OSPF]. The
	focus of this document is on the latter.	focus of this document is on the latter.


	skipping to change at page 4, line 19	skipping to change at page 4, line 19
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\|0\|0\| Type \| Length \|	\|0\|0\| Type \| Length \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\| LSR's Router ID \|	\| LSR's Router ID \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\| Interface ID (32 bits) \|	\| Interface ID (32 bits) \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

	6. Signalling Unnumbered Links in EROs	6. Signalling Unnumbered Links in EROs


	A new subobject of the Explicit Route Object (ERO) is used to specify	A new Type of ER-Hop TLV of the Explicit Route Object (ERO) is used
	unnumbered links. This subobject has the following format:	to specify unnumbered links. This Type is called Unnumbered
		Interface ID, and has the following format:


	Figure 2: Unnumbered Interface ID Subobject	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 \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\| Router ID \|	\| Router ID \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

	skipping to change at page 5, line 10	skipping to change at page 5, line 11
	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.


	6.2. Processing the ERO object	6.2. Processing the ERO


	The Unnumbered Interface ID subobject 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 subobject, and if the node has an	to the Router ID field in the Unnumbered Interface ID ER-Hop, and if
	(unnumbered) link or an (unnumbered) Forwarding Adjacency whose local	the node has an (unnumbered) link or an (unnumbered) Forwarding
	identifier (from that node's point of view) is equal to the value	Adjacency whose local identifier (from that node's point of view) is
	carried in the Interface ID field of the subobject.	equal to the value carried in the Interface ID field of the
		Unnumbered Interface ID ER-Hop.

	With this in mind, the ERO processing in the presence of the	With this in mind, the ERO processing in the presence of the

	Unnumbered Interface ID subobject follows the rules specified in	Unnumbered Interface ID ER-Hop follows the rules specified in section
	section 4.8.1 of [CR-LDP].	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 ERO processing, or to be more precise, as part of the
	next hop selection, if the outgoing link is unnumbered, the REQUEST	next hop selection, if the outgoing link is unnumbered, the REQUEST
	message that the node sends to the next hop MUST include the IF_ID	message that the node sends to the next hop MUST include the IF_ID
	TLV, with the IP address field of that TLV set to the Router ID of	TLV, with the IP address field of that TLV set to the Router ID of
	the node, and the Interface ID field of that TLV set to the	the node, and the Interface ID field of that TLV set to the
	identifier assigned to the link by the node.	identifier assigned to the link by the node.


	7. Security Considerations	7. IANA Considerations


	This document raises no new security concerns for CR-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
		associated with the CR-LDP in the range 0x0800 - 0x08FF.


	8. Acknowledgments	Following the policies outlined in [IANA], TLV types in this range
		are allocated through an IETF Consensus action.

		This document makes the following assignments:

		TLV Type
		-------------------------------------- ----------
		UNNUMBERED_INTERFACE_ID 0x0805
		LSP_TUNNEL_INTERFACE_ID 0x08??

		8. Security Considerations

		This document extends CR-LDP and raises no new security issues. CR-
		LDP inherits the same security mechanism described in Section 4.0 of
		[LDP] to protect against the introduction of spoofed TCP segments
		into LDP session connection streams.

		9. Acknowledgments

	Thanks to Rahul Aggarwal for his comments on the text. Thanks too to	Thanks to Rahul Aggarwal for his comments on the text. Thanks too to

	Bora Akyol and Vach Kompella.	Bora Akyol, Vach Kompella, and George Swallow.


	9. References	10. References


	9.1. Normative references	10.1. Normative references

	[CR-LDP] Jamoussi, B., editor, "Constraint-Based LSP Setup using	[CR-LDP] Jamoussi, B., editor, "Constraint-Based LSP Setup using
	LDP", RFC3212, December 2001	LDP", RFC3212, December 2001

	[GMPLS-SIG] Ashwood, P., et al., "Generalized MPLS - Signalling	[GMPLS-SIG] Ashwood, P., et al., "Generalized MPLS - Signalling
	Functional Description", draft-ietf-generalized-mpls-	Functional Description", draft-ietf-generalized-mpls-
	signalling-08.txt	signalling-08.txt

	[GMPLS-CRLDP] Ashwood, P., et al., "Generalized MPLS Signaling - CR-	[GMPLS-CRLDP] Ashwood, P., et al., "Generalized MPLS Signaling - CR-
	LDP Extensions", draft-ietf-mpls-generalized-cr-ldp-06.txt	LDP Extensions", draft-ietf-mpls-generalized-cr-ldp-06.txt


	9.2. Non-normative references	[LDP] Andersson, Loa, et al., "LDP Specification" RFC3036, January
		2001

		10.2. Non-normative references

	[LINK-BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., "Link	[LINK-BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., "Link
	Bundling in MPLS Traffic Engineering", draft-kompella-mpls-	Bundling in MPLS Traffic Engineering", draft-kompella-mpls-
	bundle-05.txt (work in progress)	bundle-05.txt (work in progress)

	[LSP-HIER] Kompella, K., and Rekhter, Y., "LSP Hierarchy with MPLS	[LSP-HIER] Kompella, K., and Rekhter, Y., "LSP Hierarchy with MPLS
	TE", draft-ietf-mpls-lsp-hierarchy-02.txt (work in progress)	TE", draft-ietf-mpls-lsp-hierarchy-02.txt (work in progress)

	[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)

	skipping to change at page 6, line 34	skipping to change at page 7, line 4

	[LSP-HIER] Kompella, K., and Rekhter, Y., "LSP Hierarchy with MPLS	[LSP-HIER] Kompella, K., and Rekhter, Y., "LSP Hierarchy with MPLS
	TE", draft-ietf-mpls-lsp-hierarchy-02.txt (work in progress)	TE", draft-ietf-mpls-lsp-hierarchy-02.txt (work in progress)

	[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)


	10. Author Information	11. 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
	Juniper Networks, Inc.	Juniper Networks, Inc.
	1194 N. Mathilda Ave.	1194 N. Mathilda Ave.

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