IPv6 Encapsulation for SFC and IFIT
draft-li-6man-ipv6-sfc-ifit-02

Document Type Active Internet-Draft (individual)
Last updated 2019-09-09
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                              Z. Li
Internet-Draft                                                   S. Peng
Intended status: Standards Track                     Huawei Technologies
Expires: March 13, 2020                                           K. LEE
                                                                   LG U+
                                                      September 10, 2019

                  IPv6 Encapsulation for SFC and IFIT
                     draft-li-6man-ipv6-sfc-ifit-02

Abstract

   Service Function Chaining (SFC) and In-situ Flow Information
   Telemetry (IFIT) are important path services along with the packets.
   In order to support these services, several encapsulations have been
   defined.  The document analyzes the problems of these encapsulations
   in the IPv6 scenario and proposes the possible optimized
   encapsulation for IPv6.

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 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 March 13, 2020.

Copyright Notice

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

Li, et al.               Expires March 13, 2020                 [Page 1]
Internet-Draft        IPv6 Encaps for SFC and IFIT        September 2019

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Design Consideration  . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Service Options . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  IPv6 Service Metadata Options . . . . . . . . . . . . . .   7
       4.2.1.  SFC Service Metadata Option . . . . . . . . . . . . .   7
       4.2.2.  IOAM Service Metadata Option  . . . . . . . . . . . .   8
       4.2.3.  IFA Service Metadata Option . . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Service Function Chaining (SFC) [RFC7665] and In-situ Flow
   Information Telemetry (IFIT) [I-D.song-opsawg-ifit-framework] are
   important path services along with the packets.  In order to support
   these services, several encapsulations have been defined.  Network
   Service Header (NSH) is defined in [RFC8300] as the encapsulation for
   SFC.  For IFIT encapsulations, In-situ OAM (iOAM) Header is defined
   in [I-D.ietf-ippm-ioam-data] and Postcard-Based Telemetry (PBT)
   Header is defined in [I-D.song-ippm-postcard-based-telemetry].
   Inband Flow Analyzer (IFA) is also defined in [I-D.kumar-ippm-ifa] to
   record flow specific information from an end station and/or switches
   across a network.  In the application scenario of IPv6, these
   encapsulations propose challenges for the data plane.  The document
   analyzes the problems and proposes the possible optimized
   encapsulation for IPv6.

Li, et al.               Expires March 13, 2020                 [Page 2]
Internet-Draft        IPv6 Encaps for SFC and IFIT        September 2019

2.  Terminology

   SFC: Service Function Chaining

   IFIT: In-situ Flow Information Telemetry
Show full document text