IANA is request to create a new subregistry called the "SFC Attribute TLVs" registry. o Values 5 are to be marked "Reserved, not to be allocated".
IANA maintains a registry of "Border Gateway Protocol (BGP) Parameters".
This document defines a control plane for Service Function Chaining.
However, this specification does not change the existence of Service Function Chaining and security issues specific to Service Function Chaining are covered in [RFC7665] and [I-D.ietf-sfc-nsh].
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.
I-D] | Date-to-be-set [I-D.ietf-idr-tunnel-encaps] Rosen, E., Patel, K., and G. Elzur, "Network Service Header", draft- ietf-sfc-nsh-10 (work in progress), September 2016.
The new registry should track: o Value o Name o Reference Document or Contact o Registration Date The registry should initially be populated as follows: Value | Name | Reference | Date ------ ----------------------- --------------- --------------- 1 | Change Sequence | [This.
General Rules For The Service Function Chain Attribute .
Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF).
Protocol Control of Looping, Jumping, and Branching .
Velde, "The BGP Tunnel Encapsulation Attribute", draft-ietf-idr-tunnel-encaps-02 (work in progress), May 2016. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, John Drake Juniper Networks Email: [email protected] Rosen Juniper Networks Email: [email protected] Uttaro AT&T Email: [email protected] Jalil Verizon Email: [email protected], et al.