draft-ietf-ippm-twamp-session-cntrl-01.txt   draft-ietf-ippm-twamp-session-cntrl-02.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 Intended status: Standards Track M. Chiba
Expires: September 7, 2009 Cisco Systems Expires: April 26, 2010 Cisco Systems
March 6, 2009 October 23, 2009
Individual Session Control Feature for TWAMP Individual Session Control Feature for TWAMP
draft-ietf-ippm-twamp-session-cntrl-01 draft-ietf-ippm-twamp-session-cntrl-02
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
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 7, 2009. This Internet-Draft will expire on April 26, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 12 skipping to change at page 3, line 12
"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].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 4 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 4
3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 5 3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 5
3.1. Connection Setup with Individual Session Control . . . . . 5 3.1. Connection Setup with Individual Session Control . . . . . 5
3.2. Start-N-Sessions Command with Individual Session 3.2. Start-N-Sessions Command with Individual Session
Control . . . . . . . . . . . . . . . . . . . . . . . . . 6 Control . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3. Start-N-Ack Command with Individual Session Control . . . 8 3.3. Start-N-Ack Command with Individual Session Control . . . 9
3.4. Stop-N-Sessions Command with Individual Session Control . 10 3.4. Stop-N-Sessions Command with Individual Session Control . 10
3.5. Stop-N-Ack Command with Individual Session Control . . . . 11 3.5. Stop-N-Ack Command with Individual Session Control . . . . 11
3.6. SERVWAIT Timeout Operation . . . . . . . . . . . . . . . . 13 3.6. SERVWAIT Timeout Operation . . . . . . . . . . . . . . . . 13
3.7. Additional considerations . . . . . . . . . . . . . . . . 13 3.7. Additional considerations . . . . . . . . . . . . . . . . 14
4. TWAMP Test with Individual Session Control . . . . . . . . . . 14 4. TWAMP Test with Individual Session Control . . . . . . . . . . 14
4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 14 4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 14
4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 14 4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
6.1. Registry Specification . . . . . . . . . . . . . . . . . . 15 6.1. Registry Specification . . . . . . . . . . . . . . . . . . 15
6.2. Registry Management . . . . . . . . . . . . . . . . . . . 15 6.2. Registry Management . . . . . . . . . . . . . . . . . . . 15
6.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 15 6.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 16
6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 16 6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 16
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 17 8.2. Informative References . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
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
skipping to change at page 5, line 19 skipping to change at page 5, line 19
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
3. the definition of related procedures for TWAMP entities. 3. the definition of related procedures for TWAMP entities.
The motivation for this feature is the ability to start and stop The motivation for this feature is the ability to start and stop
individual test sessions at will, using a single TWAMP-control individual test sessions at will, using a single TWAMP-control
connection. connection.
When the Server and Control-Client have agreed to use the Individual
Session Control mode during control connection setup, then the
Control-Client, the Server, the Session-Sender, and the Session-
Reflector MUST all conform to the requirements of that mode, as
identified below. The original TWAMP-Control Start and Stop commands
MUST NOT be used.
3. TWAMP Control Extensions 3. TWAMP Control Extensions
TWAMP-Control protocol is a derivative of the OWAMP-Control protocol, TWAMP-Control protocol is a derivative of the OWAMP-Control protocol,
and provides two-way measurement capability. TWAMP [RFC5357] uses and provides two-way measurement capability. TWAMP [RFC5357] uses
the Modes Field to identify and select specific communication the Modes Field to identify and select specific communication
capabilities, and this field is a recognized extension mechanism. capabilities, and this field is a recognized extension mechanism.
The following sections describe one such extension. The following sections describe one such extension.
3.1. Connection Setup with Individual Session Control 3.1. Connection Setup with Individual Session Control
skipping to change at page 6, line 4 skipping to change at page 6, line 19
4 Encrypted RFC4656, Section 3.1 4 Encrypted RFC4656, Section 3.1
8 Unauth. TEST protocol, draft-...-more-twamp (3) 8 Unauth. TEST protocol, draft-...-more-twamp (3)
Auth. CONTROL Auth. CONTROL
-------------------------------------------------------- --------------------------------------------------------
zzz Individual Session this memo, bit position (Z) zzz Individual Session this memo, bit position (Z)
Control Control
In the original OWAMP mode field, setting bit positions 0, 1 or 2 In the original OWAMP mode field, setting bit positions 0, 1 or 2
indicated the security mode of the Control protocol, and the Test indicated the security mode of the Control protocol, and the Test
protocol inherited the same mode (see section 4 of [RFC4656]). In protocol inherited the same mode (see section 4 of [RFC4656]). In
the [I-D.ietf-ippm-more-twamp] memo, bit position (3) allows a the [RFC5618] memo, bit position (3) allows a different security mode
different security mode in the Test protocol and uses the in the Test protocol and uses the unauthenticated test packet format.
unauthenticated test packet format.
If the Server sets the new bit position (bit position Z) in the If the Server sets the new bit position (bit position Z) in the
Server Greeting message to indicate its capabilities, then the Server Server Greeting message to indicate its capabilities, then the Server
and Session-Reflector MUST comply with the requirements of this memo and Session-Reflector MUST comply with the requirements of this memo
to control sessions on an individual basis if desired. to control sessions on an individual basis if desired.
If the Control-Client intends to control sessions on an individual If the Control-Client intends to control sessions on an individual
basis (according to the requirements in this memo), it MUST set the basis (according to the requirements in this memo), it MUST set the
mode bit (Z, corresponding to the new mode) in the Setup Response mode bit (Z, corresponding to the new mode) in the Setup Response
message. This means that: message. This means that:
skipping to change at page 8, line 14 skipping to change at page 9, line 5
OWAMP section 3.5 [RFC4656] (and referenced in TWAMP). Note that the OWAMP section 3.5 [RFC4656] (and referenced in TWAMP). Note that the
SID is assigned by the Server during the session request exchange. SID is assigned by the Server during the session request exchange.
The message is terminated with a single block HMAC, as illustrated The message is terminated with a single block HMAC, as illustrated
above. above.
The Server MUST respond with one or more Start-N-Ack messages (which The Server MUST respond with one or more Start-N-Ack messages (which
SHOULD be sent as quickly as possible). Start-N-Ack messages SHALL SHOULD be sent as quickly as possible). Start-N-Ack messages SHALL
have the format defined in the next session. have the format defined in the next session.
<<<<< Comment: Al thinks we don't need the limitation below now,
unless it refers to the EXISTING Start-Sessions command. The real
question is, Do we require (MUST) the use of the -N- commands in
Indiv.Sess.Cntrl mode, or allow both types??? I'm leaning toward -N-
commands ONLY. >>>> The Control Client MUST NOT send a subsequent
Start Sessions command until an outstanding message is acknowledged
with a Start-Ack message.
When using Individual Session Control mode and its Start-N-Ack When using Individual Session Control mode and its Start-N-Ack
command as described in the next section, multiple Start-N-Sessions command as described in the next section, multiple Start-N-Sessions
commands MAY be sent without waiting for acknowledgement, and the commands MAY be sent without waiting for acknowledgement, and the
Start-N-sessions commands MAY arrive in any order. Start-N-sessions commands MAY arrive in any order.
3.3. Start-N-Ack Command with Individual Session Control 3.3. Start-N-Ack Command with Individual Session Control
The Server responds to the Start-N-Sessions command (for one or more The Server responds to the Start-N-Sessions command (for one or more
specific sessions referenced by their SIDs) with one or more Start-N- specific sessions referenced by their SIDs) with one or more Start-N-
Ack commands with Accept fields corresponding to one or more of the Ack commands with Accept fields corresponding to one or more of the
skipping to change at page 15, line 19 skipping to change at page 15, line 30
the new mode is used. This field is a recognized extension mechanism the new mode is used. This field is a recognized extension mechanism
for TWAMP. for TWAMP.
This memo also requests assignment of four command numbers in the This memo also requests assignment of four command numbers in the
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 IANA has created a TWAMP-Modes registry (as requested in [RFC5618]).
[I-D.ietf-ippm-more-twamp]). TWAMP-Modes are specified in TWAMP TWAMP-Modes are specified in TWAMP Server Greeting messages and
Server Greeting messages and Set-up Response messages, as described Set-up Response messages, as described in section 3.1 of [RFC5357],
in section 3.1 of [RFC5357], consistent with section 3.1 of consistent with section 3.1 of [RFC4656], and extended by this memo.
[RFC4656], and extended by this memo. Modes are indicated by setting Modes are indicated by setting bits in the 32-bit Modes field. Thus,
bits in the 32-bit Modes field. Thus, this registry can contain a this registry can contain a total of 32 possible values.
total of 32 possible values.
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 [RFC2434](an RFC documenting only by "IETF Consensus" as specified in [RFC2434](an RFC documenting
registry use that is approved by the IESG). Management of these registry use that is approved by the IESG). Management of these
registries is described in section 8.2 of [RFC5357] and registries is described in section 8.2 of [RFC5357] and [RFC5618].
[I-D.ietf-ippm-more-twamp].
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 section 3.1
above. Note that these values should be replaced by IANA or the RFC above. Note that these values should be replaced by IANA or the RFC
Editor when assigned. 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
skipping to change at page 16, line 38 skipping to change at page 17, line 14
Value Description Reference/Explanation Value Description Reference/Explanation
0 Reserved 0 Reserved
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, draft-...-more-twamp (3) 8 Unauth. TEST protocol, draft-...-more-twamp (3)
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:
Z=4 zzz=16
7. Acknowledgements 7. Acknowledgements
The author would like to thank anyone who provides valuable comments The author would like to thank anyone who provides valuable comments
on this feature. on this feature.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-ippm-more-twamp]
Morton, A. and K. Hedayat, "More Features for TWAMP",
draft-ietf-ippm-more-twamp-00 (work in progress),
October 2008.
[I-D.ietf-ippm-twamp-reflect-octets] [I-D.ietf-ippm-twamp-reflect-octets]
Morton, A. and L. Ciavattone, "TWAMP Reflect Octets Morton, A. and L. Ciavattone, "TWAMP Reflect Octets
Feature", draft-ietf-ippm-twamp-reflect-octets-00 (work in Feature", draft-ietf-ippm-twamp-reflect-octets-02 (work in
progress), October 2008. progress), July 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M. [RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M.
Zekauskas, "A One-way Active Measurement Protocol Zekauskas, "A One-way Active Measurement Protocol
(OWAMP)", RFC 4656, September 2006. (OWAMP)", RFC 4656, September 2006.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, October 2008. RFC 5357, October 2008.
[RFC5618] Morton, A. and K. Hedayat, "Mixed Security Mode for the
Two-Way Active Measurement Protocol (TWAMP)", RFC 5618,
August 2009.
8.2. Informative References 8.2. Informative References
[x] "". [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
 End of changes. 17 change blocks. 
41 lines changed or deleted 39 lines changed or added

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