RE: [l2vpn] WG adoption call for the draft VPWS support in E-VPN, draft-boutros-l2vpn-evpn-vpws-04

John E Drake <jdrake@juniper.net> Thu, 18 December 2014 17:45 UTC

Return-Path: <jdrake@juniper.net>
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 A3FA11A901E for <l2vpn@ietfa.amsl.com>; Thu, 18 Dec 2014 09:45:41 -0800 (PST)
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 Fkq0t1QnqefM for <l2vpn@ietfa.amsl.com>; Thu, 18 Dec 2014 09:45:35 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0127.outbound.protection.outlook.com [207.46.100.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4945C1A8F4C for <l2vpn@ietf.org>; Thu, 18 Dec 2014 09:45:35 -0800 (PST)
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB561.namprd05.prod.outlook.com (10.141.202.139) with Microsoft SMTP Server (TLS) id 15.1.49.12; Thu, 18 Dec 2014 17:45:32 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.01.0049.002; Thu, 18 Dec 2014 17:45:32 +0000
From: John E Drake <jdrake@juniper.net>
To: "EXT - thomas.morin@orange.com" <thomas.morin@orange.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>, "draft-boutros-l2vpn-evpn-vpws@tools.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: AQHP4WfnqghG2LM5vUy93Ud/0O4vDpxdmJvVgDg/ygCAADlBYA==
Date: Thu, 18 Dec 2014 17:45:31 +0000
Message-ID: <BLUPR05MB562048793510E7C0130150BC76A0@BLUPR05MB562.namprd05.prod.outlook.com>
References: <DFEE5C63-7ED6-4DEE-AA2D-2082E711C085@gmail.com>, <EE3DB9B68D417942A9B1863918E159FA124555F356@FLDP1LUMXC7V63.us.one.verizon.com>, <EE3DB9B68D417942A9B1863918E159FA124555F359@FLDP1LUMXC7V63.us.one.verizon.com> <EE3DB9B68D417942A9B1863918E159FA12486DC1E5@FLDP1LUMXC7V63.us.one.verizon.com> <5492E264.7080001@orange.com>
In-Reply-To: <5492E264.7080001@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.239.10]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jdrake@juniper.net;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB561;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB561;
x-forefront-prvs: 042957ACD7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(6009001)(164054003)(189002)(377454003)(13464003)(51704005)(53754006)(199003)(99286002)(2900100001)(107046002)(2950100001)(64706001)(20776003)(40100003)(86362001)(105586002)(46102003)(107886001)(54606007)(93886004)(122556002)(106356001)(106116001)(4396001)(54356999)(54206007)(2201001)(77096005)(15975445007)(76176999)(92566001)(66066001)(50986999)(102836002)(76576001)(97736003)(21056001)(74316001)(87936001)(2501002)(33656002)(68736005)(120916001)(77156002)(99396003)(62966003)(2656002)(101416001)(31966008)(19580405001)(230783001)(19580395003)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB561; H:BLUPR05MB562.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Dec 2014 17:45:31.4713 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB561
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/ljE2RYlHHwlY8hFdJ_TUUj5yW0U
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: Thu, 18 Dec 2014 17:45:41 -0000

Thomas,

I am not aware of any IPR associated w/ this draft.

Yours Irrespectively,

John

> -----Original Message-----
> From: L2vpn [mailto:l2vpn-bounces@ietf.org] On Behalf Of Thomas Morin
> Sent: Thursday, December 18, 2014 9:19 AM
> To: 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 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).
> 
> ==> *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 ³VPWS support in E-VPN²,
> > 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
> >
> >
> >