From nobody Sun Jan 4 21:33:21 2015 Return-Path: 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 4C4741A1B9A for ; Sun, 4 Jan 2015 21:33:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.612 X-Spam-Level: X-Spam-Status: No, score=-12.612 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 xyRrXIne7K9B for ; Sun, 4 Jan 2015 21:33:18 -0800 (PST) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECBE01A1B8B for ; Sun, 4 Jan 2015 21:33:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3424; q=dns/txt; s=iport; t=1420435998; x=1421645598; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=0INgOLwIAcWWhTVV4dSKBXqZSqLSD/rsBX9AcheqlxI=; b=cBB3EjUst33MjkLBt3+rOeoVpsjGcBQDECXRT32853HaZlRrEms4snmb gvNPgx9W1ZFNdnziMaMH7Q1+feNn4nJjiHMZ1V4n6risB+2IxLGWpasYF lIwEzsB5pRoM07GUe6aE9W7zubIqFSv7JIhV6bR9chntp5DBebH0UWDBu g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlMFAHIhqlStJA2N/2dsb2JhbABZA4MGUlgExhmFcQKBAxYBAQEBAX2EDAEBAQQdSR8CAgIBCBEEAQELHQcbFxQJCAIEARIIAYgjDalrkWgBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBI8REQEfCxYSBQYLgwWBEwWJIYR0gz+GQTCCNYolgzkiggcXFIE8bwGBBAcXIn4BAQE X-IronPort-AV: E=Sophos;i="5.07,697,1413244800"; d="scan'208";a="110289678" Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-5.cisco.com with ESMTP; 05 Jan 2015 05:33:17 +0000 Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t055XGIe021659 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 Jan 2015 05:33:16 GMT Received: from xmb-rcd-x05.cisco.com ([169.254.15.149]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Sun, 4 Jan 2015 23:33:16 -0600 From: "Dennis Cai (dcai)" To: "Patrice Brissette (pbrisset)" , Thomas Morin , "l2vpn@ietf.org" , "draft-boutros-l2vpn-evpn-vpws@tools.ietf.org" Subject: RE: [l2vpn] WG adoption call for the draft VPWS support in E-VPN, draft-boutros-l2vpn-evpn-vpws-04 Thread-Topic: [l2vpn] WG adoption call for the draft VPWS support in E-VPN, draft-boutros-l2vpn-evpn-vpws-04 Thread-Index: AQHP4Wf/IEE4/SOI90yxqPAYncXWcJyWBSwAgAA3zgCAAZYYAIAZvD/g Date: Mon, 5 Jan 2015 05:33:16 +0000 Message-ID: <623637051A3DC34E80FC9BA35B4629951D37A3C3@xmb-rcd-x05.cisco.com> References: <5492E264.7080001@orange.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.24.13.166] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/ZuVzfAmJmp2mtZHjhn4zrEk67og X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Layer 2 Virtual Private Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2015 05:33:20 -0000 I am not aware of any IPR associated with this draft. -----Original Message----- From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Patrice Brissette = (pbrisset) Sent: Friday, December 19, 2014 6:33 AM To: Thomas Morin; l2vpn@ietf.org; draft-boutros-l2vpn-evpn-vpws@tools.ietf.= org Subject: Re: [l2vpn] WG adoption call for the draft VPWS support in E-VPN, = draft-boutros-l2vpn-evpn-vpws-04 Hi Thomas, I'm not aware of any IPR related to that draft. Regards, Patrice Patrice Brissette TECHNICAL LEADER.ENGINEERING pbrisset@cisco.com Phone: +1 613 254 3336 Cisco Systems Canada Co. / Les Systemes Cisco Canada CIE Canada Cisco.com <= http://www.cisco.com/global/CA/> Think before you print.This email may contain confidential and privileged material for the sole use o= f the intended recipient. Any review, use, distribution or disclosure by ot= hers is strictly prohibited. If you are not the intended recipient (or auth= orized to receive for the recipient), please contact the sender by reply em= ail and delete all copies of this message. Please click here for Co= mpany Registration Information. On 2014-12-18, 9:19 AM, "Thomas Morin" wrote: >Hi everyone, > >Before formally adopting this in BESS, we need an answer from each >co-author on this recurrent reminder question about existing knowledge >of any IPR that applies to this draft, to ensure that IPR has been >disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 >and 5378 for more details). > >=3D=3D> *If you are listed as a document author or contributor* please >respond to this email and indicate whether or not you are aware of any >relevant IPR. > >The draft will not be adopted until a response has been received from >each author and contributor. > >If you are not listed as an author or contributor, then please >explicitly respond only if you are aware of any IPR that has not yet >been disclosed in conformance with IETF rules. > >Best, > >-Thomas/Martin > > >Nabil: >> Hi, >> For the record, this call had closed on October 20. The draft has good >> support. The authors are to work with the BESS WG chairs to issue this >>draft as a BESS working group draft. >> >> Thanks, >> Nabil & Giles >> _____________________________ >> From: Bitar, Nabil >> N >> Sent: Monday, October 06, 2014 9:16 AM >> To: l2vpn@ietf.org >> Cc: Giles Heron; >> amclachl@cisco.com >> Subject: [l2vpn] WG adoption call for the draft VPWS >> support in E-VPN, draft-boutros-l2vpn-evpn-vpws-04 >> >> L2VPN WG, >> >> This is the >> start of a 2-week call for adopting the draft =B3VPWS support in E-VPN= =B2, >> draft-boutros-l2vpn-evpn-vpws-04, as an L2VPN WG document. The draft >>can be >> found at: http://www.ietf.org/id/draft-boutros-l2vpn-evpn-vpws-04.txt >> >> This >> draft was well supported in the WG meeting in Toronto, but as always we >>are >> taking it to the list to decide on WG adoption. Please, reply to this >>email >> indicating your support or objection to adopting this draft as a WG >> document. Substantive comments in addition to indicating your support or >> objection are appreciated >> >> This call will close on Monday, October 20, >> 2014. >> >> >> Thanks, >> Nabil & Giles >> >> >> > From nobody Wed Jan 14 14:44:37 2015 Return-Path: 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 27B421ACF02; Wed, 14 Jan 2015 14:44:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.912 X-Spam-Level: X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 zGAl6TQCDEgW; Wed, 14 Jan 2015 14:44:22 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id ECD621ACEDE; Wed, 14 Jan 2015 14:44:13 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 1801F1832B8; Wed, 14 Jan 2015 14:43:25 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Subject: RFC 7436 on IP-Only LAN Service (IPLS) X-PHP-Originating-Script: 6000:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20150114224325.1801F1832B8@rfc-editor.org> Date: Wed, 14 Jan 2015 14:43:25 -0800 (PST) Archived-At: Cc: l2vpn@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org X-BeenThere: l2vpn@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Layer 2 Virtual Private Networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 22:44:30 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7436 Title: IP-Only LAN Service (IPLS) Author: H. Shah, E. Rosen, F. Le Faucheur, G. Heron Status: Historic Stream: IETF Date: January 2015 Mailbox: hshah@ciena.com, erosen@juniper.net, flefauch@cisco.com, giheron@cisco.com Pages: 32 Characters: 74340 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-l2vpn-ipls-16.txt URL: https://www.rfc-editor.org/info/rfc7436 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 that 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 Media Access Control (MAC) addresses. However, the maintenance of the MAC forwarding tables is done via signaling, rather than via the MAC address learning procedures specified in the IEEE's "Media Access Control (MAC) Bridges". This document 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 Provider Edge (PE) routers that were not capable of learning MAC addresses through data plane. This became a non-issue with newer hardware. The concepts put forth by this document 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 it is published simply as a historic record of the ideas. This document is a product of the Layer 2 Virtual Private Networks Working Group of the IETF. HISTORIC: This memo defines a Historic Document for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC