Re: Poll to adopt draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a L3VPN WG document

<benjamin.niven-jenkins@bt.com> Wed, 28 April 2010 19:02 UTC

Return-Path: <benjamin.niven-jenkins@bt.com>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AE583A6BB8 for <l3vpn@core3.amsl.com>; Wed, 28 Apr 2010 12:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.142
X-Spam-Level: *
X-Spam-Status: No, score=1.142 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_40=-0.185, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6]
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 J2JV+SEbT27u for <l3vpn@core3.amsl.com>; Wed, 28 Apr 2010 12:02:09 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp62.intersmtp.COM [62.239.224.235]) by core3.amsl.com (Postfix) with ESMTP id A9B1A3A6ACA for <l3vpn@ietf.org>; Wed, 28 Apr 2010 12:02:03 -0700 (PDT)
Received: from EVMHT66-UKRD.domain1.systemhost.net (10.36.3.103) by RDW083A006ED62.smtp-e2.hygiene.service (10.187.98.11) with Microsoft SMTP Server (TLS) id 8.1.393.1; Wed, 28 Apr 2010 20:01:50 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.2.251]) by EVMHT66-UKRD.domain1.systemhost.net ([10.36.3.103]) with mapi; Wed, 28 Apr 2010 20:01:50 +0100
From: benjamin.niven-jenkins@bt.com
To: jdrake@juniper.net, thomas.morin@orange-ftgroup.com, l3vpn@ietf.org
Date: Wed, 28 Apr 2010 20:01:47 +0100
Subject: Re: Poll to adopt draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a L3VPN WG document
Thread-Topic: Poll to adopt draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a L3VPN WG document
Thread-Index: AcrmGSzChfDHN+d8S3e7z2Vvt6VB7wAFa0TQADWZki8=
Message-ID: <C7FE44AB.15D43%benjamin.niven-jenkins@bt.com>
In-Reply-To: <5E893DB832F57341992548CDBB3331639814B27208@EMBX01-HQ.jnpr.net>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.3.0.091002
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Apr 2010 19:02:10 -0000

John,

Same question to you that I just asked Thomas:

Does this mean that you would support adoption of the document if section
3.1 was removed or that you object to the adoption of the document in
general?

Thanks
Ben

[I am trying to separate out whether the ongoing debate is really just about
Section 3.1 of the document or there are more general objections to the
document]


On 27/04/2010 18:27, "John E Drake" <jdrake@juniper.net> wrote:

> +1
> 
>> -----Original Message-----
>> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf Of
>> Thomas Morin
>> Sent: Tuesday, April 27, 2010 7:45 AM
>> To: l3vpn@ietf.org
>> Subject: Re: Poll to adopt draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a
>> L3VPN WG document
>> 
>> Ben, Colleagues,
>> 
>> The working group has recently submitted to the IESG a document that
>> highlights the drawbacks of the UDP-based S-PMSI signaling mechanism,
>> compared to the BGP-based S-PMSI signaling mechanism, and specifically
>> recommends against extending the UDP-based scheme for types of tunnels
>> beyond what is already covered by the base mVPN specs recently submitted
>> to the IESG [draft-ietf-l3vpn-mvpn-considerations-06#section-3.2].
>> Nobody commented against this part of the document, even though the
>> document was debated in length on many other points.
>> 
>> Eric mentioned the promise made between co-authors of mVPN specs and an
>> A-D as a key argument to adopt the IPv6-related part of this draft, even
>> though this promise did not involve the working group.   By comparison,
>> strong and recent working group consensus to not extend the UDP-based
>> signaling to other types of P-tunnels, looks to me as a reason at least
>> as good to *not* adopt a document proposition such an extension.
>> 
>> So well, I don't think that adopting the document with section 3.1
>> should even be considered, and in any case I'm opposed the adoption of
>> the document if it includes that section.
>> 
>> -Thomas
>> 
>> 
>> 
>> benjamin.niven-jenkins@bt.com:
>>> Colleagues,
>>> 
>>> This e-mail is to start a poll on whether the L3VPN WG should adopt
>>> draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a L3VPN WG document.
>>> 
>>> As there was some discussion in Anaheim on section 3.1 of the draft, we
>> will
>>> follow Eric's suggestion in his mail of 16th April (
>>> http://www.ietf.org/mail-archive/web/l3vpn/current/msg02664.html).
>>> 
>>> Therefore please indicate your support or otherwise by responding to
>> this
>>> message or e-mailing the WG chairs privately with one of the following
>> three
>>> options:
>>> 
>>> 1) Yes/Support for the entire of draft-rosen-l3vpn-mvpn-spmsi-joins-00
>> to be
>>> adopted as a L3VPN WG document.
>>> 
>>> 2) Yes/Support for draft-rosen-l3vpn-mvpn-spmsi-joins-00 to be adopted
>> as a
>>> WG document provided section 3.1 is removed.
>>> 
>>> 3) No/Do not support draft-rosen-l3vpn-mvpn-spmsi-joins-00 being adopted
>> as
>>> a WG document at all.
>>> 
>>> Please send your responses by the end of May 9th PST.
>>> 
>>> Ben
>>> 
>>>