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

IJsbrand Wijnands <ice@cisco.com> Tue, 27 April 2010 17:59 UTC

Return-Path: <ice@cisco.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 76B853A6A61 for <l3vpn@core3.amsl.com>; Tue, 27 Apr 2010 10:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.14
X-Spam-Level:
X-Spam-Status: No, score=-0.14 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 SJiUSArTttoY for <l3vpn@core3.amsl.com>; Tue, 27 Apr 2010 10:59:33 -0700 (PDT)
Received: from av-tac-bru.cisco.com (odd-brew.cisco.com [144.254.15.119]) by core3.amsl.com (Postfix) with ESMTP id 715823A6943 for <l3vpn@ietf.org>; Tue, 27 Apr 2010 10:59:33 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o3RHxJvb013581; Tue, 27 Apr 2010 19:59:19 +0200 (CEST)
Received: from ams-iwijnand-8718.cisco.com (ams-iwijnand-8718.cisco.com [10.55.191.153]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o3RHxGiE013469; Tue, 27 Apr 2010 19:59:16 +0200 (CEST)
Subject: Re: Poll to adopt draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a L3VPN WG document
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <4BD6F868.5030402@orange-ftgroup.com>
Date: Tue, 27 Apr 2010 19:59:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBFC2FA4-8DCA-4C7E-B7D7-4AF5777F8B13@cisco.com>
References: <C7FA25C8.15838%benjamin.niven-jenkins@bt.com> <4BD6F868.5030402@orange-ftgroup.com>
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
X-Mailer: Apple Mail (2.1077)
Cc: l3vpn@ietf.org
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: Tue, 27 Apr 2010 17:59:34 -0000

Thomas,

> 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.

There are many successful deployments of the UDP based mechanism and many of these customers don't even care to come to IETF to debate this. There is a perfectly valid deployment reason to allow a simple extension to the UDP based mechanism, even if it goes against your recommendation.

I vote for option 1.


Thx,

Ice.


> 
> 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
>> 
>>