Active OAM for Service Function Chaining
draft-ietf-sfc-multi-layer-oam-09

Document Type Active Internet-Draft (sfc WG)
Authors Greg Mirsky  , Wei Meng  , Bhumip Khasnabish  , Cui(Linda) Wang 
Last updated 2021-02-11
Replaces draft-wang-sfc-multi-layer-oam
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
SFC WG                                                         G. Mirsky
Internet-Draft                                                 ZTE Corp.
Updates: 8300 (if approved)                                      W. Meng
Intended status: Standards Track                         ZTE Corporation
Expires: August 15, 2021                                   B. Khasnabish
                                                                 C. Wang
                                                  Individual contributor
                                                       February 11, 2021

                Active OAM for Service Function Chaining
                   draft-ietf-sfc-multi-layer-oam-09

Abstract

   A set of requirements for active Operation, Administration, and
   Maintenance (OAM) of Service Function Chains (SFCs) in a network is
   presented in this document.  Based on these requirements, an
   encapsulation of active OAM messages in SFC and a mechanism to detect
   and localize defects are described.

   This document updates RFC 8300 in the definition of O (OAM) bit in
   the Network Service Header (NSH) and defines how an active OAM
   message is identified in the NSH.

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 August 15, 2021.

Copyright Notice

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

Mirsky, et al.           Expires August 15, 2021                [Page 1]
Internet-Draft             Active OAM for SFC              February 2021

   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 and Conventions . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Requirements for Active OAM in SFC Network  . . . . . . . . .   4
   4.  Active OAM Identification in SFC NSH  . . . . . . . . . . . .   6
   5.  Echo Request/Echo Reply for SFC . . . . . . . . . . . . . . .   8
     5.1.  Return Codes  . . . . . . . . . . . . . . . . . . . . . .  10
     5.2.  Authentication in Echo Request/Reply  . . . . . . . . . .  11
     5.3.  SFC Echo Request Transmission . . . . . . . . . . . . . .  11
     5.4.  SFC Echo Request Reception  . . . . . . . . . . . . . . .  12
       5.4.1.  Errored TLVs TLV  . . . . . . . . . . . . . . . . . .  12
     5.5.  SFC Echo Reply Transmission . . . . . . . . . . . . . . .  13
     5.6.  SFC Echo Reply Reception  . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  SFC Active OAM Protocol . . . . . . . . . . . . . . . . .  15
     8.2.  SFC Active OAM Message Type . . . . . . . . . . . . . . .  15
     8.3.  SFC Echo Request/Echo Reply Parameters  . . . . . . . . .  16
     8.4.  SFC Echo Request/Echo Reply Message Types . . . . . . . .  16
     8.5.  SFC Echo Reply Modes  . . . . . . . . . . . . . . . . . .  17
     8.6.  SFC Echo Return Codes . . . . . . . . . . . . . . . . . .  18
     8.7.  SFC TLV Type  . . . . . . . . . . . . . . . . . . . . . .  19
     8.8.  SFC OAM UDP Port  . . . . . . . . . . . . . . . . . . . .  20
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   [RFC7665] defines components necessary to implement a Service
   Function Chain (SFC).  These include:
Show full document text