Re: [PWE3] OAM Msg Mapping Drafts

"Drake, John E" <John.E.Drake2@boeing.com> Fri, 25 July 2008 15:36 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 16F393A6B01; Fri, 25 Jul 2008 08:36:44 -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 05B1628C1ED for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 08:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.3
X-Spam-Level:
X-Spam-Status: No, score=-5.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6GSw1bBFzHNB for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 08:36:42 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 29F983A6B01 for <pwe3@ietf.org>; Fri, 25 Jul 2008 08:36:41 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id m6PFaWH5006325 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 25 Jul 2008 08:36:33 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id m6PFaWfv004275; Fri, 25 Jul 2008 10:36:32 -0500 (CDT)
Received: from xch-swbh-11.sw.nos.boeing.com (xch-swbh-11.sw.nos.boeing.com [129.172.192.157]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id m6PFaDqL003825; Fri, 25 Jul 2008 10:36:32 -0500 (CDT)
Received: from XCH-SW-5V2.sw.nos.boeing.com ([129.172.193.50]) by xch-swbh-11.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 25 Jul 2008 08:36:31 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 25 Jul 2008 08:36:30 -0700
Message-ID: <51661468CBD1354294533DA79E85955AEFE96A@XCH-SW-5V2.sw.nos.boeing.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: AcjuYVgu+GjvS9+3T1SHU6IYlKnYPgACsmeQ
References: <4889E042.2090404@cisco.com>
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: stbryant@cisco.com, pwe3 <pwe3@ietf.org>
X-OriginalArrivalTime: 25 Jul 2008 15:36:31.0826 (UTC) FILETIME=[367F7320:01C8EE6C]
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

a) 

>-----Original Message-----
>From: Stewart Bryant [mailto:stbryant@cisco.com] 
>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