mPlane Protocol Specification
draft-trammell-mplane-protocol-02

Document Type Active Internet-Draft (individual)
Last updated 2016-10-27
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                   B. Trammell, Ed.
Internet-Draft                                        M. Kuehlewind, Ed.
Intended status: Informational                                ETH Zurich
Expires: April 30, 2017                                 October 27, 2016

                     mPlane Protocol Specification
                   draft-trammell-mplane-protocol-02

Abstract

   This document defines the mPlane protocol for coordination of
   heterogeneous network measurement Components: probes and repositories
   that measure, analyze, and store network measurements, data derived
   from measurements, and other ancillary data about elements of the
   network.  The mPlane architecture is defined in terms of
   relationships between Components and Clients which communicate using
   the mPlane protocol defined in this document.

   This revision of the document describes Version 2 of the mPlane
   protocol.

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 April 30, 2017.

Copyright Notice

   Copyright (c) 2016 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

Trammell & Kuehlewind    Expires April 30, 2017                 [Page 1]
Internet-Draft               mPlane Protocol                October 2016

   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
     1.1.  Changes from Revision -00 (Protocol version 1)  . . . . .   4
     1.2.  Changes from Revision -01 . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview of the mPlane Architecture . . . . . . . . . . . . .   5
     3.1.  Key Architectural Principles and Features . . . . . . . .   6
       3.1.1.  Flexibility and Extensibility . . . . . . . . . . . .   6
       3.1.2.  Schema-centric Measurement Definition . . . . . . . .   7
       3.1.3.  Iterative Measurement Support . . . . . . . . . . . .   7
       3.1.4.  Weak Imperativeness . . . . . . . . . . . . . . . . .   7
     3.2.  Entities and Relationships  . . . . . . . . . . . . . . .   8
       3.2.1.  Components and Clients  . . . . . . . . . . . . . . .   9
       3.2.2.  Probes and Repositories . . . . . . . . . . . . . . .   9
     3.3.  Message Types and Message Exchange Sequences  . . . . . .   9
     3.4.  Integrating Measurement Tools into mPlane . . . . . . . .  11
     3.5.  From Architecture to Protocol Specification . . . . . . .  11
   4.  Protocol Information Model  . . . . . . . . . . . . . . . . .  11
     4.1.  Element Registry  . . . . . . . . . . . . . . . . . . . .  12
       4.1.1.  Structured Element Names  . . . . . . . . . . . . . .  13
       4.1.2.  Primitive Types . . . . . . . . . . . . . . . . . . .  14
       4.1.3.  Augmented Registry Information  . . . . . . . . . . .  15
     4.2.  Message Types . . . . . . . . . . . . . . . . . . . . . .  15
       4.2.1.  Capability and Withdrawal . . . . . . . . . . . . . .  16
       4.2.2.  Specification and Interrupt . . . . . . . . . . . . .  16
       4.2.3.  Result  . . . . . . . . . . . . . . . . . . . . . . .  16
       4.2.4.  Receipt and Redemption  . . . . . . . . . . . . . . .  16
       4.2.5.  Exception . . . . . . . . . . . . . . . . . . . . . .  17
       4.2.6.  Envelope  . . . . . . . . . . . . . . . . . . . . . .  17
     4.3.  Message Sections  . . . . . . . . . . . . . . . . . . . .  18
       4.3.1.  Message Type and Verb . . . . . . . . . . . . . . . .  19
       4.3.2.  Version . . . . . . . . . . . . . . . . . . . . . . .  20
       4.3.3.  Registry  . . . . . . . . . . . . . . . . . . . . . .  20
Show full document text