draft-ietf-mpls-ldp-p2mp-03.txt		draft-ietf-mpls-ldp-p2mp-04.txt
	Network Working Group I. Minei (Editor)		Network Working Group I. Minei (Editor)
	Internet-Draft K. Kompella		Internet-Draft K. Kompella
	Intended status: Standards Track Juniper Networks		Intended status: Standards Track Juniper Networks
	Expires: January 10, 2008 I. Wijnands (Editor)		Expires: August 25, 2008 I. Wijnands (Editor)
	B. Thomas		B. Thomas
	Cisco Systems, Inc.		Cisco Systems, Inc.
	July 9, 2007		February 22, 2008
	Label Distribution Protocol Extensions for Point-to-Multipoint and		Label Distribution Protocol Extensions for Point-to-Multipoint and
	Multipoint-to-Multipoint Label Switched Paths		Multipoint-to-Multipoint Label Switched Paths
	draft-ietf-mpls-ldp-p2mp-03		draft-ietf-mpls-ldp-p2mp-04
	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 1, line 38		skipping to change at page 1, line 38
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	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.
	This Internet-Draft will expire on January 10, 2008.		This Internet-Draft will expire on August 25, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	This document describes extensions to the Label Distribution Protocol		This document describes extensions to the Label Distribution Protocol
	(LDP) for the setup of point to multi-point (P2MP) and multipoint-to-		(LDP) for the setup of point to multi-point (P2MP) and multipoint-to-
	multipoint (MP2MP) Label Switched Paths (LSPs) in Multi-Protocol		multipoint (MP2MP) Label Switched Paths (LSPs) in Multi-Protocol
	Label Switching (MPLS) networks. The solution relies on LDP without		Label Switching (MPLS) networks. The solution relies on LDP without
	requiring a multicast routing protocol in the network. Protocol		requiring a multicast routing protocol in the network. Protocol
	elements and procedures for this solution are described for building		elements and procedures for this solution are described for building
	such LSPs in a receiver-initiated manner. There can be various		such LSPs in a receiver-initiated manner. There can be various
	skipping to change at page 6, line 41		skipping to change at page 6, line 41
	context of the root node. The combination of (Root Node Address,		context of the root node. The combination of (Root Node Address,
	Opaque Value) uniquely identifies a P2MP LSP within the MPLS network.		Opaque Value) uniquely identifies a P2MP LSP within the MPLS network.
	The P2MP FEC Element is encoded as follows:		The P2MP FEC Element is encoded as follows:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|P2MP Type (TBD)| Address Family | Address Length|		|P2MP Type (TBD)| Address Family | Address Length|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Root Node Address |		~ Root Node Address ~
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Opaque Length | Opaque Value ... |		| Opaque Length | Opaque Value ... |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
	~ ~		~ ~
	| |		| |
	| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Type: The type of the P2MP FEC Element is to be assigned by IANA.		Type: The type of the P2MP FEC Element is to be assigned by IANA.
	skipping to change at page 26, line 35		skipping to change at page 26, line 35
	|1|0| LDP MP MBB Capability | Length = 1 |		|1|0| LDP MP MBB Capability | Length = 1 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|1| Reserved |		|1| Reserved |
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	If an LSR has not advertised that it is MBB capable, its LDP peers		If an LSR has not advertised that it is MBB capable, its LDP peers
	MUST NOT send it messages which include MBB parameters. If an LSR		MUST NOT send it messages which include MBB parameters. If an LSR
	receives a Label Mapping message with a MBB parameter from downstream		receives a Label Mapping message with a MBB parameter from downstream
	LSR-D and its upstream LSR-U has not advertised that it is MBB		LSR-D and its upstream LSR-U has not advertised that it is MBB
	capable, the LSR MUST send an MBB notification immediatly to LSR-U		capable, the LSR MUST send an MBB notification immediatly to LSR-U
	(see Section Section 8.4). If this happens an MBB MP LSP will not be		(see Section 8.4). If this happens an MBB MP LSP will not be
	established, but normal a MP LSP will be the result.		established, but normal a MP LSP will be the result.
	8.4. The MBB procedures		8.4. The MBB procedures
	8.4.1. Terminology		8.4.1. Terminology
	1. MBB LSP <X, Y>: A P2MP or MP2MP Make Before Break (MBB) LSP entry		1. MBB LSP <X, Y>: A P2MP or MP2MP Make Before Break (MBB) LSP entry
	with Root Node Address X and Opaque Value Y.		with Root Node Address X and Opaque Value Y.
	2. A(N, L): An Accepting element that consists of an upstream		2. A(N, L): An Accepting element that consists of an upstream
	skipping to change at page 30, line 21		skipping to change at page 30, line 21
	This document creates a new name space (the LDP MP Status Value		This document creates a new name space (the LDP MP Status Value
	Element type) that is to be managed by IANA, and the allocation of		Element type) that is to be managed by IANA, and the allocation of
	the value 1 for the type of MBB Status.		the value 1 for the type of MBB Status.
	11. Acknowledgments		11. Acknowledgments
	The authors would like to thank the following individuals for their		The authors would like to thank the following individuals for their
	review and contribution: Nischal Sheth, Yakov Rekhter, Rahul		review and contribution: Nischal Sheth, Yakov Rekhter, Rahul
	Aggarwal, Arjen Boers, Eric Rosen, Nidhi Bhaskar, Toerless Eckert,		Aggarwal, Arjen Boers, Eric Rosen, Nidhi Bhaskar, Toerless Eckert,
	George Swallow, Jin Lizhong and Vanson Lim.		George Swallow, Jin Lizhong, Vanson Lim and Adrian Farrel.
	12. Contributing authors		12. Contributing authors
	Below is a list of the contributing authors in alphabetical order:		Below is a list of the contributing authors in alphabetical order:
	Shane Amante		Shane Amante
	Level 3 Communications, LLC		Level 3 Communications, LLC
	1025 Eldorado Blvd		1025 Eldorado Blvd
	Broomfield, CO 80021		Broomfield, CO 80021
	US		US
	skipping to change at page 34, line 7		skipping to change at page 34, line 7
	Bob Thomas		Bob Thomas
	Cisco Systems, Inc.		Cisco Systems, Inc.
	300 Beaver Brook Road		300 Beaver Brook Road
	Boxborough 01719		Boxborough 01719
	US		US
	Email: rhthomas@cisco.com		Email: rhthomas@cisco.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
End of changes. 9 change blocks.
	9 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/