Re: [PWE3] OAM Msg Mapping Drafts

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Fri, 25 July 2008 16:41 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 58EDD28C1C8; Fri, 25 Jul 2008 09:41:24 -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 AB89B28C1C8 for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 09:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 ihzvLJCLCnsS for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 09:41:22 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id DE74928C136 for <pwe3@ietf.org>; Fri, 25 Jul 2008 09:41:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,253,1215388800"; d="scan'208";a="57717039"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 25 Jul 2008 16:41:25 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m6PGfNU3023837; Fri, 25 Jul 2008 09:41:23 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m6PGfM5C024840; Fri, 25 Jul 2008 16:41:23 GMT
Received: from xmb-sjc-239.amer.cisco.com ([128.107.191.105]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Jul 2008 09:41:19 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 25 Jul 2008 09:41:19 -0700
Message-ID: <483F121CD2155B43B56DB71228DBAF1501F35005@xmb-sjc-239.amer.cisco.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: AcjuYV7tYa298S3DRuyQv1nR+KIZxAAD5djQ
References: <4889E042.2090404@cisco.com>
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>, pwe3 <pwe3@ietf.org>
X-OriginalArrivalTime: 25 Jul 2008 16:41:19.0826 (UTC) FILETIME=[43ED2B20:01C8EE75]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2747; t=1217004083; x=1217868083; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sajassi@cisco.com; z=From:=20=22Ali=20Sajassi=20(sajassi)=22=20<sajassi@cisco.c om> |Subject:=20RE=3A=20[PWE3]=20OAM=20Msg=20Mapping=20Drafts |Sender:=20; bh=mEZ5tAJHT6k3Q4AQOOHKXFiPM/y11HHYPb6YOD6Nlac=; b=tQaqJRG/boYqg2j+mmsl46gesT5qbfqarl6gkpV1398BAxMV5ag0vsK+lV /PMgnlePiBOSUTxm9cqwxhxmLbPCUtw95eRiJAnukqx2jVAS7ifIl1Jr8BmP TZVQeUxWe+;
Authentication-Results: sj-dkim-4; header.From=sajassi@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
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


Given that Luca has spent time & energy to update this draft (specially
for non-Eth sections), I would opt for option (b) (Luca rewrite without
Ethernet and WG call of Ethernet draft) with proper editorship list (so
credit be given where it is due).

- Ali    

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Stewart Bryant (stbryant)
> 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