draft-ietf-ippm-type-p-monitor-01.txt   draft-ietf-ippm-type-p-monitor-02.txt 
Network Working Group J. Hedin Network Working Group J. Hedin
Internet-Draft G. Mirsky Internet-Draft G. Mirsky
Intended status: Standards Track S. Baillargeon Intended status: Standards Track S. Baillargeon
Expires: June 21, 2015 Ericsson Expires: November 21, 2015 Ericsson
December 18, 2014 May 20, 2015
Differentiated Service Code Point and Explicit Congestion Notification Differentiated Service Code Point and Explicit Congestion Notification
Monitoring in Two-Way Active Measurement Protocol (TWAMP) Monitoring in Two-Way Active Measurement Protocol (TWAMP)
draft-ietf-ippm-type-p-monitor-01 draft-ietf-ippm-type-p-monitor-02
Abstract Abstract
This document describes an OPTIONAL extension for Two-Way Active This document describes an OPTIONAL extension for Two-Way Active
Measurement Protocol (TWAMP) allowing the monitoring of the Measurement Protocol (TWAMP) allowing the monitoring of the
Differentiated Service Code Point and Explicit Congestion Differentiated Service Code Point and Explicit Congestion
Notification fields with the TWAMP-Test protocol. Notification fields with the TWAMP-Test protocol.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 21, 2015. This Internet-Draft will expire on November 22, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 35 skipping to change at page 3, line 35
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
2. TWAMP Extensions 2. TWAMP Extensions
TWAMP connection establishment follows the procedure defined in TWAMP connection establishment follows the procedure defined in
Section 3.1 of [RFC4656] and Section 3.1 of [RFC5357] where the Modes Section 3.1 of [RFC4656] and Section 3.1 of [RFC5357] where the Modes
field is used to identify and select specific communication field is used to identify and select specific communication
capabilities. At the same time the Modes field been recognized and capabilities. At the same time the Modes field been recognized and
used as an extension mechanism [RFC6038]. The new feature requires a used as an extension mechanism [RFC6038]. The new feature requires a
new bit position to identify the ability of a Session-Reflector to new flag to identify the ability of a Session-Reflector to return
return value of received DSCP and ECN values back to a Session- value of received DSCP and ECN values back to a Session-Sender, and
Sender, and to support the new Session-Reflector packet format in the to support the new Session-Reflector packet format in the TWAMP-Test
TWAMP-Test protocol. See the Section 3 for details on the assigned protocol. See the Section 3 for details on the assigned bit
value and bit position. position.
2.1. Setting Up Connection to Monitor DSCP and ECN 2.1. Setting Up Connection to Monitor DSCP and ECN
The Server sets DSCP and ECN Monitoring flag in Modes field of the The Server sets DSCP and ECN Monitoring flag in Modes field of the
Server Greeting message to indicate its capabilities and willingness Server Greeting message to indicate its capabilities and willingness
to monitor them. If the Control-Client agrees to monitor DSCP and to monitor them. If the Control-Client agrees to monitor DSCP and
ECN on some or all test sessions invoked with this control ECN on some or all test sessions invoked with this control
connection, it MUST set the DSCP and ECN Monitoring flag in the Modes connection, it MUST set the DSCP and ECN Monitoring flag in the Modes
field in the Setup Response message. field in the Setup Response message.
skipping to change at page 8, line 25 skipping to change at page 8, line 25
packets. Then Session-Sender may be informed to use Sender DSCP and packets. Then Session-Sender may be informed to use Sender DSCP and
ECN field in reflected TWAMP test packet. ECN field in reflected TWAMP test packet.
3. IANA Considerations 3. IANA Considerations
The TWAMP-Modes registry defined in [RFC5618]. The TWAMP-Modes registry defined in [RFC5618].
IANA is requested to reserve a new DSCP and ECN Monitoring Capability IANA is requested to reserve a new DSCP and ECN Monitoring Capability
as follows: as follows:
+------------+--------------------+---------------------+-----------+ +-----+------------------------+---------------------+--------------+
| Value | Description | Semantics | Reference | | Bit | Description | Semantics | Reference |
+------------+--------------------+---------------------+-----------+ | | | Definition | |
| X | DSCP and ECN | bit position Y | This | +-----+------------------------+---------------------+--------------+
| (proposed | Monitoring | (proposed 7) | document | | TBA | DSCP and ECN | Section 2 | This |
| 128) | Capability | | | | | Monitoring Capability | | document |
+------------+--------------------+---------------------+-----------+ +-----+------------------------+---------------------+--------------+
Table 1: New Type-P Descriptor Monitoring Capability Table 1: New Type-P Descriptor Monitoring Capability
4. Security Considerations 4. Security Considerations
Monitoring of DSCP and ECN does not appear to introduce any Monitoring of DSCP and ECN does not appear to introduce any
additional security threat to hosts that communicate with TWAMP as additional security threat to hosts that communicate with TWAMP as
defined in [RFC5357], and existing extensions [RFC6038]. The defined in [RFC5357], and existing extensions [RFC6038]. The
security considerations that apply to any active measurement of live security considerations that apply to any active measurement of live
networks are relevant here as well. See the Security Considerations networks are relevant here as well. See the Security Considerations
 End of changes. 6 change blocks. 
17 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/