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

Adrian,

The update looks good to me, and thanks for adding that additional
paragraph to section 7.8.

Cheers,
Andy

On Mon, Feb 25, 2019 at 12:39 PM Adrian Farrel <adrian@olddog.co.uk> wrote:

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