Re: [bess] Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02

"Oya Luengo, Roberto (Nokia - US)" <roberto.oya_luengo@nokia.com> Fri, 05 February 2016 23:39 UTC

Return-Path: <roberto.oya_luengo@nokia.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518821B2FB6; Fri, 5 Feb 2016 15:39:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 Zj67gUunfzfV; Fri, 5 Feb 2016 15:39:53 -0800 (PST)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-01.alcatel-lucent.com [135.245.18.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11A241B2FB5; Fri, 5 Feb 2016 15:39:52 -0800 (PST)
Received: from us70uumx3.dmz.alcatel-lucent.com (unknown [135.245.18.15]) by Websense Email Security Gateway with ESMTPS id EBDA6BCEE504D; Fri, 5 Feb 2016 23:39:47 +0000 (GMT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (us70uusmtp3.zam.alcatel-lucent.com [135.5.2.65]) by us70uumx3.dmz.alcatel-lucent.com (GMO) with ESMTP id u15NdpCi030068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 5 Feb 2016 23:39:51 GMT
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id u15NdpA9019253 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 5 Feb 2016 23:39:51 GMT
Received: from US70TWXCHMBA10.zam.alcatel-lucent.com ([169.254.4.60]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0195.001; Fri, 5 Feb 2016 18:39:51 -0500
From: "Oya Luengo, Roberto (Nokia - US)" <roberto.oya_luengo@nokia.com>
To: "thomas.morin@orange.com" <thomas.morin@orange.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02
Thread-Index: AQHRYG6BXB7JK7ocQLKDXemsWvLl+Q==
Date: Fri, 05 Feb 2016 23:39:50 +0000
Message-ID: <D2DA72BB.535AF%roberto.oya_luengo@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.8.151023
x-originating-ip: [135.5.27.17]
Content-Type: multipart/alternative; boundary="_000_D2DA72BB535AFrobertooyaluengoalcatellucentcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/bess/-ZSY44wYjLbpmAx_WCOh707jwOs>
X-Mailman-Approved-At: Fri, 05 Feb 2016 22:10:16 -0800
Cc: "draft-snr-bess-evpn-proxy-arp-nd@ietf.org" <draft-snr-bess-evpn-proxy-arp-nd@ietf.org>
Subject: Re: [bess] Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 23:39:56 -0000

Support

From: BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of "thomas.morin@orange.com<mailto:thomas.morin@orange.com>" <thomas.morin@orange.com<mailto:thomas.morin@orange.com>>
Date: Friday, February 5, 2016 at 8:56 AM
To: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Cc: "draft-snr-bess-evpn-proxy-arp-nd@ietf.org<mailto:draft-snr-bess-evpn-proxy-arp-nd@ietf.org>" <draft-snr-bess-evpn-proxy-arp-nd@ietf.org<mailto:draft-snr-bess-evpn-proxy-arp-nd@ietf.org>>
Subject: [bess] Call for adoption: draft-snr-bess-evpn-proxy-arp-nd-02


Hello working group,

This email starts a two-week poll on adopting draft-snr-bess-evpn-proxy-arp-nd [1] as a working group item.

Please send comments to the list and state if you support adoption or not (in the later case, please also state the reasons).

This poll runs until **February 19th**.

*Coincidentally*, we are also polling for 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.

Thank you,

Martin & Thomas
bess chairs

[1] https://tools.ietf.org/html/draft-snr-bess-evpn-proxy-arp-nd-02

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.