draft-ietf-ippm-twamp-session-cntrl-06.txt   draft-ietf-ippm-twamp-session-cntrl-07.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: October 10, 2010 April 8, 2010 Expires: October 10, 2010 April 8, 2010
Individual Session Control Feature for TWAMP Individual Session Control Feature for TWAMP
draft-ietf-ippm-twamp-session-cntrl-06 draft-ietf-ippm-twamp-session-cntrl-07
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 5, line 4 skipping to change at page 5, line 4
feature supports the efficient establishment of many simultaneous feature supports the efficient establishment of many simultaneous
test sessions which the Individual Session Control feature can then test sessions which the Individual Session Control feature can then
manage (start/stop). manage (start/stop).
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
feature described in this memo to claim compliance with [RFC5357]. 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. Also, the HMAC to zero by senders and MUST be ignored by receivers. Also, the HMAC
(Hashed Message Authentication Code) is calculated as defined in (Hashed Message Authentication Code) MUST be calculated as defined in
Section 3.2 [RFC4656]. Section 3.2 of [RFC4656].
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]. function and feature for TWAMP [RFC5357].
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:
1. Extension of the modes of operation through assignment of a new 1. Extension of the modes of operation through assignment of a new
 End of changes. 2 change blocks. 
3 lines changed or deleted 3 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/