Type-P Descriptor Monitoring in Two-Way Active Measurement Protocol (TWAMP)
draft-hedin-ippm-type-p-monitor-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-06-25
Replaced by RFC 7750, RFC 7750
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) 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                                           J. Hedin
Internet-Draft                                                 G. Mirsky
Intended status: Standards Track                                Ericsson
Expires: December 27, 2013                                 June 25, 2013

  Type-P Descriptor Monitoring in Two-Way Active Measurement Protocol
                                (TWAMP)
                   draft-hedin-ippm-type-p-monitor-01

Abstract

   This document specifies how optional monitoring of Type-P Descriptor
   can be negotiated and performed by TWAMP [RFC5357] Control and Test
   protocols.

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 December 27, 2013.

Copyright Notice

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

Hedin & Mirsky          Expires December 27, 2013               [Page 1]

Internet-Draft    Type-P Descriptor Monitoring in TWAMP        June 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Conventions used in this document . . . . . . . . . . . . . 3
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . 3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . . . 3
   2.  TWAMP Extensions  . . . . . . . . . . . . . . . . . . . . . . . 3
     2.1.  Setting Up Connection to Monitor Type-P Descriptor  . . . . 4
     2.2.  TWAMP-Test Extension  . . . . . . . . . . . . . . . . . . . 4
       2.2.1.  Session-Reflector Packet Format for Type-P
               Descriptor Monitoring . . . . . . . . . . . . . . . . . 4
       2.2.2.  Type-P Descriptor Monitoring with RFC 6038
               extensions  . . . . . . . . . . . . . . . . . . . . . . 6
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 8
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 8
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Hedin & Mirsky          Expires December 27, 2013               [Page 2]

Internet-Draft    Type-P Descriptor Monitoring in TWAMP        June 2013

1.  Introduction

   Re-marking of Type-P Descriptor, i.e. change in value, might be
   demonstration of intentional or errorneous behavior.  Monitoring of
   Type-P Descriptor can provide valuable information for network
   operators.  One-Way Active Measurement Protocol [RFC4656] and Two-Way
   Active Measurement Protocol [RFC5357] define negotiation of TypeP
   Descriptor value that must be used by Session-Sender and Session-
   Reflector.  But there's not means for Session-Sender to know whether
   Type-P Descriptor was received by Session-Reflector unchanged.
   Opional monitoring of Type-P Descriptor between Session-Sender and
   Session-Reflector requires extensions to TWAMP [RFC5357] that are
   described in this document.

1.1.  Conventions used in this document

1.1.1.  Terminology

   DSCP: Differentiated Service Codepoint

   IPPM: IP Performance Measurement

   TWAMP: Two-Way Active Measuremnt Protocol

   OWAMP: One-Way Active Measurement Protocol

1.1.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
Show full document text