draft-ietf-ippm-twamp-session-cntrl-03.txt   draft-ietf-ippm-twamp-session-cntrl-04.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft AT&T Labs Internet-Draft AT&T Labs
Intended status: Standards Track M. Chiba Updates: 5357 (if approved) M. Chiba
Expires: August 21, 2010 Cisco Systems Intended status: Standards Track Cisco Systems
February 17, 2010 Expires: September 1, 2010 February 28, 2010
Individual Session Control Feature for TWAMP Individual Session Control Feature for TWAMP
draft-ietf-ippm-twamp-session-cntrl-03 draft-ietf-ippm-twamp-session-cntrl-04
Abstract Abstract
The IETF has completed its work on the core specification of TWAMP - The IETF has completed its work on the core specification of TWAMP -
the Two-Way Active Measurement Protocol. This memo describes a new the Two-Way Active Measurement Protocol. This memo describes an
feature for TWAMP, that gives the controlling host the ability to OPTIONAL feature for TWAMP, that gives the controlling host the
start and stop one or more individual test sessions using Session ability to start and stop one or more individual test sessions using
Identifiers. The base capability of the TWAMP protocol requires all Session Identifiers. The base capability of the TWAMP protocol
test sessions previously requested and accepted to start and stop at requires all test sessions previously requested and accepted to start
the same time. and stop at the same time.
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 to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 21, 2010. This Internet-Draft will expire on September 1, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 3, line 7 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 4 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3
3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 5 3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 4
3.1. Connection Setup with Individual Session Control . . . . . 5 3.1. Connection Setup with Individual Session Control . . . . . 4
3.2. Start-N-Sessions Command with Individual Session 3.2. Start-N-Sessions Command with Individual Session
Control . . . . . . . . . . . . . . . . . . . . . . . . . 7 Control . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Start-N-Ack Command with Individual Session Control . . . 9 3.3. Start-N-Ack Command with Individual Session Control . . . 8
3.4. Stop-N-Sessions Command with Individual Session Control . 10 3.4. Stop-N-Sessions Command with Individual Session Control . 9
3.5. Stop-N-Ack Command with Individual Session Control . . . . 11 3.5. Stop-N-Ack Command with Individual Session Control . . . . 10
3.6. SERVWAIT Timeout Operation . . . . . . . . . . . . . . . . 13 3.6. SERVWAIT Timeout Operation . . . . . . . . . . . . . . . . 12
3.7. Additional considerations . . . . . . . . . . . . . . . . 14 3.7. Additional considerations . . . . . . . . . . . . . . . . 13
4. TWAMP Test with Individual Session Control . . . . . . . . . . 14 4. TWAMP Test with Individual Session Control . . . . . . . . . . 13
4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 14 4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 13
4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 14 4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 13
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6.1. Registry Specification . . . . . . . . . . . . . . . . . . 15 6.1. Registry Specification . . . . . . . . . . . . . . . . . . 14
6.2. Registry Management . . . . . . . . . . . . . . . . . . . 15 6.2. Registry Management . . . . . . . . . . . . . . . . . . . 14
6.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 16 6.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 15
6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 16 6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 15
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . . 17 8.2. Informative References . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
The IETF has completed its work on the core specification of TWAMP - The IETF has completed its work on the core specification of TWAMP -
the Two-Way Active Measurement Protocol [RFC5357]. TWAMP is an the Two-Way Active Measurement Protocol [RFC5357]. TWAMP 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 [RFC4656]. The TWAMP specification gathered wide review as it
approached completion, and the by-products were several approached completion, and the by-products were several
recommendations for new features in TWAMP. There are a growing recommendations for new features in TWAMP. There are a growing
number of TWAMP implementations at present, and wide-spread usage is number of TWAMP implementations at present, and wide-spread usage is
expected. There are even devices that are designed to test expected. There are even devices that are designed to test
implementations for protocol compliance. implementations for protocol compliance.
This memo describes a new feature for TWAMP. TWAMP (and OWAMP) start This memo describes an OPTIONAL feature for TWAMP. TWAMP (and OWAMP)
all previously requested and accepted test sessions at once. This start all previously requested and accepted test sessions at once.
feature allows the Control-Client to control individual test sessions This feature allows the Control-Client to control individual test
on the basis of their Session Identifier (SID). This feature permits sessions on the basis of their Session Identifier (SID). This
a short duration TWAMP test to start (and/or stop) during a longer feature permits a short duration TWAMP test to start (and/or stop)
test. This feature permits a specific diagnostic test to begin if during a longer test. This feature permits a specific diagnostic
intermediate results indicate that the test is warranted, for test to begin if intermediate results indicate that the test is
example. warranted, for example.
This feature requires a Mode bit position assignment and the This feature requires a Mode bit position assignment and the
assignment of two new TWAMP command numbers (for the augmented Start assignment of two new TWAMP command numbers (for the augmented Start
and Stop commands). This feature also specifies a new Stop-ACK and Stop commands). This feature also specifies a new Stop-ACK
Server response, to complete the symmetry of the session stopping Server response, to complete the symmetry of the session stopping
process in the same way as the Start-ACK response. process in the same way as the Start-ACK response.
Implementers of this feature may also wish to implement the "Reflect Implementers of this feature MAY also wish to implement the "Reflect
Octets" feature, described in [I-D.ietf-ippm-twamp-reflect-octets]. Octets" feature, described in [I-D.ietf-ippm-twamp-reflect-octets],
This feature allows a Control-Client to insert a locally-specified once it has been published as an RFC. This feature allows a Control-
request number into the Request-TW-Session command (in octets Client to insert a locally-specified request number into the Request-
originally designated MBZ=Must Be Zero), and a compliant Server will TW-Session command (in octets originally designated MBZ=Must Be
return the request number in its reply (Accept message). Zero), and a compliant Server will return the request number in its
reply (Accept message).
This memo is intended to be an update to the TWAMP RFC. This memo is intended to be an update to the TWAMP core protocol
specified in [RFC5357]. It is not required to implement the feature
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. to zero by senders and MUST be ignored by receivers.
2. Purpose and Scope 2. Purpose and Scope
The purpose of this memo is to describe an additional function and The purpose of this memo is to describe an additional OPTIONAL
feature for TWAMP [RFC5357]. The feature needs a clear description function and feature for TWAMP [RFC5357]. The feature needs a clear
so it can be discussed and (hopefully) adopted in the IP Performance description so it can be discussed and (hopefully) adopted in the IP
Metrics Charter. Performance Metrics Charter.
The scope of the memo is currently limited to specifications of the The scope of the memo is currently limited to specifications of the
following features: following features:
1. Extension of the modes of operation through assignment of a new 1. Extension of the modes of operation through assignment of a new
value in the Mode field to communicate feature capability and value in the Mode field to communicate feature capability and
use, use,
2. the definitions of augmented start session and stop session 2. the definitions of augmented start session and stop session
commands (with corresponding acknowledgements), and commands (with corresponding acknowledgements), and
skipping to change at page 14, line 11 skipping to change at page 14, line 11
SID="3" SID="3"
>>>>>>>>>> Time >>>>>>>>>>>>>>>>>>> Time >>>>>>>>>>>>>>>> Time >>>>> >>>>>>>>>> Time >>>>>>>>>>>>>>>>>>> Time >>>>>>>>>>>>>>>> Time >>>>>
3.7. Additional considerations 3.7. Additional considerations
The value of the Modes field sent by the Server (in the Server The value of the Modes field sent by the Server (in the Server
Greeting message) is the bit-wise OR of the mode values that it is Greeting message) is the bit-wise OR of the mode values that it is
willing to support during this session. willing to support during this session.
If this feature is adopted, the last ???? bits of the Modes 32-bit With the publication of this feature, bit positions 0 through (Z=4)
field are used. A Control-Client MAY ignore other bit positions of the Modes 32-bit field are used. A Control-Client MAY ignore bit
greater than 2 in the Modes Field, or it MAY support other features positions greater than 2 in the Modes Field, or it MAY support
that are communicated in these bit positions. (The unassigned bits OPTIONAL features that are communicated in bit positions 3 and
are available for future protocol extensions.) higher. (The unassigned bits are available for future protocol
extensions.)
Other ways in which TWAMP extends OWAMP are described in [RFC5357]. Other ways in which TWAMP extends OWAMP are described in [RFC5357].
4. TWAMP Test with Individual Session Control 4. TWAMP Test with Individual Session Control
The TWAMP test protocol is similar to the OWAMP [RFC4656] test The TWAMP test protocol is similar to the OWAMP [RFC4656] test
protocol with the exception that the Session-Reflector transmits test protocol with the exception that the Session-Reflector transmits test
packets to the Session-Sender in response to each test packet it packets to the Session-Sender in response to each test packet it
receives. TWAMP [RFC5357] defines two different test packet formats, receives. TWAMP [RFC5357] defines two different test packet formats,
one for packets transmitted by the Session-Sender and one for packets one for packets transmitted by the Session-Sender and one for packets
skipping to change at page 16, line 9 skipping to change at page 16, line 10
Because the TWAMP-Control Command Number registry can contain only Because the TWAMP-Control Command Number registry can contain only
256 values and TWAMP-Modes can only contain thirty-two values, and 256 values and TWAMP-Modes can only contain thirty-two values, and
because TWAMP is an IETF protocol, these registries must be updated because TWAMP is an IETF protocol, these registries must be updated
only by "IETF Consensus" as specified in [RFC5226] (an RFC only by "IETF Consensus" as specified in [RFC5226] (an RFC
documenting registry use that is approved by the IESG). Management documenting registry use that is approved by the IESG). Management
of these registries is described in section 8.2 of [RFC5357] and of these registries is described in section 8.2 of [RFC5357] and
[RFC5618]. [RFC5618].
This memo proposes assignment of values 7, 8, 9 and 10 in the Command This memo proposes assignment of values 7, 8, 9 and 10 in the Command
number Registry, and the next available bit position (indicated by number Registry, and the next available bit position (indicated by
"Z") and corresponding value (indicated by "zzz") in section 3.1 "Z") and corresponding value (indicated by "zzz") in sections 3.1 and
above. Note that these values should be replaced by IANA or the RFC 3.7 above. Note that these values should be replaced by IANA or the
Editor when assigned. RFC Editor when assigned.
6.3. Experimental Numbers 6.3. Experimental Numbers
One experimental value has been assigned in the TWAMP-Control Command One experimental value has been assigned in the TWAMP-Control Command
Number registry. Number registry.
No additional experimental values are assigned in the TWAMP-Modes No additional experimental values are assigned in the TWAMP-Modes
registry. registry.
6.4. Registry Contents 6.4. Registry Contents
skipping to change at page 18, line 7 skipping to change at page 18, line 7
August 2009. August 2009.
8.2. Informative References 8.2. Informative References
[I-D.ietf-ippm-twamp-reflect-octets] [I-D.ietf-ippm-twamp-reflect-octets]
Morton, A. and L. Ciavattone, "TWAMP Reflect Octets and Morton, A. and L. Ciavattone, "TWAMP Reflect Octets and
Symmetrical Size Features", Symmetrical Size Features",
draft-ietf-ippm-twamp-reflect-octets-03 (work in draft-ietf-ippm-twamp-reflect-octets-03 (work in
progress), October 2009. progress), October 2009.
[x] "".
Authors' Addresses Authors' Addresses
Al Morton Al Morton
AT&T Labs AT&T Labs
200 Laurel Avenue South 200 Laurel Avenue South
Middletown,, NJ 07748 Middletown,, NJ 07748
USA USA
Phone: +1 732 420 1571 Phone: +1 732 420 1571
Fax: +1 732 368 1192 Fax: +1 732 368 1192
 End of changes. 13 change blocks. 
64 lines changed or deleted 66 lines changed or added

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