Re: Possible Shutdown of L3VPN
IJsbrand Wijnands <ice@cisco.com> Tue, 24 January 2012 11:04 UTC
Return-Path: <ice@cisco.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 6BCEA21F8540 for <l3vpn@ietfa.amsl.com>; Tue, 24 Jan 2012 03:04:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level:
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 ABIVgsl07q8W for <l3vpn@ietfa.amsl.com>; Tue, 24 Jan 2012 03:04:45 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 8A64921F853D for <l3vpn@ietf.org>; Tue, 24 Jan 2012 03:04:45 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from stew-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 q0OB4iNX002633 for <l3vpn@ietf.org>; Tue, 24 Jan 2012 12:04:44 +0100 (CET)
Received: from ams-iwijnand-8718.cisco.com (ams-iwijnand-8718.cisco.com [10.55.191.153]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q0OB4gY7023799; Tue, 24 Jan 2012 12:04:42 +0100 (CET)
Subject: Re: Possible Shutdown of L3VPN
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="us-ascii"
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <F9F5B7F2-D4A5-4DD7-ACBD-5D6A13592131@niven-jenkins.co.uk>
Date: Tue, 24 Jan 2012 12:04:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E714509D-A840-4EEF-8627-AEC814C165ED@cisco.com>
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>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.1251.1)
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: Tue, 24 Jan 2012 11:04:46 -0000
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? Maybe there is also a role for the WG chairs to solicit input and help drive documents through the WG. But I get the impression the chairs are more interested in killing it. 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 >>>> >>> >>> >> > >
- Possible Shutdown of L3VPN Marshall Eubanks
- RE: Possible Shutdown of L3VPN Henderickx, Wim (Wim)
- Re: Possible Shutdown of L3VPN Ben Niven-Jenkins
- RE: Possible Shutdown of L3VPN Henderickx, Wim (Wim)
- RE: Possible Shutdown of L3VPN NAPIERALA, MARIA H
- Re: Possible Shutdown of L3VPN thomas.morin
- Re: Possible Shutdown of L3VPN Ben Niven-Jenkins
- Re: Possible Shutdown of L3VPN Ben Niven-Jenkins
- Re: Possible Shutdown of L3VPN Thomas Nadeau
- RE: Possible Shutdown of L3VPN Linda Dunbar
- Re: Possible Shutdown of L3VPN Marshall Eubanks
- Re: Possible Shutdown of L3VPN Ben Niven-Jenkins
- Re: Possible Shutdown of L3VPN IJsbrand Wijnands
- Re: Possible Shutdown of L3VPN Robert Raszuk
- Re: Possible Shutdown of L3VPN Ben Niven-Jenkins
- Re: Possible Shutdown of L3VPN IJsbrand Wijnands
- RE: Possible Shutdown of L3VPN NAPIERALA, MARIA H
- Re: Possible Shutdown of L3VPN Robert Raszuk
- Re: Possible Shutdown of L3VPN Ben Niven-Jenkins
- Re: Possible Shutdown of L3VPN Thomas Narten
- Re: Possible Shutdown of L3VPN Marshall Eubanks
- Re: Possible Shutdown of L3VPN thomas.morin