QoS Telemetry Requirements
draft-asechoud-rtgwg-qos-telemetry-req-00

Document Type Active Internet-Draft (individual)
Last updated 2018-05-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Network Working Group                                       A. Choudhary
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                            May 12, 2018
Expires: November 13, 2018

                       QoS Telemetry Requirements
               draft-asechoud-rtgwg-qos-telemetry-req-00

Abstract

   This document discusses QoS requirements for data model based network
   telemetry.  QoS configuration and operational models have been
   defined as part of [I-D.asechoud-rtgwg-qos-model] and
   [I-D.asechoud-rtgwg-qos-oper-model] respectively.  This document
   describes the requirement to extend the models to support QoS
   Telemetry.

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 November 13, 2018.

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

Choudhary               Expires November 13, 2018               [Page 1]

Internet-Draft         QoS Telemetry Requirements               May 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  Granularity and Completeness  . . . . . . . . . . . . . .   2
     3.2.  Scale . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.3.  Cadence . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.4.  Time-stamping . . . . . . . . . . . . . . . . . . . . . .   3
     3.5.  Grouping  . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.6.  Filtering . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.7.  Aggregation . . . . . . . . . . . . . . . . . . . . . . .   3
     3.8.  Threshold . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Motivation

   Network visibility is an important aspect of Network availability.
   QoS counters provide good insight into network device performance,
   congestion and security.  Continuous monitoring of each QoS resource
   may not be always desired.  Mechanism to monitor data set of QoS
   resources is needed.  The motivation of this document is to come up
   with the set of requirements of such a mechanism.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Requirements

3.1.  Granularity and Completeness

   Statistics passed for a QoS resource should be complete at the same
   time granular to avoid sending undesired information.  A particular
   counter in isolation may not provide sufficient information about a
   QoS resource.  E.g tail-drop counter of a queue is not sufficient to
   define state of a Queue unless some other counters like maximum queue
   size and average queue size is known.  Hence, it is important to get
   complete context of a resource based on device capability.

Choudhary               Expires November 13, 2018               [Page 2]

Internet-Draft         QoS Telemetry Requirements               May 2018

3.2.  Scale

   It is important to have visibility into vast number of QoS resources
   in a network device on a regular basis.  Some of the devices, e.g.,
   may support millions of queues in a single device.  To be able to
   scale, it is desired to have data sets of important resources and
Show full document text