Re: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-06.txt

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 26 February 2019 08:50 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 38DCB1228B7 for <bess@ietfa.amsl.com>; Tue, 26 Feb 2019 00:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 SeCm2BlDx0Td for <bess@ietfa.amsl.com>; Tue, 26 Feb 2019 00:50:34 -0800 (PST)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 CFDDD130E95 for <bess@ietf.org>; Tue, 26 Feb 2019 00:50:33 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x1Q8oVT6005138; Tue, 26 Feb 2019 08:50:31 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A96EF2203D; Tue, 26 Feb 2019 08:50:31 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id 93E8A2203C; Tue, 26 Feb 2019 08:50:31 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.112.237.8]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x1Q8oUnE022216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Feb 2019 08:50:31 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: stephane.litkowski@orange.com, bess@ietf.org
References: <155111521251.10690.6116598025512863065@ietfa.amsl.com> <020801d4cd31$0b387d10$21a97730$@olddog.co.uk> <32522_1551170249_5C74FAC9_32522_238_4_9E32478DFA9976438E7A22F69B08FF924C198DC5@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <32522_1551170249_5C74FAC9_32522_238_4_9E32478DFA9976438E7A22F69B08FF924C198DC5@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
Date: Tue, 26 Feb 2019 08:50:28 -0000
Organization: Old Dog Consulting
Message-ID: <02f001d4cdb0$530f5940$f92e0bc0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKHCMqDjrMamo/xhc6WZyeNYrhf5QHqO+MWAGtXLHSkeqBwoA==
Content-Language: en-gb
X-Originating-IP: 87.112.237.8
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-24456.005
X-TM-AS-Result: No--27.163-10.0-31-10
X-imss-scan-details: No--27.163-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24456.005
X-TMASE-Result: 10--27.163300-10.000000
X-TMASE-MatchedRID: oll/cJ/dUC7xIbpQ8BhdbOYAh37ZsBDCCQ3xS+zL6e2ZVv3vkd2dt3Z5 WvuLBD7qBt5KNd+dhyo65ruFXpKsmsnUsvxvsR6SFhQfbPNnjNs/FeJYf9wxdc+7FhXMB7ia8gv cSKVCSkK2tDoRCzmPJgt1FbTRkWhlN8ZpC5zlYTrThGbP9qB93DtSuYjPEOigxSZxKZrfThNbRF Mz0XghAo3YFjIOixzkRpInzGQ53+sLazoQyrpm0i0x8J2DopENNcII11l+erjjsTquy0JRix5Qc SoVnpgLm/Z2TxxGY4nIa/iDijEsybM5yFdOCNfRVU3yVpaj3Qz4bPjfm0hIQWjof4lG8KmQVnhu VlhvAMUFmt4ek24vckRtiShpxWHK+0A8R+vxw9u1PiMh4ZF39ZhwKdlCfPk8DO+DX+rUwfZncpG Qs7S9GTRzIRIo4G/0Bc5l05FO6qvk18JBpE0OqjAoNxJKRrVrdyejMZ27QTi/+hl14/Ope1Hwbc 2EVWYnVF4Z94ujWnode6CFnVoZk74b+dXCdFMOstOuzx/1YL/SBVBNwL95D2Mnw0UE3R8SBEh2n CFqjWVpSX2FvJ+6NSYbdS7ICG966ZNJZlkJ+m7Wkykw8PZpKtrH4KCM7gKEVH9mNMbazyXCDcjF 5OS/iHwDvs5w2tBmMvRDxDGXhjNtcr/uuDMv3hMMmcrjEONdfS0Ip2eEHny+qryzYw2E8M8943o c3p3s4mKBXpZ1/+1TptoDfp6JrMRB0bsfrpPIqxB32o9eGclVaBFytIQUtw==
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/N2tJ5st87Qsp6c4SKEJKT-qZ4J8>
Subject: Re: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-06.txt
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, 26 Feb 2019 08:50:37 -0000

Thanks Stephane,

I understand.

It may be hard to track down Eric: I understand he has retired.

I will ask Ron Bonica if he can reach him, but otherwise I would note:
- We an move him to the Contributors section to avoid Auth-48 issues
- As an author on the document he has already confirmed that he has
  complied with BCP 78 and 79
- There is Juniper IPR already disclosed
- John Drake has given you IPR assurances and, as a Juniper employee,
  It is likely that he has done the same IPR search that Eric would have
  done.

Let's see whether we can wake up Jim, Stuart, Keyur, and Avinash.

Thanks,
Adrian

-----Original Message-----
From: stephane.litkowski@orange.com <stephane.litkowski@orange.com> 
Sent: 26 February 2019 08:37
To: adrian@olddog.co.uk; bess@ietf.org
Subject: RE: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-06.txt

Hi Adrian,

Yes it is ready, we will proceed with the shepherd's review. However, we
don't have any sign of implementation or roadmap yet, we (chairs) will have
to ask the WG to determine a consensus to progress the document without an
implementation (as per our implementation policy).

In addition, I missing the IPR poll reply from: Jim, Eric, Stuart, Keyur,
Avinash.

Brgds,


-----Original Message-----
From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Monday, February 25, 2019 18:39
To: bess@ietf.org
Subject: Re: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-06.txt

All,

Thanks for the comments we received during WG last call.

John and I have also re-reviewed the entire text.

We made a small number of little changes resulting from these activities.

Chairs: I think we are ready to move forward.

Best,
Adrian

-----Original Message-----
From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
internet-drafts@ietf.org
Sent: 25 February 2019 17:20
To: i-d-announce@ietf.org
Cc: bess@ietf.org
Subject: I-D Action: draft-ietf-bess-nsh-bgp-control-plane-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the BGP Enabled ServiceS WG of the IETF.

        Title           : BGP Control Plane for NSH SFC
        Authors         : Adrian Farrel
                          John Drake
                          Eric Rosen
                          Jim Uttaro
                          Luay Jalil
	Filename        : draft-ietf-bess-nsh-bgp-control-plane-06.txt
	Pages           : 55
	Date            : 2019-02-25

Abstract:
   This document describes the use of BGP as a control plane for
   networks that support Service Function Chaining (SFC).  The document
   introduces a new BGP address family called the SFC AFI/SAFI with two
   route types.  One route type is originated by a node to advertise
   that it hosts a particular instance of a specified service function.
   This route type also provides "instructions" on how to send a packet
   to the hosting node in a way that indicates that the service function
   has to be applied to the packet.  The other route type is used by a
   Controller to advertise the paths of "chains" of service functions,
   and to give a unique designator to each such path so that they can be
   used in conjunction with the Network Service Header.

   This document adopts the SFC architecture described in RFC 7665.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bess-nsh-bgp-control-plane-06
https://datatracker.ietf.org/doc/html/draft-ietf-bess-nsh-bgp-control-plane-
06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-nsh-bgp-control-plane-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_______________________________________________
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.