Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07

<stephane.litkowski@orange.com> Wed, 21 August 2019 08:29 UTC

Return-Path: <stephane.litkowski@orange.com>
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 8B6C212081F for <bess@ietfa.amsl.com>; Wed, 21 Aug 2019 01:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] 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 Hls0gE2Ip4yA for <bess@ietfa.amsl.com>; Wed, 21 Aug 2019 01:29:42 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CE7B120122 for <bess@ietf.org>; Wed, 21 Aug 2019 01:29:42 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 46D16r6Dl1z2yc9 for <bess@ietf.org>; Wed, 21 Aug 2019 10:29:40 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.20]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 46D16r5SkKzCqjh for <bess@ietf.org>; Wed, 21 Aug 2019 10:29:40 +0200 (CEST)
Received: from OPEXCAUBMA3.corporate.adroot.infra.ftgroup ([fe80::90fe:7dc1:fb15:a02b]) by OPEXCAUBMA1.corporate.adroot.infra.ftgroup ([fe80::f04d:ad3c:61de:a175%21]) with mapi id 14.03.0468.000; Wed, 21 Aug 2019 10:29:40 +0200
From: <stephane.litkowski@orange.com>
To: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07
Thread-Index: AQHVVzfZaZkrndeslkmw0SJ4JRyDf6cFRfxw
Date: Wed, 21 Aug 2019 08:29:40 +0000
Message-ID: <24083_1566376180_5D5D00F4_24083_196_1_9E32478DFA9976438E7A22F69B08FF924D9EE392@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
References: <CAKVaF1T08KLHtj6V56OynuwOcWSxugTZkRQd044GMdm-Or5MdA@mail.gmail.com>
In-Reply-To: <CAKVaF1T08KLHtj6V56OynuwOcWSxugTZkRQd044GMdm-Or5MdA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924D9EE392OPEXCAUBMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/1vH32JEjIDmq10HiVtaYVgIcXjE>
Subject: Re: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Aug 2019 08:29:45 -0000

Hi,

Speaking as individual, what is the goal of the vendor key ? Is it to allow a vendor to encode multiple “sub-types” with different vendor specific info ?  Or is it a security key ? That would be great to mention how a vendor should use it.

Thanks !

From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Stephane Litkowski
Sent: Monday, August 19, 2019 16:32
To: bess@ietf.org
Subject: [bess] WG adoption call and IPR poll for draft-rabadan-bess-vendor-evpn-route-07

Hi,

This email begins a two-weeks WG adoption poll for draft-rabadan-bess-vendor-evpn-route-07 [1]
Please review the draft and post any comments to the BESS working group list.

We are also polling for knowledge of any undisclosed IPR that applies to this Document, 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 an author or a contributor of this document, please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR, copying the BESS mailing list. The document won't progress without answers from all the authors and contributors.
Currently, there are no IPR disclosures against this document.

If you are not listed as an author or a contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

This poll for adoption closes on 2nd September 2019.

Regards,
Stephane and Matthew

[1] https://datatracker.ietf.org/doc/draft-rabadan-bess-vendor-evpn-route/

_________________________________________________________________________________________________________________________

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.