Re: [mpls] Mail regarding draft-ietf-pwe3-mpls-tp-oam-config

Gregory Mirsky <> Sat, 30 August 2014 06:59 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 88A181A8830; Fri, 29 Aug 2014 23:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Dbi3A8bSZ0Qi; Fri, 29 Aug 2014 23:59:25 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 02F751A8828; Fri, 29 Aug 2014 23:59:24 -0700 (PDT)
X-AuditID: c618062d-f79206d0000014d2-fd-5401215f795d
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id DC.CD.05330.F5121045; Sat, 30 Aug 2014 02:57:03 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Sat, 30 Aug 2014 02:59:18 -0400
From: Gregory Mirsky <>
To: Mach Chen <>, "" <>
Thread-Topic: Mail regarding draft-ietf-pwe3-mpls-tp-oam-config
Thread-Index: Ac/EHzNiM8L42u/HRiC1vK41AsrBRQAADI0w
Date: Sat, 30 Aug 2014 06:59:17 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyuXRPoG68ImOIQfN/EYsLa4Utbi1dyWrR 92kLiwOzR8uRt6weS5b8ZApgiuKySUnNySxLLdK3S+DKmH/vPVPBIc6K9Ts3szUwvmTvYuTk kBAwkei8e44RwhaTuHBvPVsXIxeHkMBRRonbfd1MEM5yRol33/Yxg1SxCRhJvNjYA9YtIuAq 8WPCcqAiDg5mAWWJU3dlQMLCAnYSm96fYIQosZf43vuNCcI2kliw9z4biM0ioCrx4fdXsDG8 Ar4Sz1d8BRsvJBAq8XPlDrB6ToEwieVrFoDVMwId9/3UGrA4s4C4xK0n85kgjhaQWLLnPDOE LSrx8vE/VghbUWJf/3R2iHodiQW7P7FB2NoSyxa+ZobYKyhxcuYTlgmMYrOQjJ2FpGUWkpZZ SFoWMLKsYuQoLU4ty003MtjECIyWYxJsujsY97y0PMQowMGoxMP74DtDiBBrYllxZe4hRmkO FiVx3lm184KFBNITS1KzU1MLUovii0pzUosPMTJxcEo1MOqf3pDntETSYJX8vqtmwpteLD/8 S+ihw91v+dMfTpxVkhjDeXTXXC6pXTFBekbK0xbd/SS1sZ1x97RKJwmbRZouYhYiK6o46sst 7pRFLFS+FONlsogheHbkt9dBf18VGfb0b3CP/b71nyd3esLTM52d0QuXXcmUf7qncN6yRQ8M NTuk46zUbymxFGckGmoxFxUnAgCquJSWdwIAAA==
Cc: "" <>
Subject: Re: [mpls] Mail regarding draft-ietf-pwe3-mpls-tp-oam-config
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 30 Aug 2014 06:59:28 -0000

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.


-----Original Message-----
From: pwe3 [] On Behalf Of Mach Chen
Sent: Friday, August 29, 2014 11:54 PM
Subject: [PWE3] Mail regarding draft-ietf-pwe3-mpls-tp-oam-config


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! 


pwe3 mailing list