Re: [PWE3] OAM Msg Mapping Drafts

"BALUS Florin" <Florin.Balus@alcatel-lucent.com> Fri, 25 July 2008 21:52 UTC

Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A4B93A6A4C; Fri, 25 Jul 2008 14:52:25 -0700 (PDT)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C68D63A6A4B for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 14:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 4ossKTwjjI+u for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 14:52:22 -0700 (PDT)
Received: from audl951.usa.alcatel.com (audl951.usa.alcatel.com [143.209.238.161]) by core3.amsl.com (Postfix) with ESMTP id 4497228C179 for <pwe3@ietf.org>; Fri, 25 Jul 2008 14:50:34 -0700 (PDT)
Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl951.usa.alcatel.com (ALCANET) with ESMTP id m6PLoXXv024463; Fri, 25 Jul 2008 16:50:33 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.8]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 25 Jul 2008 16:50:33 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 25 Jul 2008 16:50:24 -0500
Message-ID: <4A5028372622294A99B8FFF6BD06EB7B04791866@USDALSMBS03.ad3.ad.alcatel.com>
In-reply-to: <4889E042.2090404@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] OAM Msg Mapping Drafts
Thread-Index: AcjuYVvqP5ocKcX9Qkm+/lSjsk3e5QAPukqQ
References: <4889E042.2090404@cisco.com>
From: BALUS Florin <Florin.Balus@alcatel-lucent.com>
To: stbryant@cisco.com, pwe3 <pwe3@ietf.org>
X-OriginalArrivalTime: 25 Jul 2008 21:50:33.0161 (UTC) FILETIME=[76936B90:01C8EEA0]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
Subject: Re: [PWE3] OAM Msg Mapping Drafts
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Option a for me. 

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf
Of
> Stewart Bryant
> Sent: Friday, July 25, 2008 7:17 AM
> To: pwe3
> Subject: [PWE3] OAM Msg Mapping Drafts
> 
> 
> We had hoped to resolve this face to face before
> the PWE3 meeting next week but that now looks
> unlikely. We are  concerned that we need to
> resolve this without the issue absorbing all
> of the time in the WG meeting.
> 
> In order to gauge the consensus of the WG we would
> would like to ask some questions.
> 
> When considering how to approach the message mapping
> document issue, we think that the most important
> considerations are:
> 
> 1) That we deliver a high quality document that describes
>     the design to the implementors and users.
> 
> 2) That the Ethernet design is fully reviewed.
> 
> 3) That there is consistency between the approaches used
>     for the various OAM mappings.
> 
> 4) That the Ethernet design is delivered in an expedited
>     manner and the ATM and FR designs are also delivered
>     in a timely manner.
> 
> 
> We have three approaches:
> 
> a) LC and publish draft-ietf-pwe3-oam-msg-map-06.txt, and
> 
>     Accept draft-mohan-pwe3-mpls-eth-oam-iwk as
>     a WG document
> 
> b) LC and publish draft-ietf-pwe3-oam-msg-map-07.txt
>     (i.e. Luca's rewrite) but without  the Ethernet
>     section, and
> 
>     Accept draft-mohan-pwe3-mpls-eth-oam-iwk as a WG
>     document
> 
> c) Use publish draft-ietf-pwe3-oam-msg-map-07.txt  as
>     the basis for ongoing work.
> 
> Before any document is sent to the IESG for publication
> we will ensure contributions are appropriately acknowledged
> through  editorship, authorship, & acknowledgments. So
> please set any such issues aside and focus on the best
> document to deliver to our users.
> 
> Please also set aside the poor etiquette that has taken
> place, and  focus on  how best to deliver  the required
> documentation to the community. On the basis of
> considerations 1..4 above, which documentation
> approach, a, b or c, do you consider most likely to
> achieve the goals of the WG?
> 
> 
> Stewart & Matthew
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3