Re: Possible Shutdown of L3VPN

Marshall Eubanks <marshall.eubanks@gmail.com> Wed, 25 January 2012 02:36 UTC

Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84E3621F8589 for <l3vpn@ietfa.amsl.com>; Tue, 24 Jan 2012 18:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.195
X-Spam-Level:
X-Spam-Status: No, score=-103.195 tagged_above=-999 required=5 tests=[AWL=-0.196, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hjj4+UORhCGz for <l3vpn@ietfa.amsl.com>; Tue, 24 Jan 2012 18:36:34 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id B2E9021F8578 for <l3vpn@ietf.org>; Tue, 24 Jan 2012 18:36:34 -0800 (PST)
Received: by obbwc12 with SMTP id wc12so6099497obb.31 for <l3vpn@ietf.org>; Tue, 24 Jan 2012 18:36:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=gREOLBK+wufP8oMA48Wi56JAk2rI6Y1m+2xOpmDoCTI=; b=Ifq3szBvGrImEdOO4Lf4TiM3SbpMoHxkbdoqOEecoHwp1/9IbUhPBRUVyYqPhG4Xzd xggBz1SXy82uRb3BmD6eJwwKR1uwK1ry67p1GXnO6FqUoAtKgfTzB8bhYWhwwOB+NjnQ gm18epwbMmFrBW2z0lkQ2hq7gMmy+Ygr02lj0=
MIME-Version: 1.0
Received: by 10.182.231.7 with SMTP id tc7mr14025155obc.29.1327458994210; Tue, 24 Jan 2012 18:36:34 -0800 (PST)
Received: by 10.182.79.102 with HTTP; Tue, 24 Jan 2012 18:36:34 -0800 (PST)
In-Reply-To: <CE832713-B1CE-473B-A836-9A64D22B87FD@niven-jenkins.co.uk>
References: <CAJNg7VJFnTEWEJWMRJ6dy+TFSEVqGtwmFGFCpPw8yzqExE_BRg@mail.gmail.com> <14C7F4F06DB5814AB0DE29716C4F6D671CF51277@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <E4F48EA2-B1BA-488F-A630-05B379691763@niven-jenkins.co.uk> <1D70D757A2C9D54D83B4CBD7625FA80EA81894@MISOUT7MSGUSR9I.ITServices.sbc.com> <1E20A067-9908-41FE-9739-19850A3DCA93@niven-jenkins.co.uk> <E81B62FB-6417-4E4F-B735-4CBE4ED9AE46@cisco.com> <F9F5B7F2-D4A5-4DD7-ACBD-5D6A13592131@niven-jenkins.co.uk> <E714509D-A840-4EEF-8627-AEC814C165ED@cisco.com> <CE832713-B1CE-473B-A836-9A64D22B87FD@niven-jenkins.co.uk>
Date: Tue, 24 Jan 2012 21:36:34 -0500
Message-ID: <CAJNg7VKU0uBG7Cn1Y=6id0+aZvcH7f-P9UdSq9=8c9qR4SzLSA@mail.gmail.com>
Subject: Re: Possible Shutdown of L3VPN
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: L3VPN <l3vpn@ietf.org>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 25 Jan 2012 02:36:35 -0000

On Tue, Jan 24, 2012 at 2:28 PM, Ben Niven-Jenkins
<ben@niven-jenkins.co.uk> wrote:
> Ice,
>
> On 24 Jan 2012, at 11:04, IJsbrand Wijnands wrote:
>
>> Ben,
>>
>>> Yes but one could argue that L3VPN isn't performing that role currently. For example I know of other WGs that follow a process where at least 5 people that aren't the authors must review a draft before it is progressed, if we were to instigate a similar rule in L3VPN I suspect few, if any, drafts would meet the criteria for progression.
>>>
>>> IMO L3VPN no longer has a critical mass of active participants that help review, reach consensus and process documents.
>>
>> And by moving it to a different WG you think it will get better?
>
> <hat="individual">
> I don't know if it will get better but I don't think it will be any worse.
> </hat>
>
>> Maybe there is also a role for the WG chairs to solicit input and help drive documents through the WG.
>
> On one hand that's probably a reasonable criticism of the WG chairs.
>
>> But I get the impression the chairs are more interested in killing it.
>
> <hat ="individual">
> I, personally, have no vested interest in whether L3VPN remains "alive" or gets "killed" and FWIW it wasn't the WG chairs that initiated the discussions on whether the WG should remain open, it was our Area Directors.
>

Indeed it was. Speaking just for myself, I also have no vested
interest here. In my opinion, if people want it to continue, they need
to speak up, start commenting on drafts, and re-energize the group.

Regards
Marshall

> I do question whether the L3VPN WG is really providing what the community would generally expect from a WG beyond document processing services and if it isn't then IMO it's hard to justify keeping the WG open when there are other valid routes for progressing those documents.
> </hat>
>
> Ben
>
>>
>> Thx,
>>
>> Ice.
>>
>>>
>>> Ben
>>>
>>>>
>>>> Thx,
>>>>
>>>> Ice.
>>>>
>>>>
>>>>
>>>>>
>>>>> Ben
>>>>>
>>>>>>
>>>>>> Maria
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
>>>>>>> Of Ben Niven-Jenkins
>>>>>>> Sent: Sunday, January 22, 2012 4:59 AM
>>>>>>> To: Henderickx, Wim (Wim)
>>>>>>> Cc: L3VPN; Stewart Bryant (stbryant)
>>>>>>> Subject: Re: Possible Shutdown of L3VPN
>>>>>>>
>>>>>>> Wim,
>>>>>>>
>>>>>>> On 22 Jan 2012, at 06:11, Henderickx, Wim (Wim) wrote:
>>>>>>>
>>>>>>>> Why don't we keep the WG open until the WG drafts are finished?
>>>>>>>
>>>>>>> Because there's nothing like a deadline to motivate people :-)
>>>>>>>
>>>>>>> If it's decided to wind the WG down, what I would expect is that it
>>>>>>> wouldn't just happen overnight but that we would produce a 'plan' for
>>>>>>> closure within a reasonable timeframe (say 6 months) where we would aim
>>>>>>> to finish what we have on our plate first, if possible.
>>>>>>>
>>>>>>> Regarding WG drafts, currently we have 3:
>>>>>>> -> draft-ietf-l3vpn-mvpn-wildcards, which has just gone through WG LC
>>>>>>> and about to be sent to IESG for publication
>>>>>>> -> draft-ietf-l3vpn-acceptown-community, which we will initiate a WG LC
>>>>>>> on shortly
>>>>>>> -> draft-ietf-l3vpn-mvpn-bidir, which the authors say needs another
>>>>>>> revision before being ready for WG LC
>>>>>>>
>>>>>>> So getting those finished relatively quickly before closure seems
>>>>>>> achievable.
>>>>>>>
>>>>>>> I'd personally also like the combined extranet draft produced before
>>>>>>> closure but again I'd expect that should be possible relatively quickly
>>>>>>> too.
>>>>>>>
>>>>>>> Ben
>>>>>>>
>>>>>>>> We can probably do this on the mailing list and don't need a
>>>>>>> face2face meeting, but as such you keep the WG alive until the work is
>>>>>>> done.
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On
>>>>>>> Behalf Of Marshall Eubanks
>>>>>>>> Sent: zaterdag 21 januari 2012 14:38
>>>>>>>> To: L3VPN; Stewart Bryant (stbryant); ben@niven-jenkins.co.uk
>>>>>>>> Subject: Possible Shutdown of L3VPN
>>>>>>>>
>>>>>>>> Dear WG members;
>>>>>>>>
>>>>>>>> With the Paris meeting coming up, we felt that you should know that
>>>>>>>> there has been serious discussion of shutting down the L3VPN working
>>>>>>>> group, both because of a decline of work in the group, and because of
>>>>>>> the
>>>>>>>> expected new work to come from the DC effort is likely to require a
>>>>>>>> new working group with a different focus.
>>>>>>>>
>>>>>>>> If the WG were to be wound down, the basic choices for existing
>>>>>>> drafts are
>>>>>>>>
>>>>>>>> - to go to last call with the drafts that are ready for it or
>>>>>>>>
>>>>>>>> - to put outstanding WG drafts into another WG, such as MPLS, or
>>>>>>>>
>>>>>>>> - to have the ADs sponsor "orphaned" drafts that don't fit in another
>>>>>>>> WG as individual submissions.
>>>>>>>>
>>>>>>>> We have polled the current draft authors, and do not see any
>>>>>>>> insurmountable difficulties with this process.
>>>>>>>>
>>>>>>>> There doesn't at present seem to be enough business to warrant
>>>>>>> another
>>>>>>>> L3VPN meeting in Paris. However, we feel that the future of the WG
>>>>>>>> (and of the work)
>>>>>>>> should be discussed in person, so we plan to request time on the
>>>>>>>> agenda to discuss this at
>>>>>>>> the RTGAREA meeting.
>>>>>>>>
>>>>>>>> If anyone feels that closing L3VPN would be a mistake, now is the
>>>>>>> time
>>>>>>>> to speak up.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Marshall Eubanks / Ben Niven-Jenkins
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>