In-situ Flow Information Telemetry Framework
draft-song-opsawg-ifit-framework-03

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

• Versions
• 00
• 01
• 02
• 03

OPSAWG                                                      H. Song, Ed.
Internet-Draft                                                 Futurewei
Intended status: Informational                                     Z. Li
Expires: January 9, 2020                                         T. Zhou
                                                                  Huawei
                                                                  F. Qin
                                                            China Mobile
                                                                 J. Shin
                                                              SK Telecom
                                                                  J. Jin
                                                                   LG U+
                                                            July 8, 2019

              In-situ Flow Information Telemetry Framework
                  draft-song-opsawg-ifit-framework-03

Abstract

   In-situ Flow Information Telemetry (iFIT) is a framework for applying
   on-path data plane telemetry techniques such as In-situ OAM (iOAM)
   and Postcard-Based Telemetry (PBT).  It enumerates several key
   components and describes how these components are assembled to
   achieve a complete working solution for on-path user traffic
   telemetry in carrier networks.

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.

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."

Song, et al.             Expires January 9, 2020                [Page 1]
Internet-Draft               iFIT Framework                    July 2019

   This Internet-Draft will expire on January 9, 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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Smart Flow and Data Selection . . . . . . . . . . . . . . . .   5
   3.  Export Data Reduction . . . . . . . . . . . . . . . . . . . .   5
   4.  Dynamic Network Probe . . . . . . . . . . . . . . . . . . . .   6
   5.  Encapsulation and Tunnel Modes  . . . . . . . . . . . . . . .   6
   6.  On-demand Technique Selection and Integration . . . . . . . .   7
   7.  Summary and Future Work . . . . . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     12.2.  Informative References . . . . . . . . . . . . . . . . .   8
     12.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Application-aware network operation is important for user SLA
   compliance, service path enforcement, fault diagnosis, and network
   resource optimization.  In-situ OAM (IOAM)
   [I-D.brockners-inband-oam-data] and PBT
   [I-D.song-ippm-postcard-based-telemetry] provide the direct on-path
   experience of user traffic.  These techniques are invaluable for
   application-aware network operations in not only data center and
   enterprise networks but also carrier networks.

Song, et al.             Expires January 9, 2020                [Page 2]