Re: Document Action: 'IP-Only LAN Service (IPLS)' to Historic RFC (draft-ietf-l2vpn-ipls-16.txt)

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 04 November 2014 20:08 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 4B1931A7D80 for <l2vpn@ietfa.amsl.com>; Tue, 4 Nov 2014 12:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 I68KYSnoPK5h for <l2vpn@ietfa.amsl.com>; Tue, 4 Nov 2014 12:08:45 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0733.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::733]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59D7A1A701D for <l2vpn@ietf.org>; Tue, 4 Nov 2014 12:08:44 -0800 (PST)
Received: from DB4PR03MB395.eurprd03.prod.outlook.com (10.242.231.16) by DB4PR03MB393.eurprd03.prod.outlook.com (10.242.231.11) with Microsoft SMTP Server (TLS) id 15.1.11.14; Tue, 4 Nov 2014 20:06:39 +0000
Received: from DB4PR03MB395.eurprd03.prod.outlook.com ([10.242.231.16]) by DB4PR03MB395.eurprd03.prod.outlook.com ([10.242.231.16]) with mapi id 15.01.0011.000; Tue, 4 Nov 2014 20:06:39 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Himanshu Shah <hshah@ciena.com>
Subject: Re: Document Action: 'IP-Only LAN Service (IPLS)' to Historic RFC (draft-ietf-l2vpn-ipls-16.txt)
Thread-Topic: Document Action: 'IP-Only LAN Service (IPLS)' to Historic RFC (draft-ietf-l2vpn-ipls-16.txt)
Thread-Index: AQHP+GrX6BBaRx8xsk+3J0xSvg7jog==
Date: Tue, 04 Nov 2014 20:06:38 +0000
Message-ID: <6e9af99517a740c89715e137149d680e@DB4PR03MB395.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Infraware POLARIS Mobile Mailer v2.5
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [109.253.135.119]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR03MB393;
x-exchange-antispam-report-test: UriScan:;
x-forefront-prvs: 03853D523D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(51704005)(189002)(377454003)(479174003)(199003)(24454002)(21056001)(33646002)(46102003)(4396001)(110136001)(230783001)(104166001)(19617315012)(31966008)(106356001)(64706001)(50226001)(20776003)(106116001)(105586002)(66066001)(99396003)(16236675004)(108616004)(107046002)(120916001)(19625215002)(2656002)(76576001)(101416001)(74316001)(87286001)(88136002)(87936001)(19580395003)(15975445006)(95666004)(77156002)(89996001)(92566001)(50986999)(86362001)(15202345003)(93916002)(40100003)(122556002)(62966003)(19580405001)(97736003)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR03MB393; H:DB4PR03MB395.eurprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_6e9af99517a740c89715e137149d680eDB4PR03MB395eurprd03pro_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/ebnMGFElkio5sq6e9PUF8hWhYJs
Cc: l2vpn mailing list <l2vpn@ietf.org>, l2vpn chair <l2vpn-chairs@tools.ietf.org>, "Ali Sajassi (sajassi)" <sajassi@cisco.com>
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: Tue, 04 Nov 2014 20:08:48 -0000

Himanshu,

My congratulations as well.

You have improved your earlier record IMO on the "longest time in the IETF limbo" draft (ARP Mediation is now second bedt). A historic high, so getting this as a Historic RFC is only just...



Regards,



Thumb typed on my LG,
Sasha

------ Original message ------
From: Ali Sajassi (sajassi)
Date: 04/11/2014 19:23
To: The IESG;IETF-Announce;
Cc: l2vpn mailing list;l2vpn chair;RFC Editor;
Subject:Re: Document Action: 'IP-Only LAN Service (IPLS)' to Historic RFC (draft-ietf-l2vpn-ipls-16.txt)


Himanshu,

Congrats! It only took 13 years for it to become a RFC :-) Look at the
bright side of it - it happened while you are still alive :-)


Cheers,
Ali

On 11/4/14, 4:50 AM, "The IESG" <iesg-secretary@ietf.org> wrote:

>The IESG has approved the following document:
>- 'IP-Only LAN Service (IPLS)'
>  (draft-ietf-l2vpn-ipls-16.txt) as Historic RFC
>
>This document is the product of the Layer 2 Virtual Private Networks
>Working Group.
>
>The IESG contact persons are Adrian Farrel and Alia Atlas.
>
>A URL of this Internet Draft is:
>http://datatracker.ietf.org/doc/draft-ietf-l2vpn-ipls/
>
>
>
>
>Technical Summary:
>
>   A Virtual Private LAN Service (VPLS) is used to interconnect
>   systems across a wide-area or metropolitan-area network, making it
>   appear that they are on a private LAN.  The systems which are
>   interconnected may themselves be LAN switches.  If, however, they
>   are IP hosts or IP routers, certain simplifications to the operation
>   of the VPLS are possible.  We call this simplified type of VPLS an
>   "IP-only LAN Service" (IPLS).  In an IPLS, as in a VPLS, LAN
>   interfaces are run in promiscuous mode, and frames are forwarded
>   based on their destination MAC addresses.  However, the maintenance
>   of the MAC forwarding tables is done via signaling, rather than via
>   the MAC address learning procedures specified in [IEEE 802.1D].
>   This draft specifies the protocol extensions and procedures for
>   support of the IPLS service.
>
>   The original intent was to provide an alternate solution to VPLS
>   for those PE routers that were not capable of learning MAC address
>   through data plane. This became a non-issue with newer hardware.
>   The concepts put forth by this draft are still valuable and are
>   adopted in one form or other by newer work such as Ethernet VPN
>   in L2VPN Working Group and possible data center applications. At
>   this point, no further action is planned to update this document
>   and is published simply as a historic record of the ideas.
>
>Working Group Summary:
>
>   This document is an L2VPN Working Group document, and has been
>reviewed in
>   the working group through multiple iterations of the draft.  It was
>considered to be an
>   informational draft, with the last few iterations of the draft now
>cleaning up references.
>   There was considerable debate during and after the WG last call which
>resulted in
>   new revisions being issued to resolve various comments.
>
>   After discussion with the serving AD, the document was changed to be
>Historic. Thus
>   it presents a record of the working group discussions. The revised I-D
>was also
>   shown to the WG to check for any concerns.
>
>Document Quality:
>
>    The document provides a clear and concise set of requirements for
>IPLS - broken
>    down into different requirement areas.  As a requirements draft there
>is no protocol
>    implement.
>
>Personnel:
>
>     Document Shepherd: Andrew McLachlan (amclachl@cisco.com)
>     Area Director: Adrian Farrel (adrian@olddog.co.uk)
>