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

"Mankamana Mishra (mankamis)" <mankamis@cisco.com> Mon, 07 January 2019 22:54 UTC

Return-Path: <mankamis@cisco.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 CD32F12E036 for <bess@ietfa.amsl.com>; Mon, 7 Jan 2019 14:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.565
X-Spam-Level:
X-Spam-Status: No, score=-14.565 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 jjen_-43Xrlj for <bess@ietfa.amsl.com>; Mon, 7 Jan 2019 14:54:55 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23D1812DDA3 for <bess@ietf.org>; Mon, 7 Jan 2019 14:54:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=31380; q=dns/txt; s=iport; t=1546901695; x=1548111295; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=+H9IQlJ4u+613n1VPSHf/ivd4G6I5SoK9xsL0A53uWI=; b=mzSp8v38pzttMCijQLqSQVCw4J1rgBK5k3zx7h4iR0qkEM2eysqupKK9 WiRRHAwD1Oqo75PEhXGg7zgI0x1fmdXtRfym94GZwLKg0gwLXQ1ra5lVn qfirwGjT1/uDr20cC2ytD6BXjH5A4GhNfTs2mBwSycWPUCduJAd6EONII 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAACF2DNc/40NJK1jGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ1ILmaBAicKg3WIGotrgWgll28UgWc?= =?us-ascii?q?LAQElhEcCF4FtIjQJDQEDAQECAQECbRwMhUoBAQEEI2YCAQgRAwEBASEHAwI?= =?us-ascii?q?CAjAUCQgBAQQBEoMiAYEdZA+nJoEvhC0BE0CFLAWMPxeBQD+BEScME4JMgx4?= =?us-ascii?q?BAQIBAYEqARIBJhAJFgKCUDGCJgKJNgqBEYR/hmGLKwkChxKKXRiBYIUjimy?= =?us-ascii?q?JFAlFhQWLLwIRFIEnHzgoPXFwFWUBgkEJgkiITIU/QTGIRYEfgR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.56,451,1539648000"; d="scan'208,217";a="502948493"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jan 2019 22:54:36 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x07MsaoU021067 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 7 Jan 2019 22:54:36 GMT
Received: from xch-rcd-008.cisco.com (173.37.102.18) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 7 Jan 2019 16:54:35 -0600
Received: from xch-rcd-008.cisco.com ([173.37.102.18]) by XCH-RCD-008.cisco.com ([173.37.102.18]) with mapi id 15.00.1395.000; Mon, 7 Jan 2019 16:54:35 -0600
From: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.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+OMrGu2oHHStwLEptGQBAXuyQAAKwRogA==
Date: Mon, 7 Jan 2019 22:54:35 +0000
Message-ID: <5F598AF2-6122-4ED9-9D42-EE7955463AB8@cisco.com>
References: <17128_1543833795_5C0508C3_17128_38_7_9E32478DFA9976438E7A22F69B08FF924B778825@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <7578_1545051284_5C179C94_7578_408_1_1749d600-0efb-4b68-b2b4-99d469ca024c@OPEXCLILM5E.corporate.adroot.infra.ftgroup> <B61D4B20-4FB7-400B-9E5C-C90E7D32D468@cisco.com>
In-Reply-To: <B61D4B20-4FB7-400B-9E5C-C90E7D32D468@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.161.154]
Content-Type: multipart/alternative; boundary="_000_5F598AF261224ED99D42EE7955463AB8ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/FBeS67euzMtXDYl9pfTI1E673AY>
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: Mon, 07 Jan 2019 22:54:58 -0000

Thanks Ali for addressing my comments.

Sorry, some how I missed initially but not sure if these section have to be filled before it goes to next step, or it can move forward and  you can take care of this in next revision.


8<https://tools.ietf.org/html/draft-ietf-bess-evpn-virtual-eth-segment-01#section-8>-8>. Security Considerations This document does not introduce anyadditional security constraints. <This has to go inside paragraph, right now it is part of heading. And you might want to say that it does not introduce any additional security consideration compare to RFC 7432 or any other RFC which you want to point out>



9<https://tools.ietf.org/html/draft-ietf-bess-evpn-virtual-eth-segment-01#section-9>-9>. IANA Considerations


   TBD.  >>>>>> I think this document does add some new EC, do we need to write something here about it ?


Thanks
Mankamana


From: BESS <bess-bounces@ietf.org> on behalf of "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Date: Sunday, January 6, 2019 at 7:23 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

Hi Stephane,

I just checked in a new revision of the document that incorporates the comments from Sasha and Mankamana. Rick also responded to the IPR call, so we are good to go.

Cheers,
Ali

From: BESS <bess-bounces@ietf.org> on behalf of "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>
Date: Monday, December 17, 2018 at 4:55 AM
To: LITKOWSKI Stephane OBS/OINIS <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

Hi,

The WGLC poll is now ended.
We have one comment from Mankamana that requires a reply from the authors.

We are also missing an IPR reply from Richard Schnell from Verizon.

We can’t proceed before clearing these two points.

Brgds,

Stephane



From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com
Sent: Monday, December 03, 2018 11:43
To: 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.