A Light Weight IOAM for SRv6 Network Programming
draft-li-spring-light-weight-srv6-ioam-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Network Working Group                                              C. Li
Internet-Draft                                                   M. Chen
Intended status: Standards Track                              S. Previdi
Expires: June 22, 2019                                            Huawei
                                                                   Z. Li
                                                            China Mobile
                                                       December 19, 2018

            A Light Weight IOAM for SRv6 Network Programming
               draft-li-spring-light-weight-srv6-ioam-00

Abstract

   In-situ OAM(IOAM) records OAM information within the packet while the
   packet traverses a particular network domain.  A discussion of the
   motivation and requirements for in-situ OAM can be found in
   [I-D.brockners-inband-oam-requirements].

   This document defines a light weight IOAM method for SRv6 network
   programming.  In this method, IOAM information is carried in the data
   packet by the SIDs in the SRH.

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 June 22, 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

Li, et al.                Expires June 22, 2019                 [Page 1]
Internet-Draft        Light Weight IOAM for SRv6 NP        December 2018

   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
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  SRv6 Light Weight IOAM  . . . . . . . . . . . . . . . . . . .   4
     3.1.  The FLAG Field of SID . . . . . . . . . . . . . . . . . .   4
   4.  Capabilities and SID Format Advertisement . . . . . . . . . .   5
   5.  SIDs Distribution . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Packet Processing . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Source SR Node  . . . . . . . . . . . . . . . . . . . . .   6
       6.1.1.  Reduced SRH . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  Transit Node  . . . . . . . . . . . . . . . . . . . . . .   7
     6.3.  SR Segment Endpoint Node  . . . . . . . . . . . . . . . .   7
       6.3.1.  Egress Node . . . . . . . . . . . . . . . . . . . . .   7
     6.4.  Instructions for FLAG . . . . . . . . . . . . . . . . . .   8
   7.  Illustrations . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Timestamp Recording Procedures  . . . . . . . . . . . . .  10
   8.  Backward Compatibility Considerations . . . . . . . . . . . .  10
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   11. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  11
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     13.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Segment routing (SR) [RFC8402] is a source routing paradigm that
   explicitly indicates the forwarding path for packets at the source
   node by inserting an ordered list of instructions, called segments.
   A segment can represent a topological or service-based instruction.

   When segment routing is deployed on IPv6 dataplane, called SRv6
   [I-D.ietf-6man-segment-routing-header], a segment is a 128 bit value,
   and it can be an IPv6 address of a local interface but it does not
   have to.  As defined in