RE: Possible Shutdown of L3VPN

"NAPIERALA, MARIA H" <mn1921@att.com> Sun, 22 January 2012 17:01 UTC

Return-Path: <mn1921@att.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 E5DC921F8445 for <l3vpn@ietfa.amsl.com>; Sun, 22 Jan 2012 09:01:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level:
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, 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 v5NhJNXhchn7 for <l3vpn@ietfa.amsl.com>; Sun, 22 Jan 2012 09:01:49 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8C921F8444 for <l3vpn@ietf.org>; Sun, 22 Jan 2012 09:01:48 -0800 (PST)
X-Env-Sender: mn1921@att.com
X-Msg-Ref: server-14.tower-119.messagelabs.com!1327251707!11869094!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.4.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8255 invoked from network); 22 Jan 2012 17:01:48 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-14.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Jan 2012 17:01:48 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q0MH2HNu025982; Sun, 22 Jan 2012 12:02:17 -0500
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q0MH2EKP025968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 22 Jan 2012 12:02:14 -0500
Received: from MISOUT7MSGHUB9B.ITServices.sbc.com (misout7msghub9b.itservices.sbc.com [144.151.223.72]) by sflint01.pst.cso.att.com (RSA Interceptor); Sun, 22 Jan 2012 12:01:40 -0500
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([169.254.1.140]) by MISOUT7MSGHUB9B.ITServices.sbc.com ([144.151.223.72]) with mapi id 14.01.0355.002; Sun, 22 Jan 2012 12:01:40 -0500
From: "NAPIERALA, MARIA H" <mn1921@att.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>, "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
Subject: RE: Possible Shutdown of L3VPN
Thread-Topic: Possible Shutdown of L3VPN
Thread-Index: AQHM2EHa7k8EYPJVdUGejXeUkd/tmpYYPMwAgAA/foCAACHKwA==
Date: Sun, 22 Jan 2012 17:01:40 +0000
Message-ID: <1D70D757A2C9D54D83B4CBD7625FA80EA81894@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <CAJNg7VJFnTEWEJWMRJ6dy+TFSEVqGtwmFGFCpPw8yzqExE_BRg@mail.gmail.com> <14C7F4F06DB5814AB0DE29716C4F6D671CF51277@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <E4F48EA2-B1BA-488F-A630-05B379691763@niven-jenkins.co.uk>
In-Reply-To: <E4F48EA2-B1BA-488F-A630-05B379691763@niven-jenkins.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.33.24]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
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 17:01:50 -0000

Ben,

There are also drafts that there are no WG documents, for example: draft-rosen-l3vpn-mvpn-segments-02.txt.

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