draft-ietf-ippm-more-twamp-01.txt   draft-ietf-ippm-more-twamp-02.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) K. Hedayat Updates: 5357 (if approved) K. Hedayat
Intended status: Standards Track EXFO Intended status: Standards Track EXFO
Expires: November 6, 2009 May 5, 2009 Expires: November 21, 2009 May 20, 2009
More Features for the Two-Way Active Measurement Protocol - TWAMP More Features for the Two-Way Active Measurement Protocol - TWAMP
draft-ietf-ippm-more-twamp-01 draft-ietf-ippm-more-twamp-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 November 6, 2009. This Internet-Draft will expire on November 21, 2009.
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 4, line 11 skipping to change at page 4, line 11
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
8. Normative References . . . . . . . . . . . . . . . . . . . . . 9 8. Normative References . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
The Two-Way Active Measurement Protocol, TWAMP [RFC5357] is an The Two-Way Active Measurement Protocol, TWAMP [RFC5357] 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 is a growing number
number TWAMP implementations at present, and wide-spread usage is TWAMP implementations at present, and wide-spread usage is expected.
expected. There are even devices that are designed to test There are even devices that are designed to test implementations for
implementations for protocol compliance. protocol compliance.
This memo describes a simple extension for TWAMP, the option to use This memo describes a simple extension for TWAMP, the option to use
different security modes in the TWAMP-Control and TWAMP-Test different security modes in the TWAMP-Control and TWAMP-Test
protocols (mixed security mode). It also requests that IANA protocols (mixed security mode). It also requests that IANA
establish a registry for additional new features, called the TWAMP- establish a registry for additional new features, called the TWAMP-
Modes registry. Modes registry.
When the Server and Control-Client have agreed to use the mixed When the Server and Control-Client have agreed to use the mixed
security mode during control connection setup, then the Control- security mode during control connection setup, then the Control-
Client, the Server, the Session-Sender and the Session-Reflector MUST Client, the Server, the Session-Sender and the Session-Reflector MUST
skipping to change at page 6, line 45 skipping to change at page 6, line 45
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
transmitted by the Session-Reflector. As with OWAMP-Test protocol transmitted by the Session-Reflector. As with OWAMP-Test protocol
there are three security modes that also determine the test packet there are three security modes that also determine the test packet
format: unauthenticated, authenticated, and encrypted. This TWAMP format: unauthenticated, authenticated, and encrypted. This TWAMP
extension makes it possible to use TWAMP-Test Unauthenticated mode extension makes it possible to use TWAMP-Test Unauthenticated mode
regardless of the mode used in the TWAMP-Control protocol. regardless of the mode used in the TWAMP-Control protocol.
This section describes OPTIONAL extensions. When the Server has When the Server has identified the ability to support the mixed
identified the ability to support the mixed security mode, the security mode, the Control-Client has selected the mixed security
Control-Client has selected the mixed security mode in its Set-Up- mode in its Set-Up-Response, and the Server responds with a zero
Response, and the Server responds with a zero Accept field in the Accept field in the Server-Start message, these extensions are
Server-Start message, then these extensions are conditionally
REQUIRED. REQUIRED.
4.1. Sender Behavior 4.1. Sender Behavior
This section describes extensions to the behavior of the TWAMP This section describes extensions to the behavior of the TWAMP
Session-Sender. Session-Sender.
4.1.1. Packet Timings 4.1.1. Packet Timings
The Send Schedule is not utilized in TWAMP, and there are no The Send Schedule is not utilized in TWAMP, and there are no
skipping to change at page 8, line 18 skipping to change at page 8, line 18
the OWAMP-Control specification[RFC4656], and describes behavior when the OWAMP-Control specification[RFC4656], and describes behavior when
the new mode is used. This memo requests creation of an IANA the new mode is used. This memo requests creation of an IANA
registry for the TWAMP Modes field. This field is a recognized registry for the TWAMP Modes field. This field is a recognized
extension mechanism for TWAMP. extension mechanism for TWAMP.
6.1. Registry Specification 6.1. Registry Specification
IANA is requested to create a TWAMP-Modes registry. TWAMP-Modes are IANA is requested to create a TWAMP-Modes registry. TWAMP-Modes are
specified in TWAMP Server Greeting messages and Set-up Response specified in TWAMP Server Greeting messages and Set-up Response
messages consistent with section 3.1 of [RFC4656] and section 3.1 of messages consistent with section 3.1 of [RFC4656] and section 3.1 of
[RFC5357], and extended by this memo. Modes are indicated by setting [RFC5357], and extended by this memo. Modes are currently indicated
bits in the 32-bit Modes Field. Thus, this registry can contain a by setting single bits in the 32-bit Modes Field. However, more
total of 32 possible bit positions and corresponding values. complex encoding may be used in the future. Thus, this registry can
contain a total of 2^32 possible assignments.
6.2. Registry Management 6.2. Registry Management
Because the TWAMP-Modes registry can contain only thirty-two values, Because the TWAMP-Modes registry can contain a maximum of 2^32
and because TWAMP is an IETF protocol, this registry must be updated values, and because TWAMP is an IETF protocol, this registry must be
only by "IETF Consensus" as specified in [RFC5226](an RFC documenting updated only by "IETF Review" as specified in [RFC5226](an RFC
registry use that is approved by the IESG). For the TWAMP-Modes documenting registry use that is approved by the IESG). For the
registry, we expect that new features will be assigned using TWAMP-Modes registry, we expect that new features will be assigned
monotonically increasing bit positions and in the range [0-31] and using monotonically increasing single bit positions and in the range
the corresponding values, unless there is a good reason to do [0-31], unless there is a good reason to do otherwise (more complex
otherwise. encoding than single bit positions may be used in the future, to
access the 2^32 value space).
6.3. Experimental Numbers 6.3. Experimental Numbers
No experimental values are currently assigned for the Modes Registry. No experimental values are currently assigned for the Modes Registry.
6.4. Initial Registry Contents 6.4. Initial Registry Contents
TWAMP Modes Registry TWAMP Modes Registry
Value Description Semantics Definition Value Description Semantics Definition
0 Reserved 0 Reserved
skipping to change at page 10, line 26 skipping to change at page 10, line 26
URI: http://home.comcast.net/~acmacm/ URI: http://home.comcast.net/~acmacm/
Kaynam Hedayat Kaynam Hedayat
EXFO EXFO
285 Mill Road 285 Mill Road
Chelmsford, MA 01824 Chelmsford, MA 01824
USA USA
Phone: +1 Phone: +1
Fax: +1 Fax: +1
Email: khedayat@exfo.com Email: kaynam.hedayat@exfo.com
URI: http://www.exfo.com/ URI: http://www.exfo.com/
 End of changes. 8 change blocks. 
24 lines changed or deleted 25 lines changed or added

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