Network Service Header (NSH) Context Header Allocation: Timestamp
draft-mymb-sfc-nsh-allocation-timestamp-05

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

• Versions
• 00
• 01
• 02
• 03
• 04
• 05

Network Working Group                                         T. Mizrahi
Internet-Draft                          Huawei Network.IO Innovation Lab
Intended status: Informational                             I. Yerushalmi
Expires: April 13, 2019                                        D. Melman
                                                                 Marvell
                                                               R. Browne
                                                                   Intel
                                                        October 10, 2018

   Network Service Header (NSH) Context Header Allocation: Timestamp
               draft-mymb-sfc-nsh-allocation-timestamp-05

Abstract

   This memo defines an allocation for the Context Headers of the
   Network Service Header (NSH), which incorporates the packet's
   timestamp, a sequence number, and a source interface identifier.

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 13, 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
   include Simplified BSD License text as described in Section 4.e of

Mizrahi, et al.          Expires April 13, 2019                 [Page 1]
Internet-Draft                NSH Timestamp                 October 2018

   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 . . . . . . . . . . . . . . . . . .   3
     2.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   3
   3.  NSH Context Header Allocation . . . . . . . . . . . . . . . .   3
   4.  Timestamping Use Cases  . . . . . . . . . . . . . . . . . . .   5
     4.1.  Network Analytics . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Alternate Marking . . . . . . . . . . . . . . . . . . . .   6
     4.3.  Consistent Updates  . . . . . . . . . . . . . . . . . . .   6
   5.  Synchronization Considerations  . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The Network Service Header (NSH), defined in [I-D.ietf-sfc-nsh], is
   an encapsulation header that is used in Service Function Chains
   (SFC).

   The NSH specification [I-D.ietf-sfc-nsh] supports two possible
   methods of including metadata in the NSH; MD Type 0x1 and MD Type
   0x2.  When using MD Type 0x1 the NSH includes 16 octets of Context
   Header fields.  The current memo proposes an allocation for the MD
   Type 0x1 Context Headers, which incorporates the timestamp of the
   packet, a sequence number, and a source interface identifier.

   In a nutshell, packets that enter the SFC-Enabled Domain are
   timestamped.  The timestamp is measured by the Classifier [RFC7665],
   and incorporated in the NSH.  The timestamp may be used for various
   different purposes, including delay measurement, packet marking for
   passive performance monitoring, and timestamp-based policies.
   Notably, the timestamp does not increase the packet length, since it
   is incorporated in the MD Type 0x1 Mandatory Context Headers.

   The source interface identifier indicates the interface through which
   the packet was received at the classifier.  This identifer may
   specify a physical or a virtual interface.  The sequence numbers can
   be used by Service Functions (SFs) to detect out-of-order delivery or