BGP Control Plane for NSH SFC
draft-ietf-bess-nsh-bgp-control-plane-04
| Document | Type | Expired Internet-Draft (bess WG) | |
|---|---|---|---|
| Authors | Adrian Farrel , John Drake , Eric C. Rosen , Jim Uttaro , Luay Jalil | ||
| Last updated | 2019-01-02 (Latest revision 2018-07-01) | ||
| Replaces | draft-mackie-bess-nsh-bgp-control-plane | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
RTGDIR Last Call review
(of
-13)
Has Issues
OPSDIR Last Call review
(of
-13)
Has Issues
GENART Last Call review
(of
-12)
Ready with Issues
|
||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-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
John Drake
Eric C. Rosen
Jim Uttaro
Luay Jalil
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)