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

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 03 June 2019 10:00 UTC

Return-Path: <adrian@olddog.co.uk>
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 7A3C712010D for <bess@ietfa.amsl.com>; Mon, 3 Jun 2019 03:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level:
X-Spam-Status: No, score=-2.596 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_NONE=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 w_oAgGZTbgfK for <bess@ietfa.amsl.com>; Mon, 3 Jun 2019 02:59:59 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64312120004 for <bess@ietf.org>; Mon, 3 Jun 2019 02:59:59 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id x539xu77016800; Mon, 3 Jun 2019 10:59:57 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2F23722050; Mon, 3 Jun 2019 10:59:57 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id 1A0CE2204A; Mon, 3 Jun 2019 10:59:57 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.172.175]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x539xtUb021803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 3 Jun 2019 10:59:56 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: stephane.litkowski@orange.com, 'Susan Hares' <shares@ndzh.com>, bess@ietf.org
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> <13974_1559546693_5CF4CB45_13974_63_5_9E32478DFA9976438E7A22F69B08FF924C230F27@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <13974_1559546693_5CF4CB45_13974_63_5_9E32478DFA9976438E7A22F69B08FF924C230F27@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
Date: Mon, 03 Jun 2019 10:59:54 +0100
Organization: Old Dog Consulting
Message-ID: <00e401d519f3$187f4940$497ddbc0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E5_01D519FB.7A462240"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQFDc2J2M3q0g0nwjqUkmWgq38rqVgJF6ERPAbWCq1sCFF0ZNAGq+4lup28onVA=
Content-Language: en-gb
X-Originating-IP: 87.112.172.175
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24654.006
X-TM-AS-Result: No--35.982-10.0-31-10
X-imss-scan-details: No--35.982-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24654.006
X-TMASE-Result: 10--35.981500-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFrxIbpQ8BhdbIVMtEwAWsdcxXRDKEyu2zFGpg/nZAuJ/Rfo +oVE2PIvqc7+9x7aAUZU3LEkb35TTQMwOZUXOlJ48KQMqZXaCzkZSo6PM4Lsikhcmj54ab4U28T WUhJNQdntKEHVxyUbVW53M7Tz7E6rKXGXWv7oGogqWbR3GHCDGyIk3dpe5X+hjr+PnGtGztPcla yGYv+Tv98O6sGX8A554ffQ6oExXGr4miWUEaTQPmsBfpoHMapl4NNiN6MhlPAXY+gNTubOQNtuL nl6rSi7UUoNBhw+3ES023N+wvUXQP85GCR7+Gth9m9PbNihg7A5iooXtStiHrQnfFdSRlnduwtu U4MtDuWquR4bEQmavzeaoPpP+53JcO+orlNZmqZLIfps09VJ2/aS52LUPfcSfqFWsdsssTcqjJT 3U5+KOf91gmVjVa5iynhLA9cPR3ldjYupu5cMz0Vt+RM6im3+1nzAvzCY2qyu408c9ly810nYUV lmOUsMiit0R2zg5cH2C/LOoCIZTLcJ/zjQ+NPdWRfN4zFaLod3WgoPkw7b1Sd0mOGtcEbC/9xks itWU1mRmtHBJfjm5OOs6/h/QRAd+rKpThFtmT2tBybNxXyi/BIO7Iu9ucMGMafFtBI3ERnSKUtb L1AAi5M2d9YHqWlmi/7tBBBxVMVEXwnTCGfm3f0peXGEEBlvrogFtKd/P7cLBZEuqIL9SpO9mQG x4jC3Sa7i4WMGYwF/2SsgU8jyNW7vEKjEI8LygNylVbI/EAxbD9LQcHt6gzAx/HIgP92dNEZZmA O2JUhbY4OE3kF6CUBggEfJoaep+rU9PV9YsWKeAiCmPx4NwGmRqNBHmBve1B0Hk1Q1KyLr8uVzX avvg1KMqIeOstifOMB0shqXhHr/NH80kzpMASu4tEBXMp6BZ6EqJkHM71mDTqgf6U1uSRBmvgiA ym96
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Kqh0d-T0oSOUTf54pnwocPCSLOw>
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 10:00:03 -0000

Very happy to have more comments and help to clarify our text.

 

At this stage the authors believe they have addressed all comments received during working group last call and from the shepherd’s review. But (of course) any review that points up a problem or suggests a clarification is a good review, and we would love to see it.

 

Thanks,

Adrian

 

From: BESS <bess-bounces@ietf.org> On Behalf Of stephane.litkowski@orange.com
Sent: 03 June 2019 08:25
To: Susan Hares <shares@ndzh.com>; bess@ietf.org
Subject: Re: [bess] Poll to progress draft-ietf-bess-nsh-bgp-controlplane without implementation

 

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.