Re: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation

<stephane.litkowski@orange.com> Mon, 03 June 2019 07:24 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 182DE120183 for <bess@ietfa.amsl.com>; Mon, 3 Jun 2019 00:24:58 -0700 (PDT)
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 oSr9LHtKapfD for <bess@ietfa.amsl.com>; Mon, 3 Jun 2019 00:24:55 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3718312017D for <bess@ietf.org>; Mon, 3 Jun 2019 00:24:55 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 45HRQY4fsNz10Z0; Mon, 3 Jun 2019 09:24:53 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.54]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 45HRQY3jSxzDq9Q; Mon, 3 Jun 2019 09:24:53 +0200 (CEST)
Received: from OPEXCAUBMA3.corporate.adroot.infra.ftgroup ([fe80::90fe:7dc1:fb15:a02b]) by OPEXCAUBM7D.corporate.adroot.infra.ftgroup ([fe80::bcfe:4850:e646:f223%21]) with mapi id 14.03.0439.000; Mon, 3 Jun 2019 09:24:53 +0200
From: stephane.litkowski@orange.com
To: Susan Hares <shares@ndzh.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation
Thread-Index: AQHU69hrDYv6Ub5ZQ+6evU81c/qWSaYtuDsAgBwGlfCAOkebgIAF3AyQ
Date: Mon, 03 Jun 2019 07:24:52 +0000
Message-ID: <13974_1559546693_5CF4CB45_13974_63_5_9E32478DFA9976438E7A22F69B08FF924C230F27@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
References: <38B95AA4-9D4D-47BC-9265-DC08DE70BBA9@vmware.com> <7a35c463-43ae-40e1-a0a1-da8501210c5d@Spark> <15924_1556020501_5CBEFD15_15924_204_9_9E32478DFA9976438E7A22F69B08FF924C1EF389@OPEXCAUBMA3.corporate.adroot.infra.ftgroup> <008201d516ff$d290bc70$77b23550$@ndzh.com>
In-Reply-To: <008201d516ff$d290bc70$77b23550$@ndzh.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_9E32478DFA9976438E7A22F69B08FF924C230F27OPEXCAUBMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/fYInusVYEPVCjt9-YuTeXfe3S4k>
Subject: Re: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation
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, 03 Jun 2019 07:24:58 -0000

Hi Sue,

Thanks.
This part is still under review and is not closed. If you have any particular comments, feel free to send the details. It would be great if you could also help the authors on the flowspec part of the draft if you think that it is not fully clear.

Brgds,

Stephane


From: Susan Hares [mailto:shares@ndzh.com]
Sent: Thursday, May 30, 2019 17:53
To: LITKOWSKI Stephane OBS/OINIS; bess@ietf.org
Subject: RE: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation

Stephane:

[RFC5575bis author hat on]
In progressing the draft without an implementation, please review carefully to the error handling text that Adrian just added.

Sue

From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com
Sent: Tuesday, April 23, 2019 7:55 AM
To: bess@ietf.org
Subject: Re: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation

Hi,

We have a good amount of support to progress the document with implementations.
We (chairs) are now waiting for the next I-D update to move forward.

Brgds,


From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com]
Sent: Friday, April 05, 2019 19:55
To: LITKOWSKI Stephane OBS/OINIS; Sami Boutros
Cc: bess@ietf.org
Subject: Re: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation

yes/support

Cheers,
Jeff
On Apr 5, 2019, 10:53 AM -0700, Sami Boutros <boutross=40vmware.com@dmarc.ietf.org>, wrote:

Support, Please progress the document.



Thanks,



Sami



Hi WG,



draft-ietf-bess-nsh-bgp-controlplane has passed WGLC and its finishing the shepherd's review phasis (I-D update required). It is in a good shape to progress further. However we are not aware of any implementation. As per our Implementation Requirement Policy, we need to poll the WG to know if WG agrees to progress the document without implementation.



This email starts a 2 weeks poll closing on 04/18/2019.



Please raise your support or any concern regarding the progress of this document without implementation.

If you are aware of any implementation, please also state it.





https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/



Brgds,



Stephane & Matthew

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

_________________________________________________________________________________________________________________________



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.