Re: [L1vpn] Re: I-D ACTION:draft-ietf-l1vpn-framework-01.txt

Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp> Wed, 11 January 2006 02:44 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EwVxy-0001ee-C0; Tue, 10 Jan 2006 21:44:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EwVxw-0001eZ-ED for l1vpn@megatron.ietf.org; Tue, 10 Jan 2006 21:44:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03939 for <l1vpn@ietf.org>; Tue, 10 Jan 2006 21:42:39 -0500 (EST)
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwW4k-0002BC-58 for l1vpn@ietf.org; Tue, 10 Jan 2006 21:51:03 -0500
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id k0B2hkpY001051; Wed, 11 Jan 2006 11:43:47 +0900 (JST)
Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id k0B2hkFi005793; Wed, 11 Jan 2006 11:43:46 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id k0B2hjbg020454; Wed, 11 Jan 2006 11:43:45 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id k0B2hjlu008468; Wed, 11 Jan 2006 11:43:45 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id k0B2hic1029990; Wed, 11 Jan 2006 11:43:44 +0900 (JST)
Received: from imf.m.ecl.ntt.co.jp (imf.m.ecl.ntt.co.jp [129.60.5.230]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id k0B2hiO3029987; Wed, 11 Jan 2006 11:43:44 +0900 (JST)
Received: from TAKEDA_PANA.lab.ntt.co.jp ([129.60.80.92]) by imf.m.ecl.ntt.co.jp (8.13.4/8.13.4) with ESMTP id k0B2heRR006428; Wed, 11 Jan 2006 11:43:43 +0900 (JST)
Message-Id: <5.1.1.9.2.20060111113751.06635cb0@imf.m.ecl.ntt.co.jp>
X-Sender: tt043@imf.m.ecl.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr3
Date: Wed, 11 Jan 2006 11:43:30 +0900
To: Dimitri.Papadimitriou@alcatel.be
From: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
Subject: Re: [L1vpn] Re: I-D ACTION:draft-ietf-l1vpn-framework-01.txt
In-Reply-To: <OF649E52B9.BD75743F-ONC12570EC.003D4F98-C12570EC.003F0450@ netfr.alcatel.fr>
References: <20060104132949.37AE.TAKEDA.TOMONORI@lab.ntt.co.jp>
Mime-Version: 1.0
X-Spam-Score: 0.6 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: l1vpn@ietf.org
X-BeenThere: l1vpn@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 1 Virtual Private Networks <l1vpn.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@lists.ietf.org>
List-Help: <mailto:l1vpn-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0693480162=="
Sender: l1vpn-bounces@lists.ietf.org
Errors-To: l1vpn-bounces@lists.ietf.org

Hi Dimitri,

Thanks for reading the document.

Please see in-line.

At 12:28 06/01/04 +0100, Dimitri.Papadimitriou@alcatel.be wrote:

hi tomonori

i probably miss it but what has been added concerning P2MP aspects ?

Near the end of section 4.1, it says:

   This document does not preclude other advanced services and topology
   support, such as point-to-multipoint (P2MP) services, as part of the
   Layer 1 services, but these are for further study.

concerning section 11 on 

o Performance management

    The provider network MUST support performance management, such as
    bit error rate per VPN connections, associated with customers.


should include a sub-section on 1) SLA monitoring (SLS parameters) 2) perf. monitoring (perf. metrics associated to the SLA) and 3) additionally a specific sub-section could be added on the monitoring of parameters related to the SP's equipment/elements/etc. providing the VPN service but not directly associated to the SLA

I think you are correct. I missed these points but they are important and should be included in the draft. I will incorporate them in the next revision.


Thanks,
Tomonori

thanks,
- dimitri.




Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>
Sent by: l1vpn-bounces@lists.ietf.org

04/01/2006 05:37        
        To:        l1vpn@ietf.org
        cc:       
        Subject:        [L1vpn] Re: I-D ACTION:draft-ietf-l1vpn-framework-01.txt


Hi,

We have submitted the update of L1VPN framework and requirement I-D.

Here is a list of major changes (based on discusssion in the last IETF
and on the mailing list).
- Addition of scheduling service as one deployment scenario (section 4.5.2)
- Addition of recovery aspects (section 9)
- Addition of control plane connectivity between CEs (section 10)
- Addition of manageability considerations (section 11)
- Addition of P2MP aspects (section 4)
- Change of the term "optical" to "layer 1" (section 4.2)

Comments are appreciated.

Thanks,
Tomonori

On Tue, 03 Jan 2006 15:50:01 -0500
Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Layer 1 Virtual Private Networks Working Group of the IETF.
>
>                  Title                                  : Framework and Requirements for Layer 1 Virtual Private Networks
>                  Author(s)                 : T. Takeda
>                  Filename                 : draft-ietf-l1vpn-framework-01.txt
>                  Pages                                  : 32
>                  Date                                  : 2006-1-3
>                 
> This document provides a framework and service level requirements
>    for Layer 1 Virtual Private Networks (L1VPNs). This framework is
>    intended to aid in developing and standardizing protocols and
>    mechanisms to support interoperable L1VPNs.
>
>    The document examines motivations for L1VPNs, high level (service
>    level) requirements, and outlines some of the architectural models
>    that might be used to build L1VPNs.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-01.txt" rel="nofollow">http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-framework-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" rel="nofollow">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-l1vpn-framework-01.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html" rel="nofollow">http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel="nofollow">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-l1vpn-framework-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.


_______________________________________________
L1vpn mailing list
L1vpn@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/l1vpn" rel="nofollow">https://www1.ietf.org/mailman/listinfo/l1vpn
_______________________________________________
L1vpn mailing list
L1vpn@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/l1vpn