Passive Performance Metrics Sub-Registry
draft-akhter-ippm-registry-passive-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-02-14
Replaced by draft-ietf-ippm-registry-passive
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)
IPPM Working Group                                             A. Akhter
Internet-Draft                                                 B. Claise
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: August 18, 2014                               February 14, 2014

                Passive Performance Metrics Sub-Registry
               draft-akhter-ippm-registry-passive-00.txt

Abstract

   This memo defines the Passive Performance Metrics sub-registry of the
   Performance Metric Registry.  This sub-registry will contain Passive
   Performance Metrics, especially those defined in RFCs prepared in the
   IP Performance Metrics (IPPM) Working Group of the IETF, and possibly
   applicable to other IETF metrics.

   IPPM Passive metric registration is meant to allow wider adoption of
   common metrics in an inter-operable way.  There are challenges with
   metric interoperability and adoption (to name a few) due to flexible
   input parameters, confusion between many similar metrics, and varying
   output formats.

   This memo proposes a way to organize registry entries into columns
   that are well-defined, permitting consistent development of entries
   over time (a column may marked NA if it is not applicable for that
   metric).  The design is intended to foster development of registry
   entries based on existing reference RFCs, whilst each column serves
   as a check-list item to avoid omissions during the registration
   process.  Every entry in the registry, before IANA action, requires
   Expert review as defined by concurrent IETF work in progress
   "Registry for Performance Metrics" (draft-manyfolks-ippm-metric-
   registry).

   The document contains example entries for the Passive Performance
   Metrics sub-registry: a registry entry for a passive metric based on
   octetTotalCount as defined in RFC5102 and a protocol specific passive
   metric based on RTP packets lost as defined in RFC3550.  The examples
   are for Informational purposes and do not create any entry in the
   IANA registry.

Requirements Language

   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 RFC 2119 [RFC2119].

Akhter & Claise          Expires August 18, 2014                [Page 1]
Internet-Draft            Passive Sub-Registry             February 2014

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 http://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 August 18, 2014.

Copyright Notice

   Copyright (c) 2014 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Background and Motivation:  . . . . . . . . . . . . . . . . .   4
   3.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Passive Registry Categories and Columns . . . . . . . . . . .   5
     4.1.  Common Registry Indexes and Information . . . . . . . . .   6
       4.1.1.  Identifier  . . . . . . . . . . . . . . . . . . . . .   6
       4.1.2.  Name  . . . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.3.  Status  . . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.4.  Requester . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.5.  Revision  . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.6.  Revision Date . . . . . . . . . . . . . . . . . . . .   6
       4.1.7.  Description . . . . . . . . . . . . . . . . . . . . .   6
       4.1.8.  Reference Specification(s)  . . . . . . . . . . . . .   6
       4.1.9.  Metric Definition . . . . . . . . . . . . . . . . . .   7

Akhter & Claise          Expires August 18, 2014                [Page 2]
Internet-Draft            Passive Sub-Registry             February 2014
Show full document text