RE: IPLS

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Mon, 14 July 2014 13:14 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2C081A03C9 for <l2vpn@ietfa.amsl.com>; Mon, 14 Jul 2014 06:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76SwNlXax125 for <l2vpn@ietfa.amsl.com>; Mon, 14 Jul 2014 06:14:46 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0084.outbound.protection.outlook.com [213.199.154.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 682361A03C5 for <l2vpn@ietf.org>; Mon, 14 Jul 2014 06:14:46 -0700 (PDT)
Received: from AM3PR03MB612.eurprd03.prod.outlook.com (10.242.110.144) by AM3PR03MB611.eurprd03.prod.outlook.com (10.242.109.28) with Microsoft SMTP Server (TLS) id 15.0.985.8; Mon, 14 Jul 2014 13:14:44 +0000
Received: from AM3PR03MB612.eurprd03.prod.outlook.com ([10.242.110.144]) by AM3PR03MB612.eurprd03.prod.outlook.com ([10.242.110.144]) with mapi id 15.00.0980.000; Mon, 14 Jul 2014 13:14:44 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Loa Andersson <loa@pi.nu>
Subject: RE: IPLS
Thread-Topic: IPLS
Thread-Index: AQHPn1xMuCiwWlvA0UubT8IwXIg58Zufef9AgAAAc4CAAAPfwIAADCIAgAABHeA=
Date: Mon, 14 Jul 2014 13:14:44 +0000
Message-ID: <fd351d63532c4969b4dc3b7fe884ae98@AM3PR03MB612.eurprd03.prod.outlook.com>
References: <7D0D3E1D-294E-4A85-AA1D-A86A5F5C0E5F@gmail.com> <de97d3d3c89241bf90769f13dac39772@AM3PR03MB612.eurprd03.prod.outlook.com> <EBA5134E-6361-4CFD-A26A-FFBA43DB898C@gmail.com> <c634f9d1ca9e4bdca4ffd19f3f60a25f@AM3PR03MB612.eurprd03.prod.outlook.com> <53C3D61A.2090102@pi.nu>
In-Reply-To: <53C3D61A.2090102@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.56.21]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 02723F29C4
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(13464003)(53754006)(189002)(199002)(51444003)(377454003)(377424004)(24454002)(51704005)(252514010)(106356001)(86362001)(83322001)(80022001)(19580395003)(15975445006)(33646001)(74316001)(105586002)(19580405001)(31966008)(110136001)(107046002)(95666004)(93886003)(79102001)(20776003)(74662001)(2656002)(76576001)(85306003)(76176999)(54356999)(81342001)(85852003)(64706001)(76482001)(87936001)(74502001)(66066001)(21056001)(77982001)(99396002)(15202345003)(50986999)(92566001)(101416001)(81542001)(221733001)(106116001)(4396001)(46102001)(83072002)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:AM3PR03MB611; H:AM3PR03MB612.eurprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/5117J-QJN4sxlmzBVqL0Gmze43M
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2014 13:14:50 -0000

Loa,
Lots of thanks for a prompt response.

I agree that making a document permanently available  (for some degree of permanence:-) is a valid reason for publishing it as a Historic RFC.

Regards,
       Sasha 
Email: Alexander.Vainshtein@ecitele.com
Mobile: 054-9266302


> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: Monday, July 14, 2014 4:08 PM
> To: Alexander Vainshtein; Giles Heron
> Cc: l2vpn@ietf.org
> Subject: Re: IPLS
> 
> Sasha,
> 
> hmmm - the MPLS wg pubished RFC 6348, that is a requirement document,
> so in itself it has not been implemented or deployed; even if you can
> problably make the argument that specification fulfilling the requirements
> has.
> 
> I think that making a document is because we want it to available in the
> future.
> 
> /Loa
> 
> On 2014-07-14 14:27, Alexander Vainshtein wrote:
> > Hi Giles,
> > Lots of thanks for a prompt response.
> >
> > I have always thought that Historic RFCs describe something that has been
> implemented and deployed, but new standards are now in force.
> > E.g., original Martini drafts (which definitely have been implemented and
> deployed)  have been published as Historic RFCs.
> >
> > For the sake of curiosity, is this the case with IPLS?
> >
> > Regards,
> >         Sasha
> > Email: Alexander.Vainshtein@ecitele.com
> > Mobile: 054-9266302
> >
> >
> >> -----Original Message-----
> >> From: Giles Heron [mailto:giles.heron@gmail.com]
> >> Sent: Monday, July 14, 2014 3:10 PM
> >> To: Alexander Vainshtein
> >> Cc: l2vpn@ietf.org
> >> Subject: Re: IPLS
> >>
> >> Hi Sasha,
> >>
> >> yes - I believe that's the plan.
> >>
> >> Giles
> >>
> >> On 14 Jul 2014, at 13:09, Alexander Vainshtein
> >> <Alexander.Vainshtein@ecitele.com> wrote:
> >>
> >>> Giles,
> >>> Do you intend to progress it directly to Historic RFC?
> >>>
> >>> Regards,
> >>>        Sasha
> >>> Email: Alexander.Vainshtein@ecitele.com
> >>> Mobile: 054-9266302
> >>>
> >>>> -----Original Message-----
> >>>> From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Giles
> >>>> Heron
> >>>> Sent: Monday, July 14, 2014 3:08 PM
> >>>> To: l2vpn@ietf.org
> >>>> Subject: IPLS
> >>>>
> >>>> Hi all,
> >>>>
> >>>> the IPLS draft (probably the oldest draft ever to attempt to
> >>>> progress to RFC) was recently re-published as "historic" rather
> >>>> than
> >> "informational":
> >>>>
> >>>> http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-14
> >>>>
> >>>> To that end the IANA assignments requested in the draft were also
> >>>> withdrawn - though they could be re-instated if the draft were ever
> >>>> to progress.
> >>>>
> >>>> Based on these changes we now intend to progress this draft to RFC.
> >>>>
> >>>> Giles
> >>>>
> >>>
> >
> 
> --
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64