OAM for Service Programming with Segment Routing
draft-ali-spring-sr-service-programming-oam-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
spring                                                            Z. Ali
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                               N. Nainar
Expires: April 21, 2019                                     C. Pignataro
                                                                 F. Clad   
                                                                F. Iqbal
                                                     Cisco Systems, Inc.
                                                                   X. Xu
                                                            Alibaba Inc.
                                                        October 22, 2018

            OAM for Service Programming with Segment Routing
              draft-ali-spring-sr-service-programming-oam-00

Abstract

   This document defines the Operations, Administrations and Maintenance 
   (OAM) for service programming in SR-enabled MPLS and IP networks. 

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 April 21, 2019.

Copyright Notice

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

Ali, et al.              Expires April 19, 2019                 [Page 1]
Internet-Draft                  SR-SP OAM                   October 2018

   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.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Programmable OAM  . . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  Service Programming OAM Packet Marker . . . . . . . . . .   3
     5.2.  OAM with SR-aware services  . . . . . . . . . . . . . . .   3
     5.3.  OAM with SR-unaware services  . . . . . . . . . . . . . .   4
     5.4.  Controlling OAM packet processing in Services . . . . . .   4
   6.  OAM for Service Programming with SRv6 . . . . . . . . . . . .   4
     6.1.  OAM Tool Kit  . . . . . . . . . . . . . . . . . . . . . .   5
       6.1.1.  ICMP  . . . . . . . . . . . . . . . . . . . . . . . .   5
       6.1.2.  UDP Probes  . . . . . . . . . . . . . . . . . . . . .   5
       6.1.3.  OAM Flag Processing . . . . . . . . . . . . . . . . .   6
       6.1.4.  OAM Segment ID  . . . . . . . . . . . . . . . . . . .   6
       6.1.5.  In-band OAM . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  Example with ICMPv6 Ping  . . . . . . . . . . . . . . . .   6
   7.  OAM for Service Programming with SR-MPLS  . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   8
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   [I-D.draft-xuclad-spring-sr-service-programming] defines data plane 
   functionality required to implement service segments and achieve service 
   programming in SR-enabled MPLS and IP networks, as described in the 
   Segment Routing architecture. This document defines the Operations, 
   Administrations and Maintenance (OAM) for service programming in 
   SR-enabled MPLS and IP networks. 

2.  Requirements notation

   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 [RFC2119].

Ali, et al.              Expires April 19, 2019                 [Page 2]
Show full document text