Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

<stephane.litkowski@orange.com> Tue, 04 December 2018 20:05 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 C4D55130E59 for <bess@ietfa.amsl.com>; Tue, 4 Dec 2018 12:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 nNrUmvcE6AhX for <bess@ietfa.amsl.com>; Tue, 4 Dec 2018 12:05:07 -0800 (PST)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BE2F130DFD for <bess@ietf.org>; Tue, 4 Dec 2018 12:05:07 -0800 (PST)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 438XsF403Mz2xpd; Tue, 4 Dec 2018 21:05:05 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.42]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 438XsF352kz1xp6; Tue, 4 Dec 2018 21:05:05 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM41.corporate.adroot.infra.ftgroup ([fe80::c845:f762:8997:ec86%19]) with mapi id 14.03.0415.000; Tue, 4 Dec 2018 21:05:05 +0100
From: <stephane.litkowski@orange.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment
Thread-Index: AdSK9MoVutPXDdgmS+OMrGu2oHHStwAjMPqAABv/6AAABr27EA==
Date: Tue, 4 Dec 2018 20:05:04 +0000
Message-ID: <10032_1543953905_5C06DDF1_10032_39_1_9E32478DFA9976438E7A22F69B08FF924B77DA1A@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <17128_1543833795_5C0508C3_17128_38_7_9E32478DFA9976438E7A22F69B08FF924B778825@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <905966EE-A8D9-4D05-81E8-FE59A9BFE2C8@cisco.com> <F6E8D7D8-51D0-44DF-B60F-346E13109FEA@cisco.com>
In-Reply-To: <F6E8D7D8-51D0-44DF-B60F-346E13109FEA@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.2]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924B77DA1AOPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/jj7BeJ3UYHeWosKPpUyceZZpIhM>
Subject: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment
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: Tue, 04 Dec 2018 20:05:10 -0000

Done, I have marked the –ietf- document replacing the individual one. The IPR is now inherited.

From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Tuesday, December 04, 2018 20:53
To: LITKOWSKI Stephane OBS/OINIS; bess@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment

Hi Stephane,

It seems like the IPR that I was talking about has already been disclosed in April of this year. The disclosure is on draft-sajassi-bess-evpn-virtual-eth-segment<https://datatracker.ietf.org/ipr/3169/>-03gt;-03. Since the history of its WG draft version doesn’t show the individual draft revisions, the IPR doesn’t appear for WG draft version. Can you fix it so that the history of the individual drafts appear on the WG draft history?

Regards,
Ali

From: BESS <bess-bounces@ietf.org> on behalf of Cisco Employee <sajassi@cisco.com>
Date: Monday, December 3, 2018 at 10:29 PM
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>om>, "bess@ietf.org" <bess@ietf.org>
Subject: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment



There is one IPR related to this draft that I thought it was disclosed but it wasn’t. I put request  for it to be disclosed ASAP. The term for it is the same as any other Cisco IPR disclosure.
Regarding implementation, this draft has been implemented in Cisco products for quite some time.

Regards,
Ali

From: BESS <bess-bounces@ietf.org> on behalf of "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>
Date: Monday, December 3, 2018 at 2:43 AM
To: "bess@ietf.org" <bess@ietf.org>
Subject: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-virtual-eth-segment


Hello Working Group,



This email starts a two-week Working Group Last Call on draft-ietf-bess-evpn-virtual-eth-segment [1]



This poll runs until *the 17th of December*.



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. The Document won't progress without answers from all the Authors and Contributors.



There is currently no IPR disclosed.



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.



We are also polling for any existing implementation as per [2].



    Thank you,

    Stephane & Matthew



    [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/



    [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw



_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________

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.