The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Comment on draft-ietf-mpls-crlsp-modify-02
Hi Olivier, You make a good point, and ideally this is what would be done. We would need to define the procedure for propagating the second Label Request (this is quite easy to define), since the current LDP spec allows the second LSR to say "I have a label for that FEC" and simply return a Label Mapping. Note, however, that it will not always be possible to provide the increased bandwidth using the same label. In this case the existing modify function will be required. Further, I don't believe there is anything in the modify draft that prohibits the use of the same label on both the initial and the modified LSP. Regards, Adrian -- Adrian Farrel mailto:af@dataconnection.com Network Convergence Group Data Connection Ltd., Chester, UK http://www.dataconnection.com/ Tel: +44 (0) 1244 313440 Fax: +44 (0) 1244 312422 >-----Original Message----- >From: Olivier Dugeon [mailto:Olivier.Dugeon@rd.francetelecom.fr] >Sent: Wednesday, October 11, 2000 8:54 AM >To: mpls@UU.NET >Subject: Comment on draft-ietf-mpls-crlsp-modify-02 > > >Hi all, > >In section 4.1 : "Ri assigns a new label for the Label Request >Message." > >I think this is necessary only for re-routing i.e. ER-TLV changes. For >over traffic parameters modification, i think it's preferable to keep >the existing label. Because the route doesn't change, it's more simple >to keep the existing label (which reflect the path of the LSPID) than >change label. Then, you doesn't need to send a Label Release Message. >But, to ensure a three-way handshake of the protocol, it must >be safe to >send a Notification Message instead of a Release Message in >this context >to confirm the modification by ingress LSR. > >In this fashion, crlsp modification is much closer than it can be >possible with RM Cells (Ressource Management Cells) in ATM network. > >In section 9 : > >Why references of crldp and ldp are not up to date ? Where i can find >draft-ash-qos-routing-00.txt ? is the same as >draft-ash-te-qos-routing-01.txt ? > >Thanks, > >Olivier >-- > FTR&D/DAC/CPN > Technopole Anticipa | mailto:Olivier.Dugeon@francetelecom.fr > 2, Avenue Pierre Marzin | Phone: +(33) 2 96 05 28 80 > F-22307 LANNION | Fax: +(33) 2 96 05 18 52 > |
|