In-situ Flow Information Telemetry
draft-song-opsawg-ifit-framework-07

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
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)
OPSAWG                                                      H. Song, Ed.
Internet-Draft                                                 Futurewei
Intended status: Informational                                    F. Qin
Expires: May 7, 2020                                        China Mobile
                                                                 H. Chen
                                                           China Telecom
                                                                  J. Jin
                                                                   LG U+
                                                                 J. Shin
                                                              SK Telecom
                                                        November 4, 2019

                   In-situ Flow Information Telemetry
                  draft-song-opsawg-ifit-framework-07

Abstract

   For efficient network operation, most network operators rely on
   traditional Operation, Administration and Maintenance (OAM) methods,
   which include proactive and reactive techniques, running in active
   and passive modes.  As networks increase in scale, they become more
   susceptible to measurement accuracy and misconfiguration errors.

   With the advent of programmable data-plane, emerging on-path
   telemetry techniques provide unprecedented flow insight and fast
   notification of network issues (e.g., jitter, increased latency,
   packet loss, significant bit error variations, and unequal load-
   balancing).

   This document outlines an In-situ Flow Information Telemetry (iFIT)
   reference framework, which enumerates several high level components
   and describes how these components can be assembled to achieve a
   complete and closed-loop working solution for on-path telemetry.

   iFIT addresses several deployment challenges for on-path telemetry
   techniques, especially in carrier networks.  As an open framework, it
   does not detail the implementation of the components as well as the
   interface between the components.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119][RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Song, et al.               Expires May 7, 2020                  [Page 1]
Internet-Draft               iFIT Framework                November 2019

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 May 7, 2020.

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.  Requirements and Challenges . . . . . . . . . . . . . . . . .   3
   2.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  iFIT Framework Overview . . . . . . . . . . . . . . . . . . .   6
     3.1.  Passport vs. Postcard . . . . . . . . . . . . . . . . . .   7
   4.  Architectural Components of iFIT  . . . . . . . . . . . . . .   8
     4.1.  Smart Flow and Data Selection . . . . . . . . . . . . . .   8
       4.1.1.  Example: Sketch-guided Elephant Flow Selection  . . .   9
       4.1.2.  Example: Adaptive Packet Sampling . . . . . . . . . .   9
     4.2.  Smart Data Export . . . . . . . . . . . . . . . . . . . .   9
       4.2.1.  Example: Event-based Anomaly Monitor  . . . . . . . .  10
     4.3.  Dynamic Network Probe . . . . . . . . . . . . . . . . . .  10
       4.3.1.  Examples  . . . . . . . . . . . . . . . . . . . . . .  11
     4.4.  Encapsulation and Tunneling . . . . . . . . . . . . . . .  11
     4.5.  On-demand Technique Selection and Integration . . . . . .  12
Show full document text