Re: [PWE3] Mail regarding draft-ietf-pwe3-mpls-tp-oam-config
Mach Chen <mach.chen@huawei.com> Sat, 30 August 2014 07:22 UTC
Return-Path: <mach.chen@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB911A8844; Sat, 30 Aug 2014 00:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level:
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IuPZXI5WBD36; Sat, 30 Aug 2014 00:21:57 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA0121A8849; Sat, 30 Aug 2014 00:21:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIW70471; Sat, 30 Aug 2014 07:21:53 +0000 (GMT)
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 30 Aug 2014 08:21:53 +0100
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.57]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Sat, 30 Aug 2014 15:21:50 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: Mail regarding draft-ietf-pwe3-mpls-tp-oam-config
Thread-Index: Ac/EHzNiM8L42u/HRiC1vK41AsrBRQAADI0wAAA1eWA=
Date: Sat, 30 Aug 2014 07:21:50 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25DA8EB1D@SZXEMA510-MBX.china.huawei.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25DA8EAE9@SZXEMA510-MBX.china.huawei.com> <7347100B5761DC41A166AC17F22DF1121B828BE1@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B828BE1@eusaamb103.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/_NA6e3VMbCJzS0LrW1_2XkEqTCs
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [PWE3] Mail regarding draft-ietf-pwe3-mpls-tp-oam-config
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3/>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Aug 2014 07:22:01 -0000
Hi Greg,
Thanks for your prompt response!
Yes, I know that draft. Actually, during the MPLS-TP era, there are three relevant drafts (this document, one is in ccamp and the one you mentioned) that intend to realize OAM configuration. I guess, the reason for this is that there is a requirement (it requires that the control plane MUST support this function) in RFC5654:
"The MPLS-TP control plane MUST support the configuration and
modification of OAM maintenance points as well as the activation/
deactivation of OAM when the transport path or transport service
is established or modified."
These three drafts have been there for a long time, and the draft (http://tools.ietf.org/html/draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-12) has already in the publish process.
I'd like hear the WG's opinions on how to progress this draft,
1. Is this document useful?
2. Is there still interest to progress this draft?
Best regards,
Mach
> -----Original Message-----
> From: Gregory Mirsky [mailto:gregory.mirsky@ericsson.com]
> Sent: Saturday, August 30, 2014 2:59 PM
> To: Mach Chen; pwe3@ietf.org
> Cc: mpls@ietf.org
> Subject: RE: Mail regarding draft-ietf-pwe3-mpls-tp-oam-config
>
> Hi Mach,
> I think that the draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf intended to be used to
> configure OAM on MPLS-TP PWs. It lapsed and expired but I'm working on
> updating it will publish shortly.
>
> Regards,
> Greg
>
> -----Original Message-----
> From: pwe3 [mailto:pwe3-bounces@ietf.org] On Behalf Of Mach Chen
> Sent: Friday, August 29, 2014 11:54 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Mail regarding draft-ietf-pwe3-mpls-tp-oam-config
>
> Hi,
>
> We submitted an update before Toronto meeting, and are working an update to
> refine and polish the document.
>
> This draft intends to solve a requirement (Requirement 51) of MPLS-TP:
>
> "If the control plane is used, it MUST support the configuration and
> modification of OAM maintenance points as well as the activation/
> deactivation of OAM when the transport path or transport service is
> established or modified (Requirement 51)[RFC5654].
> "
> We'd really like more reviews and feedbacks from the WG, any comments (is this
> document useful? is the solution technical right? etc.) are welcome!
>
> Thanks,
> Mach
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3