The MPLS WG Archive

["LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@orange-ft.com>]

Hi folks

Here are the majors changes in this new revision:

-One mandatory requirement added in section 5.4: Leaf Addition/Removal MUST not impact data transfer towards other leaves;

-Section 5.8.2 and 5.8.3 have been reformulated to account for the tension between packet loss and packet duplication during rerouting; 

-Section 6.1: Detailed requirements for MP2MP LSPs have been added;

-Section 7.1: The controversial text (the solution SHOULD not require deploying an additional routing protocol...) has been removed and replaced by  "the P2MP LDP mechanism SHOULD be designed with as key objective to minimize the additional amount of state and additional processing required in the network..."

-Edits suggested by Ben have been included;

-And also minor edits for the sake of clarity.

We are waiting for your comments on this new version, particularly on the above points.

Regards,

JL

> -----Message d'origine-----
> De : Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> Envoyé : vendredi 23 juin 2006 00:50
> À : i-d-announce@ietf.org
> Cc : mpls@lists.ietf.org
> Objet : [mpls] I-D ACTION:draft-ietf-mpls-mp-ldp-reqs-01.txt 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Multiprotocol Label 
> Switching Working Group of the IETF.
> 
> 	Title		: Requirements for point-to-multipoint 
>                           extensions to the Label 
> Distribution Protocol
> 	Author(s)	: J. Le Roux, et al.
> 	Filename	: draft-ietf-mpls-mp-ldp-reqs-01.txt
> 	Pages		: 17
> 	Date		: 2006-6-22
> 	
> This document lists a set of functional requirements for Label 
>    Distribution Protocol (LDP) extensions for setting up point-to-
>    multipoint (P2MP) Label Switched Paths (LSP), in order to deliver 
>    point-to-multipoint applications over a Multi Protocol Label 
>    Switching (MPLS) infrastructure. It is intended that 
> solutions that 
>    specify LDP procedures for setting up P2MP LSP satisfy these 
>    requirements.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-mp-ldp-reqs-01.txt
> 
> To remove yourself from the I-D Announcement list, send a 
> message to i-d-announce-request@ietf.org with the word 
> unsubscribe in the body of the message.  
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login 
> with the username "anonymous" and a password of your e-mail 
> address. After logging in, type "cd internet-drafts" and then
> 	"get draft-ietf-mpls-mp-ldp-reqs-01.txt".
> 
> A list of Internet-Drafts directories can be found in 
> http://www.ietf.org/shadow.html or 
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-mpls-mp-ldp-reqs-01.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant 
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls