The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] [mpls] Re: I-D ACTION:draft-xu-mpls-rsvp-te-bidirection-00.txt
Hi, Adrian, Thanks for your comments firstly. In contrast with the procedure of establishing a bidirectional TE tunnel defined in GMPLS draft [RFC 3473], there is no additional requirement on middle-hop LSRs here. The middle-hop LSRs only need to transit the unknown binding object. In addition, the modification of RSVP-TE is small relatively and the path of two opposite tunnel can be different, and there is no need for Path message to assign label. Bidirectional TE tunnel can support many purposes as follows: 1, be used as tunnel for VR-based VPN; 2, achieve LDP over TE easily; 3, interconnect two seperated routing domains via bidiretional TE tunnel, it is more flexible than IGP shortcut and adjacency as different routing protocols can be run in MPLS core domain and the seperated routing domains; 4, BFD can be deployed between the bidirectional TE interfaces to achieve fast switchover of hot standby LSP in case that the primary LSP is down. Best regards, Xiaohu Xu Email: xuxh@huawei.com ----- Original Message ----- From: "Adrian Farrel" <adrian@olddog.co.uk> To: <zhangle@huawei.com>; <xuxh@huawei.com> Sent: Wednesday, March 08, 2006 7:11 AM Subject: Fw: I-D ACTION:draft-xu-mpls-rsvp-te-bidirection-00.txt > Hi, > > Interesting draft, but can you tell me what is wrong with using the > existing extensions to RSVP-TE for bidirectional LSPs? See RFC3473. > > On the other hand, if you must associate to unidirectional LSPs with each > other, can you tell me what is wrong with using the existing Association > object? It was invented specifically to allow multiple LSPs to be > associated with each other. > > Thanks, > Adrian > ----- Original Message ----- > From: <Internet-Drafts@ietf.org> > To: <i-d-announce@ietf.org> > Sent: Tuesday, March 07, 2006 8:50 PM > Subject: I-D ACTION:draft-xu-mpls-rsvp-te-bidirection-00.txt > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > > > > Title : Bidirectional RSVP-TE Tunnel > > Author(s) : X. Xu, L. Zhang > > Filename : draft-xu-mpls-rsvp-te-bidirection-00.txt > > Pages : 8 > > Date : 2006-3-7 > > > > Through the binding of two unidirectional RSVP-TE tunnels established > > between a pair of LSRs destined to each other, a bidirectional RSVP- > > TE tunnel is formed. The bidirectional RSVP-TE tunnel can be used to > > establish L3VPN with virtual router technology. > > > > > > > > A URL for this Internet-Draft is: > > > http://www.ietf.org/internet-drafts/draft-xu-mpls-rsvp-te-bidirection-00.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-xu-mpls-rsvp-te-bidirection-00.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-xu-mpls-rsvp-te-bidirection-00.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. > > > > > -------------------------------------------------------------------------- > ------ > > > > _______________________________________________ > > I-D-Announce mailing list > > I-D-Announce@ietf.org > > https://www1.ietf.org/mailman/listinfo/i-d-announce > > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls |
|