BGP Control Plane for NSH SFC
draft-mackie-bess-nsh-bgp-control-plane-04

Document Type Replaced Internet-Draft (bess WG)
Last updated 2017-03-24 (latest revision 2017-02-13)
Replaced by draft-ietf-bess-nsh-bgp-control-plane
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text xml pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-bess-nsh-bgp-control-plane
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mackie-bess-nsh-bgp-control-plane-04.txt

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.

Authors

Adrian Farrel (afarrel@juniper.net)
John Drake (jdrake@juniper.net)
Eric Rosen (erosen@juniper.net)
Jim Uttaro (ju1738@att.com)
Luay Jalil (luay.jalil@verizon.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)