Re: Possible Shutdown of L3VPN

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Sun, 22 January 2012 09:59 UTC

Return-Path: <ben@niven-jenkins.co.uk>
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 ED2B721F84F5 for <l3vpn@ietfa.amsl.com>; Sun, 22 Jan 2012 01:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level:
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=-0.300, 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 1JFhTizlQJ-5 for <l3vpn@ietfa.amsl.com>; Sun, 22 Jan 2012 01:59:18 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by ietfa.amsl.com (Postfix) with ESMTP id 37AA221F84EC for <l3vpn@ietf.org>; Sun, 22 Jan 2012 01:59:17 -0800 (PST)
Received: from cpc10-cmbg15-2-0-cust121.5-4.cable.virginmedia.com ([86.30.246.122] helo=[192.168.0.3]) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1RouCh-0001OR-PX; Sun, 22 Jan 2012 09:59:16 +0000
Subject: Re: Possible Shutdown of L3VPN
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <14C7F4F06DB5814AB0DE29716C4F6D671CF51277@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
Date: Sun, 22 Jan 2012 09:59:13 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4F48EA2-B1BA-488F-A630-05B379691763@niven-jenkins.co.uk>
References: <CAJNg7VJFnTEWEJWMRJ6dy+TFSEVqGtwmFGFCpPw8yzqExE_BRg@mail.gmail.com> <14C7F4F06DB5814AB0DE29716C4F6D671CF51277@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
To: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
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: Sun, 22 Jan 2012 09:59:19 -0000

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