IETF Logo Mail Archive

Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

<Thomas.Beckhaus@telekom.de> Wed, 01 June 2016 06:55 UTC

Return-Path: <Thomas.Beckhaus@telekom.de>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62FAB12D10D for <bess@ietfa.amsl.com>; Tue, 31 May 2016 23:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level:
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=no
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 IxVKq8IsGpVU for <bess@ietfa.amsl.com>; Tue, 31 May 2016 23:55:11 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 837E812D114 for <bess@ietf.org>; Tue, 31 May 2016 23:55:10 -0700 (PDT)
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by tcmail11.telekom.de with ESMTP/TLS/DHE-RSA-AES128-SHA; 01 Jun 2016 08:55:07 +0200
X-IronPort-AV: E=Sophos;i="5.26,400,1459807200"; d="scan'208";a="890786902"
Received: from he113656.emea1.cds.t-internal.com ([10.134.99.16]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES128-SHA; 01 Jun 2016 08:55:06 +0200
Received: from HE113645.emea1.cds.t-internal.com ([fe80::a029:1dc9:1076:f497]) by HE113656.emea1.cds.t-internal.com ([10.134.99.16]) with mapi; Wed, 1 Jun 2016 08:55:06 +0200
From: Thomas.Beckhaus@telekom.de
To: martin.vigoureux@nokia.com
Date: Wed, 01 Jun 2016 08:55:04 +0200
Thread-Topic: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03
Thread-Index: AdGmvIE6sNtwGKKlQRyjVDZGQt0ghwVFdxXg
Message-ID: <D4F0EAADB2501841AC9836BEC0EF1ED9017EDD025385@HE113645.emea1.cds.t-internal.com>
References: <572B2655.3020605@alcatel-lucent.com>
In-Reply-To: <572B2655.3020605@alcatel-lucent.com>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
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/bess/aMPXPyIhfOkhgYicFr771HHPmQA>
Cc: bess@ietf.org
Subject: Re: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Jun 2016 06:55:13 -0000

Hi Martin,

I am not aware of any relevant undisclosed IPR.

Thomas

-----Ursprüngliche Nachricht-----
Von: BESS [mailto:bess-bounces@ietf.org] Im Auftrag von Martin Vigoureux
Gesendet: Donnerstag, 5. Mai 2016 12:54
An: BESS
Betreff: [bess] WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hello Working Group,

Please read carefully, this e-mail contains new elements compared to other WG LCs.

This email starts a Working Group Last Call on
draft-ietf-bess-evpn-vpws-03 [1].

¤ Please read the document if you haven't read the most recent version yet, and send your comments to the list, no later than *20th of May*.
Note that this is *not only* a call for comments on the document, but also a call for support (or not) publishing this document as a Proposed Standard RFC.

¤ We are also polling for knowledge of any undisclosed IPR that applies to draft-ietf-bess-evpn-vpws-03, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details) prior to moving forward.
If you are listed as a document Author or Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The document won't progress without answers from all the Authors and Contributors.
Two IPR disclosures exist against previous revisions of this document [2].

¤ We are also polling for knowledge of implementations of part or all of what this document specifies. This information is expected as per [3]. 
Please inform the mailing list, the chairs, or only one of the chairs.

¤ Finally, if someone wishes to volunteer to be Document Shepherd for this document, please let us know.

Thank you
M&T


[1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-vpws/
[2]
https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-bess-evpn-vpws
[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

v2.23.0 | Report a Bug | By Email