Re: [OPS-AREA] FW: I-D Action:draft-gray-mpls-tp-nm-req-02.txt

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 13 May 2009 09:48 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC84B3A6A5B; Wed, 13 May 2009 02:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.205
X-Spam-Level:
X-Spam-Status: No, score=-2.205 tagged_above=-999 required=5 tests=[AWL=-0.206, BAYES_00=-2.599, J_CHICKENPOX_35=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sVsrwnThzYt6; Wed, 13 May 2009 02:48:01 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id D5AF73A67F4; Wed, 13 May 2009 02:47:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,186,1241409600"; d="scan'208";a="161170534"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 13 May 2009 05:49:29 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 May 2009 05:49:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 May 2009 11:49:05 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401693ED9@307622ANEX5.global.avaya.com>
In-Reply-To: <00b401c9d39c$b50c2240$0601a8c0@allison>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPS-AREA] FW: I-D Action:draft-gray-mpls-tp-nm-req-02.txt
Thread-Index: AcnTpS4seph7DhaeRKyVJMsAYbi90wACjyFw
References: <EDC652A26FB23C4EB6384A4584434A04012FA3DE@307622ANEX5.global.avaya.com> <00b401c9d39c$b50c2240$0601a8c0@allison>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "tom.petch" <cfinss@dial.pipex.com>, ops-dir@ietf.org, "ops-area (IETF)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] FW: I-D Action:draft-gray-mpls-tp-nm-req-02.txt
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2009 09:48:02 -0000

Thanks, Tom. I agree that all the MPLS-TP space raises some interesting
operational issues. It's good that OAM requirements have gotten their
dedicated I-D, together with the other MPLS-TP requirements. At this
phase I would suggest that folks who are interested in this work provide
their comments as part of the respective WG process. When the documents
will reach the IETF Last Call phase I suggest that we assign dedicated
reviewers from OPS-DIR (and of course all other inputs will be welcome).


Dan


> -----Original Message-----
> From: tom.petch [mailto:cfinss@dial.pipex.com] 
> Sent: Wednesday, May 13, 2009 10:23 AM
> To: Romascanu, Dan (Dan); ops-dir@ietf.org; ops-area (IETF)
> Subject: Re: [OPS-AREA] FW: I-D 
> Action:draft-gray-mpls-tp-nm-req-02.txt
> 
> Dan
> 
> I never saw any more on this list about this I-D but, as you 
> may know, it evolved into an MPLS-TP I-D and is currently in 
> WGLC on the MPLS-TP list along with the mpls, ccamp, PWE3 and 
> l2vpn lists.
> 
> There is also draft-ietf-mpls-tp-requirements-06, also in 
> WGLC, and draft-ietf-mpls-tp-oam-requirements-01, which is not.
> 
> Tom Petch
> 
> 
> ----- Original Message -----
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: <ops-dir@ietf.org>; "ops-area (IETF)" <ops-area@ietf.org>
> Cc: <Scott.Mansfield@Ericsson.com>; 
> <hklam@Alcatel-Lucent.com>; "Eric Gray"
> <eric.gray@ericsson.com>
> Sent: Sunday, January 18, 2009 10:26 AM
> Subject: [OPS-AREA] FW: I-D Action:draft-gray-mpls-tp-nm-req-02.txt
> 
> 
> I believe that this I-D deserves some scrutiny from the OPS folks.
> 
> Dan
> 
> 
> -----Original Message-----
> From: i-d-announce-bounces@ietf.org
> [mailto:i-d-announce-bounces@ietf.org] On Behalf Of 
> Internet-Drafts@ietf.org
> Sent: Saturday, January 17, 2009 8:15 PM
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-gray-mpls-tp-nm-req-02.txt
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> 
> Title           : MPLS TP Network Management Requirements
> Author(s)       : S. Mansfield, et al.
> Filename        : draft-gray-mpls-tp-nm-req-02.txt
> Pages           : 15
> Date            : 2009-01-17
> 
> This document specifies the requirements necessary to manage the
> 
> elements and networks that support an MPLS Transport Profile
> 
> (MPLS-TP). This document is a product of a joint International
> 
> Telecommunications Union - Telecommunications Standardization
> 
> Sector (ITU-T) and Internet Engineering Task Force (IETF) effort
> 
> to include a MPLS Transport Profile within the IETF MPLS
> 
> architecture. The requirements are driven by the management
> 
> functionality needs defined by ITU-T for packet transport
> 
> networks.
> 
> 
> 
> Gray, et al
> 
> 
> 
> 
> Expires July, 2009
> 
> 
> 
> 
> [page 1]
> 
> 
> 
> 
> 
> Internet-Draft
> 
> 
> MPLS-TP NM Requirements
> 
>   January, 2009
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-gray-mpls-tp-nm-req-02.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail 
> reader implementation to automatically retrieve the ASCII 
> version of the Internet-Draft.
> 
> 
> 
> --------------------------------------------------------------
> ------------------
> 
> 
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >
> 
>