Key Performance Indicator (KPI) Stamping for the Network Service Header (NSH)
RFC 8592

Document Type RFC - Informational (May 2019; No errata)
Last updated 2019-05-15
Replaces draft-browne-sfc-nsh-timestamp
Stream ISE
Formats plain text pdf html bibtex
IETF conflict review conflict-review-browne-sfc-nsh-kpi-stamp
Stream ISE state Published RFC
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2018-11-27)
IESG IESG state RFC 8592 (Informational)
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
Independent Submission                                         R. Browne
Request for Comments: 8592                                   A. Chilikin
Category: Informational                                            Intel
ISSN: 2070-1721                                               T. Mizrahi
                                        Huawei Network.IO Innovation Lab
                                                                May 2019

                Key Performance Indicator (KPI) Stamping
                  for the Network Service Header (NSH)

Abstract

   This document describes methods of carrying Key Performance
   Indicators (KPIs) using the Network Service Header (NSH).  These
   methods may be used, for example, to monitor latency and QoS marking
   to identify problems on some links or service functions.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any other
   RFC stream.  The RFC Editor has chosen to publish this document at
   its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not candidates for any level of Internet Standard;
   see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8592.

Copyright Notice

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

Browne, et al.                Informational                     [Page 1]
RFC 8592                    KPI Timestamping                    May 2019

Table of Contents

   1. Introduction ....................................................2
   2. Terminology .....................................................3
      2.1. Requirements Language ......................................3
      2.2. Definition of Terms ........................................3
           2.2.1. Terms Defined in This Document ......................4
      2.3. Abbreviations ..............................................5
   3. NSH KPI Stamping: An Overview ...................................6
      3.1. Prerequisites ..............................................7
      3.2. Operation ..................................................9
           3.2.1. Flow Selection ......................................9
           3.2.2. SCP Interface ......................................10
      3.3. Performance Considerations ................................11
   4. NSH KPI-Stamping Encapsulation .................................12
      4.1. KPI-Stamping Extended Encapsulation .......................13
           4.1.1. NSH Timestamping Encapsulation (Extended Mode) .....15
           4.1.2. NSH QoS-Stamping Encapsulation (Extended Mode) .....17
      4.2. KPI-Stamping Encapsulation (Detection Mode) ...............20
   5. Hybrid Models ..................................................22
      5.1. Targeted VNF Stamping .....................................23
   6. Fragmentation Considerations ...................................23
   7. Security Considerations ........................................24
   8. IANA Considerations ............................................24
   9. References .....................................................25
      9.1. Normative References ......................................25
      9.2. Informative References ....................................25
   Acknowledgments ...................................................27
   Contributors ......................................................27
   Authors' Addresses ................................................27

1.  Introduction

   The Network Service Header (NSH), as defined by [RFC8300], specifies
   a method for steering traffic among an ordered set of Service
   Functions (SFs) using an extensible service header.  This allows for
   flexibility and programmability in the forwarding plane to invoke the
   appropriate SFs for specific flows.

   The NSH promises a compelling vista of operational flexibility.
   However, many service providers are concerned about service and
   configuration visibility.  This concern increases when considering
   that many service providers wish to run their networks seamlessly in
   "hybrid mode", whereby they wish to mix physical and virtual SFs and
   run services seamlessly between the two domains.

Browne, et al.                Informational                     [Page 2]
Show full document text