draft-morton-ippm-twamp-rate-01.txt   draft-morton-ippm-twamp-rate-02.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft L. Ciavattone Internet-Draft L. Ciavattone
Updates: 5357 (if approved) AT&T Labs Updates: 5357 (if approved) AT&T Labs
Intended status: Standards Track March 4, 2012 Intended status: Standards Track September 3, 2012
Expires: September 5, 2012 Expires: March 7, 2013
TWAMP Burst Rate Measurement Features TWAMP Burst Rate Measurement Features
draft-morton-ippm-twamp-rate-01 draft-morton-ippm-twamp-rate-02
Abstract Abstract
This memo describes two rate-measurement features for the core This memo describes two rate-measurement features for the core
specification of TWAMP - the Two-Way Active Measurement Protocol: an specification of TWAMP - the Two-Way Active Measurement Protocol: an
optional capability where the reflector host responds with a optional capability where the reflector host responds with a
controlled burst of test-session packets (instead of a single controlled burst of test-session packets (instead of a single
packet), and an optional test mode that requires the responder to packet), and an optional test mode that requires the responder to
measure a burst of test packets and communicate the results in measure a burst of test packets and communicate the results in
truncated packet(s). Both features add the ability to control packet truncated packet(s). Both features add the ability to control packet
size in the tested direction, enabling asymmetrical packet size size in the tested direction, enabling asymmetrical packet size
testing. testing. There is an open question on using TCP transport instead of
UDP.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 45 skipping to change at page 1, line 46
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 September 5, 2012. This Internet-Draft will expire on March 7, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
skipping to change at page 2, line 18 skipping to change at page 2, line 19
(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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Question on Transport Protocol Selection . . . . . . . . . 4
3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 4 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Connection Setup with New Features . . . . . . . . . . . . 5 3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 6
3.2. Burst Generation: Request-TW-Session Packet Format . . . . 5 3.1. Connection Setup with New Features . . . . . . . . . . . . 6
3.3. Burst Measurement: Request-TW-Session Packet Format . . . 7 3.2. Burst Generation: Request-TW-Session Packet Format . . . . 6
3.4. Burst Gen and Meas: Accept Session Packet Format . . . . . 8 3.3. Burst Measurement: Request-TW-Session Packet Format . . . 8
3.5. Burst Gen and Meas: Stopping Test Sessions . . . . . . . . 8 3.4. Burst Gen and Meas: Accept Session Packet Format . . . . . 9
3.6. Additional considerations . . . . . . . . . . . . . . . . 8 3.5. Burst Gen and Meas: Stopping Test Sessions . . . . . . . . 9
4. Burst Generation in TWAMP Test . . . . . . . . . . . . . . . . 9 3.6. Additional considerations . . . . . . . . . . . . . . . . 9
4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 9 4. Burst Generation in TWAMP Test . . . . . . . . . . . . . . . . 10
4.1.1. Packet Timings . . . . . . . . . . . . . . . . . . . . 9 4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 10
4.1.2. Packet Formats and Contents . . . . . . . . . . . . . 9 4.1.1. Packet Timings . . . . . . . . . . . . . . . . . . . . 10
4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 10 4.1.2. Packet Formats and Contents . . . . . . . . . . . . . 10
4.2.1. Session-Reflector Burst Packet Format and Contents . . 10 4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 11
5. Burst Measurement in TWAMP Test . . . . . . . . . . . . . . . 12 4.2.1. Session-Reflector Burst Packet Format and Contents . . 11
5.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 12 5. Burst Measurement in TWAMP Test . . . . . . . . . . . . . . . 13
5.1.1. Packet Timings . . . . . . . . . . . . . . . . . . . . 12 5.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 13
5.1.2. Packet Formats and Contents . . . . . . . . . . . . . 12 5.1.1. Packet Timings . . . . . . . . . . . . . . . . . . . . 13
5.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 13 5.1.2. Packet Formats and Contents . . . . . . . . . . . . . 13
5.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 14
5.2.1. Session-Reflector Burst Measurement Response 5.2.1. Session-Reflector Burst Measurement Response
Packet Format and Contents . . . . . . . . . . . . . . 14 Packet Format and Contents . . . . . . . . . . . . . . 15
6. Special Case of One-packet Bursts . . . . . . . . . . . . . . 16 6. Special Case of One-packet Bursts . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
8.1. Registry Specification . . . . . . . . . . . . . . . . . . 16 8.1. Registry Specification . . . . . . . . . . . . . . . . . . 17
8.2. Registry Contents . . . . . . . . . . . . . . . . . . . . 17 8.2. Registry Contents . . . . . . . . . . . . . . . . . . . . 18
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . . 18 10.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
TWAMP - the Two-Way Active Measurement Protocol [RFC5357] is an TWAMP - the Two-Way Active Measurement Protocol [RFC5357] is an
extension of the One-way Active Measurement Protocol, OWAMP extension of the One-way Active Measurement Protocol, OWAMP
[RFC4656]. The TWAMP specification gathered wide review as it was [RFC4656]. The TWAMP specification gathered wide review as it was
deployed, resulting in recommendations for new features. deployed, resulting in recommendations for new features.
This memo describes two closely-related features for TWAMP. When This memo describes two closely-related features for TWAMP. When
measuring packet delivery rate to end-systems, unique control and measuring packet delivery rate to end-systems, unique control and
skipping to change at page 3, line 47 skipping to change at page 4, line 47
This memo is an update to the TWAMP core protocol specified in This memo is an update to the TWAMP core protocol specified in
[RFC5357]. Measurement systems are not required to implement the [RFC5357]. Measurement systems are not required to implement the
features described in this memo to claim compliance with [RFC5357]. features described in this memo to claim compliance with [RFC5357].
Throughout this memo, the bits marked MBZ (Must Be Zero) MUST be set Throughout this memo, the bits marked MBZ (Must Be Zero) MUST be set
to zero by senders and MUST be ignored by receivers. Also, the HMAC to zero by senders and MUST be ignored by receivers. Also, the HMAC
(Hashed Message Authentication Code) MUST be calculated as defined in (Hashed Message Authentication Code) MUST be calculated as defined in
Section 3.2 of [RFC4656]. Section 3.2 of [RFC4656].
1.1. Question on Transport Protocol Selection
An open question in the IPPM problem statement draft is whether
testing with TCP transport protocol is a needed capability. The
current TWAMP test protocol capability is limited to UDP transport.
What are the implications of specifying a TWAMP-Test capability with
TCP transport headers, with or without TCP flow control?
This is clearly a topic where coordination is required between the
testing sender and receiver devices. It could be specified as an
independent TWAMP feature, although it is clearly related to the
features described here.
2. Purpose and Scope 2. Purpose and Scope
The purpose of this memo is to define two OPTIONAL closely-related The purpose of this memo is to define two OPTIONAL closely-related
features for TWAMP [RFC5357]. The features enhance the TWAMP features for TWAMP [RFC5357]. The features enhance the TWAMP
responder's capabilities to perform a simple operations on test responder's capabilities to perform a simple operations on test
packets, and the capability to demand asymmetrical size TWAMP-Test packets, and the capability to demand asymmetrical size TWAMP-Test
packets. packets.
The scope of the memo is limited to specifications of the following The scope of the memo is limited to specifications of the following
features: features:
 End of changes. 8 change blocks. 
37 lines changed or deleted 53 lines changed or added

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