Advertising Service Functions Using IS-IS
draft-xu-isis-service-function-adv-04

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Replaces draft-xu-isis-service-sid-adv
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ISIS Working Group                                                 X. Xu
Internet-Draft                                                     N. Wu
Intended status: Standards Track                                  Huawei
Expires: May 4, 2017                                             H. Shah
                                                                   Ciena
                                                            L. Contreras
                                                          Telefonica I+D
                                                        October 31, 2016

               Advertising Service Functions Using IS-IS
                 draft-xu-isis-service-function-adv-04

Abstract

   Source Packet Routing in Networking (SPRING) WG is developing an MPLS
   source routing mechanism.  This MPLS source routing mechanism can be
   leveraged to realize the service path layer functionality of the
   service function chaining (i.e., steering the selected traffic
   through a particular service function path) by encoding the service
   function path information as an MPLS label stack.  This document
   describes how to advertise service functions and their corresponding
   attributes (e.g.,segment ID) using IS-IS.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Xu, et al.                 Expires May 4, 2017                  [Page 1]
Internet-Draft                                              October 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Solution Description  . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Service Function Sub-TLV  . . . . . . . . . . . . . . . .   3
     3.2.  SF SID Sub-TLV  . . . . . . . . . . . . . . . . . . . . .   4
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [I-D.xu-mpls-service-chaining] describes how to leverage MPLS-SPRING
   [I-D.ietf-spring-segment-routing-mpls] (a.k.a., an MPLS-based source
   routing mechanism) to realize the service path layer functionality of
   the Service Function Chaining (SFC), i.e, steering traffic through
   the Service Function Path (SFP).  To allow a service classifier to
   attach the segment list (i.e., an MPLS label stack) which represents
   a particular SFP to the selected traffic, the service classifier
   needs to know on which Service Function Forwarder (SFF) a given
   Service Function (SF) is located and what segment ID (SID) is used to
   indicate that SF.  This document describes how to advertise Service
   Functions (SFs) and their corresponding attributes (e.g.,SID) using
Show full document text