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

Hi,

We made some small tweaks to this document mainly to bring it in line with
draft-farrel-mpls-sfc (no need to describe the MPLS forwarding plane in a BESS
document).
We also added the concept of a pool of service function instances so that an SFP
can be scoped more tightly than by generic SF type, but less tightly than a
specific SFI. It also allows the choice of SFI to be delegated to the SFFs on
the SFP.

Cheers,
Adrian

> -----Original Message-----
> From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: 30 October 2017 20:28
> To: i-d-announce@ietf.org
> Cc: bess@ietf.org
> Subject: [bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-02.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-02.txt
> 	Pages           : 53
> 	Date            : 2017-10-30
> 
> 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-02
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-nsh-bgp-control-plane-02
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-nsh-bgp-control-plane-02
> 
> 
> 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/
> 
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess