Subject: [sfc] Update to BGP for SFC: I-D Action: draft-mackie-bess-nsh-bgp-control-plane-04.txt

From: "Adrian Farrel" <[email-masked]>
Date: Mon, 13 Feb 2017 17:42:22 -0000

Hi SFC WG,

Just a note to point you to an update of our draft on using BGP as the control
plane for SFC.

Apart from a few minor tweaks to wording, the main changes are:

- 4.3 Clarify the scope of uniqueness of SPI
- 4.5.1 New section on handling lacunae in the SI sequence
- 5 Add initial paragraphs on multiple SFTs at a single hop
- 7.6 Clarify bit setting rules in the SPI/SI Representation sub-TLV 

As previously noted, this is a cross-posting for a draft targeted at BESS. You
can discuss it anywhere, but probably best to restrict your comments to BESS or
SFC.

Adrian

> -----Original Message-----
> From: I-D-Announce [mailto:[email-masked]] On Behalf Of
> [email-masked]
> Sent: 13 February 2017 17:17
> To: [email-masked]
> Subject: I-D Action: draft-mackie-bess-nsh-bgp-control-plane-04.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
> 
>         Title           : BGP Control Plane for NSH SFC
>         Authors         : Adrian Farrel
>                           John Drake
>                           Eric Rosen
>                           Jim Uttaro
>                           Luay Jalil
> 	Filename        : draft-mackie-bess-nsh-bgp-control-plane-04.txt
> 	Pages           : 52
> 	Date            : 2017-02-13
> 
> 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-mackie-bess-nsh-bgp-control-plane/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-mackie-bess-nsh-bgp-control-plane-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-mackie-bess-nsh-bgp-control-plane-04
> 
> 
> 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
> [email-masked]
> 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