Postcard-based On-Path Flow Data Telemetry
draft-song-ippm-postcard-based-telemetry-05

Document Type Active Internet-Draft (individual)
Last updated 2019-09-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
IPPM                                                        H. Song, Ed.
Internet-Draft                                                 Futurewei
Intended status: Standards Track                                 T. Zhou
Expires: March 12, 2020                                            Z. Li
                                                                  Huawei
                                                                 J. Shin
                                                              SK Telecom
                                                                  K. Lee
                                                                   LG U+
                                                       September 9, 2019

               Postcard-based On-Path Flow Data Telemetry
              draft-song-ippm-postcard-based-telemetry-05

Abstract

   The Postcard-Based Telemetry (PBT) allows network OAM applications to
   directly collect and export telemetry data about any user packet at
   each node on the forwarding path.  PBT has two variations.  One
   requires inserting an instruction header to user packets to guide the
   data collection.  This variation has been recast into an independent
   IOAM option mode, Direct Export, and described in a standalone
   document.  This document describes the second variation, the mark
   triggered PBT or PBT-M.  PBT-M only marks the user packets or
   configure the flow filter to invoke the data collection and postcard
   export.  It complements IOAM by addressing several specific
   implementation and deployment challenges.

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 March 12, 2020.

Song, et al.             Expires March 12, 2020                 [Page 1]
Internet-Draft          Postcard-Based Telemetry          September 2019

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.  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.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  PBT-M: Postcard-based Telemetry with Packet Marking . . . . .   5
     2.1.  New Requirements  . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Solution Description  . . . . . . . . . . . . . . . . . .   6
     2.3.  New Challenges  . . . . . . . . . . . . . . . . . . . . .   7
     2.4.  Considerations on PBT-M Design  . . . . . . . . . . . . .   8
       2.4.1.  Packet Marking  . . . . . . . . . . . . . . . . . . .   8
       2.4.2.  Flow Path Discovery . . . . . . . . . . . . . . . . .   8
       2.4.3.  Packet Identity for Export Data Correlation . . . . .   9
     2.5.  Avoid Packet Marking through Node Configuration . . . . .   9
   3.  Postcard Format . . . . . . . . . . . . . . . . . . . . . . .  10
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Motivation

   In order to gain detailed data plane visibility to support effective
   network OAM, it is important to be able to examine the trace of user
   packets along their forwarding paths.  Such on-path flow data reflect
   the state and status of each user packet's real-time experience and
   provide valuable information for network monitoring, measurement, and
   diagnosis.

   The telemetry data include but not limited to the detailed forwarding
   path, the timestamp/latency at each network node, and, in case of
   packet drop, the drop location and reason.  The emerging programmable
Show full document text