draft-ietf-ippm-twamp-session-cntrl-02.txt   draft-ietf-ippm-twamp-session-cntrl-03.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: April 26, 2010 Cisco Systems Expires: August 21, 2010 Cisco Systems
October 23, 2009 February 17, 2010
Individual Session Control Feature for TWAMP Individual Session Control Feature for TWAMP
draft-ietf-ippm-twamp-session-cntrl-02 draft-ietf-ippm-twamp-session-cntrl-03
Abstract
The IETF has completed its work on the core specification of TWAMP -
the Two-Way Active Measurement Protocol. This memo describes a new
feature for TWAMP, that gives the controlling host the ability to
start and stop one or more individual test sessions using Session
Identifiers. The base capability of the TWAMP protocol requires all
test sessions previously requested and accepted to start and stop at
the same time.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
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
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
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 April 26, 2010. This Internet-Draft will expire on August 21, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
The IETF has completed its work on the core specification of TWAMP - described in the BSD License.
the Two-Way Active Measurement Protocol. This memo describes a new
feature for TWAMP, that gives the controlling host the ability to
start and stop one or more individual test sessions using Session
Identifiers. The base capability of the TWAMP protocol requires all
test sessions previously requested and accepted to start and stop at
the same time.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", This document may contain material from IETF Documents or IETF
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this Contributions published or made publicly available before November
document are to be interpreted as described in RFC 2119 [RFC2119]. 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 7 Control . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3. Start-N-Ack Command with Individual Session Control . . . 9 3.3. Start-N-Ack Command with Individual Session Control . . . 9
skipping to change at page 3, line 30 skipping to change at page 3, line 30
4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 14 4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 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 . . . . . . . . . . . . . . . . . . . 16 6.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 16
6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 16 6.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 16
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 18 8.2. Informative References . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 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
skipping to change at page 6, line 10 skipping to change at page 6, line 10
mode requires one new bit position (and value) to identify the mode requires one new bit position (and value) to identify the
ability of the Server/Session-Reflector to start and stop specific ability of the Server/Session-Reflector to start and stop specific
sessions (according to their Session Identifier, or SID). This new sessions (according to their Session Identifier, or SID). This new
feature requires an additional TWAMP mode bit assignment as follows: feature requires an additional TWAMP mode bit assignment as follows:
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, RFC5618, Section 3.1
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 [RFC5618] memo, bit position (3) allows a different security mode the [RFC5618] memo, bit position (3) allows a different security mode
in the Test protocol and uses the unauthenticated test packet format. in the Test protocol and uses the unauthenticated test packet format.
skipping to change at page 15, line 48 skipping to change at page 15, line 48
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 [RFC5226] (an RFC
registry use that is approved by the IESG). Management of these documenting registry use that is approved by the IESG). Management
registries is described in section 8.2 of [RFC5357] and [RFC5618]. of these registries is described in section 8.2 of [RFC5357] and
[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 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 17, line 9 skipping to change at page 17, line 9
8 Start-N-Ack this memo, Section 3.3 8 Start-N-Ack this memo, Section 3.3
9 Stop-N-Sessions this memo, Section 3.4 9 Stop-N-Sessions this memo, Section 3.4
10 Stop-N-Ack this memo, Section 3.5 10 Stop-N-Ack this memo, Section 3.5
TWAMP-Modes Registry TWAMP-Modes Registry
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, 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 Z=4 zzz=16
7. Acknowledgements 7. Acknowledgements
The author would like to thank anyone who provides valuable comments The authors thank everyone who provided comments on this feature.
on this feature.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-ippm-twamp-reflect-octets]
Morton, A. and L. Ciavattone, "TWAMP Reflect Octets
Feature", draft-ietf-ippm-twamp-reflect-octets-02 (work in
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
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
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.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[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 [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]
Morton, A. and L. Ciavattone, "TWAMP Reflect Octets and
Symmetrical Size Features",
draft-ietf-ippm-twamp-reflect-octets-03 (work in
progress), October 2009.
[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
USA USA
 End of changes. 16 change blocks. 
52 lines changed or deleted 59 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/