Operating the Network Service Header (NSH) with Next Protocol "None"
draft-farrel-sfc-convent-05

Document Type Active Internet-Draft (sfc WG)
Last updated 2018-01-17 (latest revision 2017-12-29)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tal Mizrahi
Shepherd write-up Show (last changed 2018-01-08)
IESG IESG state In Last Call (ends 2018-01-31)
Consensus Boilerplate Yes
Telechat date On agenda of 2018-02-08 IESG telechat
Responsible AD Alia Atlas
Send notices to Tal Mizrahi <tal.mizrahi.phd@gmail.com>
IANA IANA review state IANA - Review Needed
IANA action state None
SFC Working Group                                              A. Farrel
Internet-Draft                                                  J. Drake
Intended status: Standards Track                        Juniper Networks
Expires: July 2, 2018                                  December 29, 2017

  Operating the Network Service Header (NSH) with Next Protocol "None"
                      draft-farrel-sfc-convent-05

Abstract

   This document describes the use of the Network Service Header (NSH)
   in a Service Function Chaining (SFC) enabled network with no payload
   data and carrying only metadata.  This is achieved by defining a new
   NSH "Next Protocol" type value of "None".

   This document illustrates some of the functions that may be achieved
   or enhanced by this mechanism, but it does not provide an exhaustive
   list of use cases, nor is it intended to be definitive about the
   functions it describes.  It is expected that other documents will
   describe specific use cases in more detail and will define the
   protocol mechanics for each use case.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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/.

   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 July 2, 2018.

Farrel & Drake            Expires July 2, 2018                  [Page 1]
Internet-Draft              NSH With No Data               December 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Network Service Header  . . . . . . . . . . . . . . . . .   3
     2.1.  Next Protocol 'None'  . . . . . . . . . . . . . . . . . .   4
   3.  Processing Rules  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Backward Compatibility  . . . . . . . . . . . . . . . . . . .   5
   5.  Overview of Use Cases . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Per-SFP Metadata  . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Per-Flow Metadata . . . . . . . . . . . . . . . . . . . .   6
     5.3.  Coordination Between SFC-Aware SFIs . . . . . . . . . . .   6
     5.4.  Operations, Administration, and Maintenance (OAM) . . . .   7
     5.5.  Control Plane and Management Plane Uses . . . . . . . . .   8
     5.6.  Non-Applicable Use Cases  . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   An architecture for Service Function Chaining (SFC) is presented in
   [RFC7665].  That architecture enables packets to be forwarded along
   Service Function Paths (SFPs) to pass through various Service
   Functions (SFs) that act on the packets.  Each packet is encapsulated
   with a Network Service Header (NSH) [I-D.ietf-sfc-nsh]  that
   identifies the SFP that the packet travels along (by means of a
   Service Path Identifier - SPI) and the hop (i.e., the next SF to be
Show full document text