Re: [PWE3] OAM Msg Mapping Drafts

"Dinesh Mohan" <mohand@nortel.com> Fri, 25 July 2008 15:39 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 3BB4428C209; Fri, 25 Jul 2008 08:39:46 -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 60AB528C20C for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 08:39:45 -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 NM0A3lw3rIb0 for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 08:39:44 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55]) by core3.amsl.com (Postfix) with ESMTP id 82A8A28C208 for <pwe3@ietf.org>; Fri, 25 Jul 2008 08:39:40 -0700 (PDT)
Received: from zcarhxm1.corp.nortel.com (zcarhxm1.corp.nortel.com [47.129.230.97]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id m6PFdWA25564; Fri, 25 Jul 2008 15:39:32 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 25 Jul 2008 11:39:08 -0400
Message-ID: <183DD1B052A11A40B76125E42F1CBAAB132721BA@zcarhxm1.corp.nortel.com>
In-Reply-To: <BBBE5BAA3B351C488C415EA662EA88400545844F@ftrdmel2>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] OAM Msg Mapping Drafts
Thread-Index: AcjuYVvu/STGfkjJSJSul9IekQb2+wAAhxrgAAISUrA=
References: <4889E042.2090404@cisco.com> <BBBE5BAA3B351C488C415EA662EA88400545844F@ftrdmel2>
From: Dinesh Mohan <mohand@nortel.com>
To: philippe.niger@orange-ftgroup.com, stbryant@cisco.com, pwe3@ietf.org
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I also support option a).

---
Dinesh

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of philippe.niger@orange-ftgroup.com
Sent: Friday, July 25, 2008 10:41 AM
To: stbryant@cisco.com; pwe3@ietf.org
Subject: Re: [PWE3] OAM Msg Mapping Drafts

Hi all,

I strongly support approach a.

For me it is the best approach to deliver an OAM solution for PW in a timely manner, and it is fully in line with the consensus that emerged during the last meeting.

Regards,

Philippe. 


-----Message d'origine-----
De : pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] De la part de Stewart Bryant Envoyé : vendredi 25 juillet 2008 16:17 À : pwe3 Objet : [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
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3