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

Document Type Active Internet-Draft (individual)
Last updated 2017-05-10
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: November 11, 2017                                       H. Shah
                                                                   Ciena
                                                            L. Contreras
                                                          Telefonica I+D
                                                            May 10, 2017

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

Abstract

   The MPLS source routing mechanism developed by Source Packet Routing
   in Networking (SPRING) WG can be leveraged to realize a unified
   source routing instruction which works across both IPv4 and IPv6
   underlays in addition to the MPLS underlay.  The unified source
   routing instruction can be used to realize a transport-independent
   service function chaining by encoding the service function path
   information or service function chain information as an MPLS label
   stack.  This document describes how to advertise service functions
   and their corresponding attributes (e.g., service function label)
   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 November 11, 2017.

Xu, et al.              Expires November 11, 2017               [Page 1]
Internet-Draft                                                  May 2017

Copyright Notice

   Copyright (c) 2017 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 Label 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 the unified
   source routing instruction
   [I-D.xu-mpls-unified-source-routing-instruction] to realize a
   transport-independent service function chaining by encoding the
   Service Function Path (SFP) or Service Function Chain (SFC)
   information as an MPLS label stack.  To allow a service classifier to
   attach the MPLS label stack which represents a particular SFP or SFC
   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 service function label is used to indicate that
Show full document text