Re: I-D ACTION:draft-takacs-asym-bw-lsp-00.txt

[Dimitri.Papadimitriou@alcatel-lucent.be]

let's go back to basic

per RFC 3471

"4. Bidirectional LSPs

   This section defines direct support of bidirectional LSPs.  Support
   is defined for LSPs that have the same traffic engineering
   requirements including fate sharing, protection and restoration,
   LSRs, and resource requirements (e.g., latency and jitter) in each
   direction."

what does it mean in practice that Path msg can carry a TSPEC and the 
Resv a FLOWSPEC, and still allow for establishment of two data paths
(upstream & downstream)

[...]

 "With bidirectional LSPs both the downstream and upstream data paths,
   i.e., from initiator to terminator and terminator to initiator, they
   are established using a single set of signaling messages."

in brief, a single msg exchange for two data paths (upstream & downstream)

but if you change the initial condition and still be somehow respectful
of the RSVP operation

the path msg shall carry an (upstream) FLOWSPEC and (downstream) TSPEC
and not a downstream TSPEC and a (default) TSPEC, but now you got the 
real issue of carrying a FLOWSPEC in a Path msg ??? 

hence, better forget about this idea and look at a simple extensions
consisting in linking two uni-directional LSP with an association 
oject

ps: the document includes in many places "marketing-like" statements 
completely - examples

" The limitation of symmetrical resource requirements may pose 
   difficulties for operators to efficiently support the services 
   foreseen for next generation networks."

pls give us a break with all the hype and hubub about "services 
foreseen for next generation networks" 

"Means must be provided by higher 
   layer entities, e.g., the network management system (NMS), to 
   correlate the LSPs not just from RSVP-TE but also from an OAM point 
   of view. "

which OAM ??? never heard someone complaining when using MPLS-BFD
where is the proof point ?

"Additionally, translation functionality may be required to 
   provide operators with a service oriented bidirectional abstraction 
   hiding the complex control plane operation."

could you speak with an IETF language please, this sentence just 
mean nothing

thanks,
-d.




Internet-Drafts@ietf.org
27/02/2007 21:50
Please respond to internet-drafts
 
        To:     i-d-announce@ietf.org
        cc: 
        Subject:        I-D ACTION:draft-takacs-asym-bw-lsp-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


                 Title                           : GMPLS RSVP-TE extension 
in support of bidirectional LSPs with 
                 Author(s)               : A. Takacs, et al.
                 Filename                : draft-takacs-asym-bw-lsp-00.txt
                 Pages                           : 8
                 Date                            : 2007-2-27
 
   GMPLS provides general connection control functionality supporting 
   different network technologies. This memo specifies a further 
   generalization to support bidirectional LSPs with asymmetric 
   requirements. The extension improves the flexibility of bidirectional 
   LSP establishment and at the same time simplifies the control and 
   management of asymmetric services. 


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-takacs-asym-bw-lsp-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-takacs-asym-bw-lsp-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-takacs-asym-bw-lsp-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.
ftp://anonymous@ftp.ietf.org/internet-drafts/draft-takacs-asym-bw-lsp-00.txt
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce