Name-Based Service Function Forwarder (nSFF) component within SFC framework
draft-trossen-sfc-name-based-sff-07

Document Type Active Internet-Draft (individual)
Last updated 2019-08-29 (latest revision 2019-05-26)
Stream ISE
Intended RFC status Informational
Formats plain text xml pdf htmlized bibtex
IETF conflict review conflict-review-trossen-sfc-name-based-sff
Stream ISE state Sent to the RFC Editor
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2019-05-26)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state RFC-EDITOR
Network Working Group                                         D. Trossen
Internet-Draft                                  InterDigital Europe, Ltd
Intended status: Informational                            D. Purkayastha
Expires: November 27, 2019                                     A. Rahman
                                        InterDigital Communications, LLC
                                                            May 26, 2019

   Name-Based Service Function Forwarder (nSFF) component within SFC
                               framework
                  draft-trossen-sfc-name-based-sff-07

Abstract

   Adoption of cloud and fog technology allows operators to deploy a
   single "Service Function" to multiple "Execution locations".  The
   decision to steer traffic to a specific location may change
   frequently based on load, proximity etc.  Under the current SFC
   framework, steering traffic dynamically to the different execution
   end points require a specific 're-chaining', i.e., a change in the
   service function path reflecting the different IP endpoints to be
   used for the new execution points.  This procedure may be complex and
   take time.  In order to simplify re-chaining and reduce the time to
   complete the procedure, we discuss separating the logical Service
   Function Path from the specific execution end points.  This can be
   done by identifying the Service Functions using a name rather than a
   routable IP endpoint (or Layer 2 address).  This document describes
   the necessary extensions, additional functions and protocol details
   in SFF (Service Function Forwarder) to handle name based
   relationships.

   This document presents InterDigital's approach to name-based service
   function chaining.  It does not represent IETF consensus and is
   presented here so that the SFC community may benefit from considering
   this mechanism and the possibility of its use in the edge data
   centers.

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 https://datatracker.ietf.org/drafts/current/.

Trossen, et al.         Expires November 27, 2019               [Page 1]
Internet-Draft               Name Based SFF                     May 2019

   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 27, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Example use case: 5G control plane services . . . . . . . . .   4
   4.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Relevant part of SFC architecture . . . . . . . . . . . .   6
     4.2.  Challenges with current framework . . . . . . . . . . . .   7
   5.  Name based operation in SFF . . . . . . . . . . . . . . . . .   8
     5.1.  General Idea  . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Name-Based Service Function Path (nSFP) . . . . . . . . .   8
     5.3.  Name Based Network Locator Map (nNLM) . . . . . . . . . .  10
     5.4.  Name-based Service Function Forwarder (nSFF)  . . . . . .  12
     5.5.  High Level Architecture . . . . . . . . . . . . . . . . .  13
     5.6.  Operational Steps . . . . . . . . . . . . . . . . . . . .  14
   6.  nSFF Forwarding Operations  . . . . . . . . . . . . . . . . .  16
     6.1.  nSFF Protocol Layers  . . . . . . . . . . . . . . . . . .  16
     6.2.  nSFF Operations . . . . . . . . . . . . . . . . . . . . .  18
       6.2.1.  Forwarding between nSFFs and nSFF-NR  . . . . . . . .  18
       6.2.2.  SF Registration . . . . . . . . . . . . . . . . . . .  21
       6.2.3.  Local SF Forwarding . . . . . . . . . . . . . . . . .  22
       6.2.4.  Handling of HTTP responses  . . . . . . . . . . . . .  23
Show full document text