Re: [PWE3] OAM Msg Mapping Drafts
"Busschbach, Peter B \(Peter\)" <busschbach@alcatel-lucent.com> Fri, 25 July 2008 17:27 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 827B83A699D; Fri, 25 Jul 2008 10:27:59 -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 D5C2E3A699D for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 10:27:57 -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=[AWL=0.000, 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 diuo68ol0zim for <pwe3@core3.amsl.com>; Fri, 25 Jul 2008 10:27:56 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id D27783A6811 for <pwe3@ietf.org>; Fri, 25 Jul 2008 10:27:56 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m6PHQdhA012713; Fri, 25 Jul 2008 12:27:30 -0500 (CDT)
Received: from ILEXC2U01.ndc.lucent.com ([135.3.39.12]) by ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Jul 2008 12:27:25 -0500
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 25 Jul 2008 12:27:24 -0500
Message-ID: <E60778C3916D3548BBCF4D964186348F01B3FDD4@ILEXC2U01.ndc.lucent.com>
In-Reply-To: <488A0910.5020409@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] OAM Msg Mapping Drafts
Thread-Index: AcjueXFal4f2KujSSdCdUYn9vs8dpAAARk2w
References: <4889E042.2090404@cisco.com> <488A0910.5020409@cisco.com>
From: "Busschbach, Peter B (Peter)" <busschbach@alcatel-lucent.com>
To: Carlos Pignataro <cpignata@cisco.com>, stbryant@cisco.com
X-OriginalArrivalTime: 25 Jul 2008 17:27:25.0460 (UTC) FILETIME=[B45F6D40:01C8EE7B]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: pwe3 <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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
Carlos, It may be true that the L2TPv3 portion required improvements, but the normal process would have been to point out on the mailing list. As far as I know, the L2TP-related text has not changed since 2005, so there has been ample time to fix the mistakes. Having new people identify themselves as editors and making modifications to a document based on the claim that the old text was "broken" is a bizarre way to update a WG document. I propose that you send an email to the mailing list to point out what needs to be changed in the 06-version of the text. The editors can then take that into consideration for the new version. Peter > -----Original Message----- > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On > Behalf Of Carlos Pignataro > Sent: Friday, July 25, 2008 1:11 PM > To: stbryant@cisco.com > Cc: pwe3 > Subject: Re: [PWE3] OAM Msg Mapping Drafts > > I'd like to point out that although this focus is on the > eth-oam, there were additional updates to this "updated rev > -07" version, including: > > 1. Update (rework/rewrite) of the L2TPv3 portions (as Luca mentioned > with "L2TP message mapping is broken", those segments > needed work). I > made those edits (and would very much like to get > feedback on them). > 2. Small catch-up with some of the VCCV-related updates > (e.g., there was > no reference to VCCV-BFD, and no demarc from RFC5085, > same) 3. Address > <http://www.ietf.org/mail-archive/web/pwe3/current/msg09479.html>. > 4. Others (standby state, et cetera). > > As such, I'd like to request that these edits (the updates to non-eth > portions) do not get lost in the process, and option a) seems > to make these updates go away. As far as whether merging the > eth-oam or keeping it in a separate document, I really do not > have a preference. As long as the WG work is equally timely, > complete and accurate, I have no preference as to which > document contains it, and thus b) or c) would be fine for me. > > Thanks, > > --Carlos. > > On 7/25/2008 10:16 AM, Stewart Bryant said the following: > > 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 > > > > -- > --Carlos Pignataro. > Escalation RTP - cisco Systems > _______________________________________________ > 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
- Re: [PWE3] OAM Msg Mapping Drafts Stewart Bryant
- Re: [PWE3] OAM Msg Mapping Drafts QIU Ray
- Re: [PWE3] OAM Msg Mapping Drafts O'Connor, Don
- [PWE3] OAM Msg Mapping Drafts Stewart Bryant
- Re: [PWE3] OAM Msg Mapping Drafts philippe.niger
- Re: [PWE3] OAM Msg Mapping Drafts Thomas Nadeau
- Re: [PWE3] OAM Msg Mapping Drafts Shahram Davari
- Re: [PWE3] OAM Msg Mapping Drafts David Allan
- Re: [PWE3] OAM Msg Mapping Drafts Drake, John E
- Re: [PWE3] OAM Msg Mapping Drafts Dinesh Mohan
- Re: [PWE3] OAM Msg Mapping Drafts Shah, Himanshu
- Re: [PWE3] OAM Msg Mapping Drafts AISSAOUI Mustapha
- Re: [PWE3] OAM Msg Mapping Drafts Ali Sajassi (sajassi)
- Re: [PWE3] OAM Msg Mapping Drafts Andrew G. Malis
- Re: [PWE3] OAM Msg Mapping Drafts Busschbach, Peter B (Peter)
- Re: [PWE3] OAM Msg Mapping Drafts AISSAOUI Mustapha
- Re: [PWE3] OAM Msg Mapping Drafts Carlos Pignataro
- Re: [PWE3] OAM Msg Mapping Drafts Hamid Ould-Brahim
- Re: [PWE3] OAM Msg Mapping Drafts Busschbach, Peter B (Peter)
- Re: [PWE3] OAM Msg Mapping Drafts Don Fedyk
- Re: [PWE3] OAM Msg Mapping Drafts nabil.n.bitar
- Re: [PWE3] OAM Msg Mapping Drafts HENDERICKX Wim
- Re: [PWE3] OAM Msg Mapping Drafts Simon Delord
- Re: [PWE3] OAM Msg Mapping Drafts BALUS Florin
- Re: [PWE3] OAM Msg Mapping Drafts Luca Martini
- Re: [PWE3] OAM Msg Mapping Drafts MULEY Praveen
- Re: [PWE3] OAM Msg Mapping Drafts Carlos Pignataro
- Re: [PWE3] OAM Msg Mapping Drafts Busschbach, Peter B (Peter)
- Re: [PWE3] OAM Msg Mapping Drafts AISSAOUI Mustapha
- Re: [PWE3] OAM Msg Mapping Drafts Thomas Nadeau
- Re: [PWE3] OAM Msg Mapping Drafts Luca Martini
- Re: [PWE3] OAM Msg Mapping Drafts Yaakov Stein
- Re: [PWE3] OAM Msg Mapping Drafts Yaakov Stein
- [PWE3] PW bonding draft Yaakov Stein
- Re: [PWE3] PW bonding draft Lucy Yong
- Re: [PWE3] PW bonding draft Yaakov Stein
- Re: [PWE3] PW bonding draft HENDERICKX Wim
- Re: [PWE3] PW bonding draft Yaakov Stein
- Re: [PWE3] PW bonding draft Lucy Yong
- Re: [PWE3] PW bonding draft Yaakov Stein
- Re: [PWE3] PW bonding draft Lucy Yong
- Re: [PWE3] PW bonding draft philippe.niger
- Re: [PWE3] PW bonding draft Yaakov Stein
- Re: [PWE3] PW bonding draft Shahram Davari
- Re: [PWE3] PW bonding draft Yaakov Stein