[L1vpn] Fwd: I-D ACTION:draft-fedyk-l1vpn-basic-mode-00.txt

[Tomonori TAKEDA <[e-mail]>]

Hi Don, Yakov,

Nice to see the draft.

With chair hat off, please see my comments below.

1)  I am expecting that this draft specifies signaling mechanisms for L1VPN 
BM, and  auto-discovery/reachability exchange mechanisms will follow. It 
may depend on how discussion will go, but if this document specifies only 
signaling, we may want to consider to change the draft title.

2) I think this draft elaborates (or precisely specifies) signaling 
procedures based on GMPLS UNI. In GMPLS UNI, nesting is recommended to be 
used if VPN addressing realm is used, or contiguous may be used if the same 
addressing realm is used.

One comment is that stitching is developed in CCAMP since that time, and I 
believe stitching can be used in L1VPN BM as well. It would be nice to 
catch this point in the document.

Another comment is that in nesting or stitching applications, it is not 
always necessary to establish FA LSP or LSP segment dynamically. It would 
be possible to pre-configure FA LSP or LSP segment. Does this also apply to 
L1VPN BM?

3) It would be good to see that recovery aspects are covered in future revisions.
- PE-PE recovery: Is this more like segment recovery or link protection?
- CE-CE recovery: I guess how to calculate CE-CE disjoint paths is for 
further study. (beyond basic mode?)

4) Section 2,

       "(2) GMPLS RSVP-TE is used not just as a signaling mechanism, but 
also as a routing mechanism
         within the provider network."

   I guess you don't mean RSVP-TE is used as a routing mechanism?


Thanks,
Tomonori

>To: [e-mail]
>From: [e-mail]
>Date: Wed, 19 Oct 2005 15:50:02 -0400
>X-Spam-Score: 0.4 (/)
>X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
>Subject: I-D ACTION:draft-fedyk-l1vpn-basic-mode-00.txt
>X-BeenThere: [e-mail]
>X-Mailman-Version: 2.1.5
>Reply-To: [e-mail]
>List-Id: i-d-announce.ietf.org
>List-Unsubscribe: 
><https://www1.ietf.org/mailman/listinfo/i-d-announce>,<mailto:[e-mail]?subject=unsubscribe>
>List-Post: <mailto:[e-mail]>
>List-Help: <mailto:[e-mail]?subject=help>
>List-Subscribe: 
><https://www1.ietf.org/mailman/listinfo/i-d-announce>,<mailto:[e-mail]?subject=subscribe>
>Sender: [e-mail]
>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>         Title           : Layer 1 VPN Basic Mode
>         Author(s)       : D. Fedyk, et al.
>         Filename        : draft-fedyk-l1vpn-basic-mode-00.txt
>         Pages           : 19
>         Date            : 2005-10-19
>
>         This draft describes the basic mode of Layer 1 VPNs (L1VPN BM)
>         that is port based VPNs. In L1VPN BM, the basic unit of service
>         is a Label Switched Path (LSP) between a pair of customer ports
>         within a given VPN port-topology. This draft defines the
>         operational model using either provisioning or a VPN auto-
>         discovery mechanism and the signaling extensions for the L1VPN
>         BM. This draft uses BGP as an example of the auto-discovery
>         mechanism.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-fedyk-l1vpn-basic-mode-00.txt
>
>To remove yourself from the I-D Announcement list, send a message to
>[e-mail] 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-fedyk-l1vpn-basic-mode-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:
>         [e-mail].
>In the body type:
>         "FILE /internet-drafts/draft-fedyk-l1vpn-basic-mode-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.
>
>Content-Type: text/plain
>Content-ID: <[e-mail]>
>
>ENCODING mime
>FILE /internet-drafts/draft-fedyk-l1vpn-basic-mode-00.txt
>
>
><ftp://ftp.ietf.org/internet-drafts/draft-fedyk-l1vpn-basic-mode-00.txt>
>_______________________________________________
>I-D-Announce mailing list
>[e-mail]
>https://www1.ietf.org/mailman/listinfo/i-d-announce


_______________________________________________
L1vpn mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/l1vpn