draft-ietf-ippm-twamp-session-cntrl-04.txt   draft-ietf-ippm-twamp-session-cntrl-05.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft AT&T Labs Internet-Draft AT&T Labs
Updates: 5357 (if approved) M. Chiba Updates: 5357 (if approved) M. Chiba
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: September 1, 2010 February 28, 2010 Expires: October 2, 2010 March 31, 2010
Individual Session Control Feature for TWAMP Individual Session Control Feature for TWAMP
draft-ietf-ippm-twamp-session-cntrl-04 draft-ietf-ippm-twamp-session-cntrl-05
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 an the Two-Way Active Measurement Protocol. This memo describes an
OPTIONAL feature for TWAMP, that gives the controlling host the OPTIONAL feature for TWAMP, that gives the controlling host the
ability to start and stop one or more individual test sessions using ability to start and stop one or more individual test sessions using
Session Identifiers. The base capability of the TWAMP protocol Session Identifiers. The base capability of the TWAMP protocol
requires all test sessions previously requested and accepted to start requires all test sessions previously requested and accepted to start
and stop at the same time. and stop at the same time.
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 September 1, 2010. This Internet-Draft will expire on October 2, 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 12 skipping to change at page 3, line 12
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3
3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 4 3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 4
3.1. Connection Setup with Individual Session Control . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . . . . . . 6 Control . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Start-N-Ack Command with Individual Session Control . . . 8 3.3. Start-N-Ack Command with Individual Session Control . . . 7
3.4. Stop-N-Sessions Command with Individual Session Control . 9 3.4. Stop-N-Sessions Command with Individual Session Control . 9
3.5. Stop-N-Ack Command with Individual Session Control . . . . 10 3.5. Stop-N-Ack Command with Individual Session Control . . . . 10
3.6. SERVWAIT Timeout Operation . . . . . . . . . . . . . . . . 12 3.6. SERVWAIT Timeout Operation . . . . . . . . . . . . . . . . 12
3.7. Additional considerations . . . . . . . . . . . . . . . . 13 3.7. Additional considerations . . . . . . . . . . . . . . . . 12
4. TWAMP Test with Individual Session Control . . . . . . . . . . 13 4. TWAMP Test with Individual Session Control . . . . . . . . . . 13
4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 13 4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 13
4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 13 4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 13
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6.1. Registry Specification . . . . . . . . . . . . . . . . . . 14 6.1. Registry Specification . . . . . . . . . . . . . . . . . . 14
6.2. Registry Management . . . . . . . . . . . . . . . . . . . 14 6.2. Registry Management . . . . . . . . . . . . . . . . . . . 14
6.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 15 6.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 15
6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 15 6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 15
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
skipping to change at page 4, line 32 skipping to change at page 4, line 32
during a longer test. This feature permits a specific diagnostic during a longer test. This feature permits a specific diagnostic
test to begin if intermediate results indicate that the test is test to begin if intermediate results indicate that the test is
warranted, for 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],
once it has been published as an RFC. This feature allows a Control- once it has been published as an RFC. This feature allows a Control-
Client to insert a locally-specified request number into the Request- Client to insert a locally-specified request number into the Request-
TW-Session command (in octets originally designated MBZ=Must Be TW-Session command (in octets originally designated MBZ=Must Be
Zero), and a compliant Server will return the request number in its Zero), and a compliant Server will return the request number in its
reply (Accept message). reply (Accept message). The Reflect Octets feature makes multiple
simultaneous session requests possible, and supports the operation of
many simultaneous test sessions (similar to the goal of this memo).
This memo is intended to be an update to the TWAMP core protocol This memo is intended to be an update to the TWAMP core protocol
specified in [RFC5357]. It is not required to implement the feature specified in [RFC5357]. It is not required to implement the feature
described in this memo to claim compliance with [RFC5357]. 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 OPTIONAL The purpose of this memo is to describe an additional OPTIONAL
function and feature for TWAMP [RFC5357]. The feature needs a clear function and feature for TWAMP [RFC5357].
description so it can be discussed and (hopefully) adopted in the IP
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 6, line 46 skipping to change at page 6, line 46
2. The Control-Client and the Server MUST NOT use the start and stop 2. The Control-Client and the Server MUST NOT use the start and stop
commands (2 and 3) and the acknowledgement defined in [RFC5357]. commands (2 and 3) and the acknowledgement defined in [RFC5357].
The Control-Client MUST also set one mode bit to indicate the chosen The Control-Client MUST also set one mode bit to indicate the chosen
security mode (currently bits 0, 1, 2, or 3), consistent with the security mode (currently bits 0, 1, 2, or 3), consistent with the
modes offered by the Server. The Control-Client MAY also set Modes modes offered by the Server. The Control-Client MAY also set Modes
bit Z with other features and bit positions (such as the reflect bit Z with other features and bit positions (such as the reflect
octets feature). octets feature).
If the Control-Client has selected the Reflect Octets feature
[I-D.ietf-ippm-twamp-reflect-octets] in combination with the
Individual Session Control feature (after the Server identified its
capability), AND utilizes the feature to insert a locally-specified
request number in the Request-TW-Session command, THEN the Control
Client MAY send more than one Request-TW-Session command to a given
Server without waiting for the corresponding Accept-Session message.
In such a case the Access-Session response reflects the locally-
specified request number. Note that when the Reflect Octets feature
is being used all Request-TW-Session command and Accept-Session
responses MUST include the locally-specified request number.
3.2. Start-N-Sessions Command with Individual Session Control 3.2. Start-N-Sessions Command with Individual Session Control
Having Having
o initiated Individual Session Control mode in the Setup Response, o initiated Individual Session Control mode in the Setup Response,
o requested one or more test sessions, and o requested one or more test sessions, and
o received affirmative Accept-Session response(s), o received affirmative Accept-Session response(s),
a TWAMP Client MAY start the execution of one or more test sessions a TWAMP Client MAY start the execution of one or more test sessions
by sending a Start-N-Sessions message to the Server (note that "N" by sending a Start-N-Sessions message to the Server (note that "N"
indicates that this command is applicable to one or more sessions, indicates that this command is applicable to one or more sessions,
and does not change with the number of sessions identified in the and does not change with the number of sessions identified in the
skipping to change at page 15, line 5 skipping to change at page 14, line 39
o The Session-Reflector MUST manage all test sessions accepted o The Session-Reflector MUST manage all test sessions accepted
according to their SID. according to their SID.
o Upon receipt of a TWAMP-Control Stop-N-Sessions command o Upon receipt of a TWAMP-Control Stop-N-Sessions command
referencing a specific session/SID, the Session-Reflector MUST referencing a specific session/SID, the Session-Reflector MUST
ignore TWAMP-Test packets (in the same session/SID) that arrive at ignore TWAMP-Test packets (in the same session/SID) that arrive at
the current time plus the Timeout (in the Request-TW-Session the current time plus the Timeout (in the Request-TW-Session
command and assuming subsequent acknowledgement). The Session- command and assuming subsequent acknowledgement). The Session-
Reflector MUST NOT generate a test packet to the Session-Sender Reflector MUST NOT generate a test packet to the Session-Sender
for packets that are ignored. for packets that are ignored. (Note: The Request-TW-Session
command includes sender address + port and receiver address +
port, and this is usually sufficient to distinguish sessions.)
o If the RECOMMENDED REFWAIT timer is implemented, it SHOULD be o If the RECOMMENDED REFWAIT timer is implemented, it SHOULD be
enforced when any test session is in-progress (started and not enforced when any test session is in-progress (started and not
stopped). stopped).
5. Security Considerations 5. Security Considerations
The security considerations that apply to any active measurement of The security considerations that apply to any active measurement of
live networks are relevant here as well. See the security live networks are relevant here as well. See the security
considerations in[RFC4656] and [RFC5357]. considerations in[RFC4656] and [RFC5357].
skipping to change at page 15, line 35 skipping to change at page 15, line 29
TWAMP-Control Command Number registry, and describes the use of the TWAMP-Control Command Number registry, and describes the use of the
new commands. The command number field is a recognized extension new commands. The command number field is a recognized extension
mechanism for TWAMP. mechanism for TWAMP.
6.1. Registry Specification 6.1. Registry Specification
IANA has created a TWAMP-Modes registry (as requested in [RFC5618]). IANA has created a TWAMP-Modes registry (as requested in [RFC5618]).
TWAMP-Modes are specified in TWAMP Server Greeting messages and TWAMP-Modes are specified in TWAMP Server Greeting messages and
Set-up Response messages, as described in section 3.1 of [RFC5357], Set-up Response messages, as described in section 3.1 of [RFC5357],
consistent with section 3.1 of [RFC4656], and extended by this memo. consistent with section 3.1 of [RFC4656], and extended by this memo.
Modes are indicated by setting bits in the 32-bit Modes field. Thus, Modes are indicated by setting bits in the 32-bit Modes field that
this registry can contain a total of 32 possible values. correspond to values in the Modes registry. For the TWAMP-Modes
registry, we expect that new features will be assigned increasing
registry values that correspond to single bit positions, unless there
is a good reason to do otherwise (more complex encoding than single
bit positions may be used in the future, to access the 2^32 value
space).
IANA has also created a TWAMP-Control Command Number registry. IANA has also created a TWAMP-Control Command Number registry.
TWAMP-Control commands are specified by the first octet in TWAMP- TWAMP-Control commands are specified by the first octet in TWAMP-
Control messages as specified in section 3.5 of [RFC5357], and Control messages as specified in section 3.5 of [RFC5357], and
augmented by this memo. This registry may contain 256 possible augmented by this memo. This registry may contain 256 possible
values. values.
6.2. Registry Management 6.2. Registry Management
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 a Mode registry value (indicated by "zzz")
"Z") and corresponding value (indicated by "zzz") in sections 3.1 and corresponding to the next available bit position (indicated by "Z")
3.7 above. Note that these values should be replaced by IANA or the in sections 3.1 and 3.7 above. Note that the "zzz" and "Z" strings
RFC Editor when assigned. should be replaced by IANA or the RFC Editor when values are
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 17, line 16 skipping to change at page 17, line 16
1 Unauthenticated RFC4656, Section 3.1 1 Unauthenticated RFC4656, Section 3.1
2 Authenticated RFC4656, Section 3.1 2 Authenticated RFC4656, Section 3.1
4 Encrypted RFC4656, Section 3.1 4 Encrypted RFC4656, Section 3.1
8 Unauth. TEST protocol, RFC5618, Section 3.1 8 Unauth. TEST protocol, RFC5618, Section 3.1
Auth. CONTROL Auth. CONTROL
-------------------------------------------------------- --------------------------------------------------------
zzz Individual Session this memo, Section 3.1 zzz Individual Session this memo, Section 3.1
Control bit position (Z) Control bit position (Z)
The suggested values are: The suggested values are:
Z=4 zzz=16 The next value corresponding to an unused bit is zzz=16, with Z=4.
7. Acknowledgements 7. Acknowledgements
The authors thank everyone who provided comments on this feature. The authors thank everyone who provided comments on this feature.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 18, line 4 skipping to change at page 18, line 4
[RFC5618] Morton, A. and K. Hedayat, "Mixed Security Mode for the [RFC5618] Morton, A. and K. Hedayat, "Mixed Security Mode for the
Two-Way Active Measurement Protocol (TWAMP)", RFC 5618, Two-Way Active Measurement Protocol (TWAMP)", RFC 5618,
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-04 (work in
progress), October 2009. progress), February 2010.
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
 End of changes. 15 change blocks. 
34 lines changed or deleted 29 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/