Advertising Service Functions Using OSPF
draft-xu-ospf-service-function-adv-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-06-17
Replaces draft-xu-ospf-service-sid-adv
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
Network Working Group                                              X. Xu
Internet-Draft                                                     N. Wu
Intended status: Standards Track                                  Huawei
Expires: December 20, 2014                                       H. Shah
                                                                   Ciena
                                                           June 18, 2014

                Advertising Service Functions Using OSPF
                 draft-xu-ospf-service-function-adv-01

Abstract

   The Segment Routing mechanism can be leveraged to realize the service
   path layer functionality of the Service Function Chaining (i.e,
   steering traffic through the service function path).  This document
   describes how to advertise service functions and their corresponding
   characters (e.g.,service function segment ID) using OSPF.  Here the
   OSPF means both OSPFv2 and OSPFv3.

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 December 20, 2014.

Copyright Notice

   Copyright (c) 2014 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

Xu, et al.              Expires December 20, 2014               [Page 1]
Internet-Draft  Advertising Service Functions Using OSPF       June 2014

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Advertising Service Functions and Corresponding SIDs  . . . .   3
     3.1.  Service Function TLV  . . . . . . . . . . . . . . . . . .   3
     3.2.  Service Function 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-spring-sfc-use-case] describes a particular use case for
   SPRING where the Segment Routing (SR) mechanism is leveraged to
   realize the service path layer functionality of the Service Function
   Chaining (SFC), i.e, steering traffic through the service function
   path.  To allow a service classifier to encode the segment list
   representing a particular service function path, the classifier needs
   to know on which service node(s) a given service function is located
   and what segment ID (SID) is used to indicate that service function
   on a given service node.  This document describes how to advertise
   service functions and their corresponding characters (e.g.,service
   function segment ID) using OSPF.  Here the OSPF means both OSPFv2
   [RFC2328] and OSPFv3 [RFC2740].

1.1.  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].

2.  Terminology

   This memo makes use of the terms defined in [RFC4970].

Xu, et al.              Expires December 20, 2014               [Page 2]
Internet-Draft  Advertising Service Functions Using OSPF       June 2014

3.  Advertising Service Functions and Corresponding SIDs

   Service nodes within the network need to advertise each service
   function they are offering by using a TLV within the body of the OSPF
   Router Information (RI) Opaque LSA [RFC4970].  This new TLV is called
Show full document text