Network Telemetry Framework
draft-song-opsawg-ntf-00

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

• Versions
• 00

OPSAWG                                                      H. Song, Ed.
Internet-Draft                                                   T. Zhou
Intended status: Informational                                    ZB. Li
Expires: February 9, 2019                                         Huawei
                                                             G. Fioccola
                                                          Telecom Italia
                                                                  ZQ. Li
                                                            China Mobile
                                                       P. Martinez-Julia
                                                                    NICT
                                                            L. Ciavaglia
                                                                   Nokia
                                                                 A. Wang
                                                           China Telecom
                                                          August 8, 2018

                      Network Telemetry Framework
                        draft-song-opsawg-ntf-00

Abstract

   This document suggests the necessity of an architectural framework
   for network telemetry in order to meet the current and future network
   operation requirements.  The defining characteristics of network
   telemetry shows a clear distinction from the conventional network OAM
   concept; hence the network telemetry demands new techniques and
   protocols.  This document clarifies the terminologies and classifies
   the categories and components of a network telemetry framework.  The
   requirements, challenges, existing solutions, and future directions
   are discussed for each category.  The network telemetry framework and
   the taxonomy help to set a common ground for the collection of
   related works and put future technique and standard developments into
   perspective.

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.

Song, et al.            Expires February 9, 2019                [Page 1]
Internet-Draft         Network Telemetry Framework           August 2018

   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 February 9, 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Challenges  . . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.4.  Network Telemetry . . . . . . . . . . . . . . . . . . . .   6
   2.  The Necessity of a Network Telemetry Framework  . . . . . . .   8
   3.  Network Telemetry Framework . . . . . . . . . . . . . . . . .   9
     3.1.  Existing Works Mapped in the Framework  . . . . . . . . .  11
     3.2.  Management Plane Telemetry  . . . . . . . . . . . . . . .  12
       3.2.1.  Requirements and Challenges . . . . . . . . . . . . .  12
       3.2.2.  Push Extensions for NETCONF . . . . . . . . . . . . .  13
       3.2.3.  gRPC Network Management Interface . . . . . . . . . .  13
     3.3.  Control Plane Telemetry . . . . . . . . . . . . . . . . .  14
       3.3.1.  Requirements and Challenges . . . . . . . . . . . . .  14
       3.3.2.  BGP Monitoring Protocol . . . . . . . . . . . . . . .  14