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

John E Drake <jdrake@juniper.net> Tue, 27 April 2010 17:32 UTC

Return-Path: <jdrake@juniper.net>
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 61C183A6943 for <l3vpn@core3.amsl.com>; Tue, 27 Apr 2010 10:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.839
X-Spam-Level:
X-Spam-Status: No, score=-4.839 tagged_above=-999 required=5 tests=[AWL=-1.254, BAYES_40=-0.185, J_CHICKENPOX_13=0.6, 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 cGpnZK9WeV3O for <l3vpn@core3.amsl.com>; Tue, 27 Apr 2010 10:32:28 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by core3.amsl.com (Postfix) with ESMTP id 94AF93A6B6A for <l3vpn@ietf.org>; Tue, 27 Apr 2010 10:32:02 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKS9cfhLfj0itXax3PcxahJyGv0Mtqi6E7@postini.com; Tue, 27 Apr 2010 10:31:50 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::99ad:1ca:2a64:e987]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 27 Apr 2010 10:27:12 -0700
From: John E Drake <jdrake@juniper.net>
To: Thomas Morin <thomas.morin@orange-ftgroup.com>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Date: Tue, 27 Apr 2010 10:27:10 -0700
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+d8S3e7z2Vvt6VB7wAFa0TQ
Message-ID: <5E893DB832F57341992548CDBB3331639814B27208@EMBX01-HQ.jnpr.net>
References: <C7FA25C8.15838%benjamin.niven-jenkins@bt.com> <4BD6F868.5030402@orange-ftgroup.com>
In-Reply-To: <4BD6F868.5030402@orange-ftgroup.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
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: Tue, 27 Apr 2010 17:32:29 -0000

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