Simple Two-way Active Measurement Protocol
draft-mirsky-ippm-stamp-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-10-13
Replaced by draft-ietf-ippm-stamp
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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                                          G. Mirsky
Internet-Draft                                                 ZTE Corp.
Intended status: Standards Track                                  G. Jun
Expires: April 15, 2018                                  ZTE Corporation
                                                        October 12, 2017

               Simple Two-way Active Measurement Protocol
                       draft-mirsky-ippm-stamp-00

Abstract

   This document describes a Two-way Active Measurement Protocol which
   enables measurement of both one-way and round-trip performance
   metrics like delay, delay variation and packet loss.

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 April 15, 2018.

Copyright Notice

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

Mirsky & Jun             Expires April 15, 2018                 [Page 1]
Internet-Draft                    STAMP                     October 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   2
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
     2.2.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   3.  Softwarization of Performance Measurement . . . . . . . . . .   2
   4.  Theory of Operation . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Sender Behavior and Packet Format . . . . . . . . . . . .   3
       4.1.1.  Sender Packet Format in Unauthenticated Mode  . . . .   3
       4.1.2.  Sender Packet Format in Authenticated and Encrypted
               Modes . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Reflector Behavior and Packet Format  . . . . . . . . . .   6
       4.2.1.  Reflector Packet Format in Unauthenticated Mode . . .   6
       4.2.2.  Reflector Packet Format in Authenticated and
               Encrypted Modes . . . . . . . . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

2.  Conventions used in this document

2.1.  Terminology

   STAMP - Simple Two-way Active Measurement Protocol

   NTP - Network Time Protocol

   PTP - Precision Time Protocol

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

3.  Softwarization of Performance Measurement

   Instance of a Simple Two-way Active Measurement Protocol (STAMP)
   session between a Sender and a Reflector controlled by communication
   between a Configuration Client as a manager and Configuration Servers
   as agents of the configuration session that configures STAMP

Mirsky & Jun             Expires April 15, 2018                 [Page 2]
Internet-Draft                    STAMP                     October 2017

   measurement between Sender and Reflector.  The Configuration Client
   also issues queries to obtain operational state information and/or
   measurement results.

         o----------------------------------------------------------o
         |                        Config client                     |
         o----------------------------------------------------------o
Show full document text