draft-ietf-ippm-twamp-reflect-octets-01.txt   draft-ietf-ippm-twamp-reflect-octets-02.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft L. Ciavattone Internet-Draft L. Ciavattone
Intended status: Standards Track AT&T Labs Intended status: Standards Track AT&T Labs
Expires: September 7, 2009 March 6, 2009 Expires: January 14, 2010 July 13, 2009
TWAMP Reflect Octets Feature TWAMP Reflect Octets Feature
draft-ietf-ippm-twamp-reflect-octets-01 draft-ietf-ippm-twamp-reflect-octets-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 42 skipping to change at page 1, line 42
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 January 14, 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 19 skipping to change at page 3, line 19
3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 5 3. TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . 5
3.1. Connection Setup with Reflect Padding Feature . . . . . . 5 3.1. Connection Setup with Reflect Padding Feature . . . . . . 5
3.2. Request-TW-Session Packet Format . . . . . . . . . . . . . 6 3.2. Request-TW-Session Packet Format . . . . . . . . . . . . . 6
3.3. Accept Session Packet Format . . . . . . . . . . . . . . . 8 3.3. Accept Session Packet Format . . . . . . . . . . . . . . . 8
3.4. Additional considerations . . . . . . . . . . . . . . . . 8 3.4. Additional considerations . . . . . . . . . . . . . . . . 8
4. Extended TWAMP Test . . . . . . . . . . . . . . . . . . . . . 9 4. Extended TWAMP Test . . . . . . . . . . . . . . . . . . . . . 9
4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 9 4.1. Sender Behavior . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. Packet Timings . . . . . . . . . . . . . . . . . . . . 9 4.1.1. Packet Timings . . . . . . . . . . . . . . . . . . . . 9
4.1.2. Packet Formats and Contents . . . . . . . . . . . . . 9 4.1.2. Packet Formats and Contents . . . . . . . . . . . . . 9
4.1.3. Padding Truncation . . . . . . . . . . . . . . . . . . 11 4.1.3. Padding Truncation . . . . . . . . . . . . . . . . . . 11
4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 11 4.2. Reflector Behavior . . . . . . . . . . . . . . . . . . . . 12
4.2.1. Packet Format and Contents . . . . . . . . . . . . . . 11 4.2.1. Packet Format and Contents . . . . . . . . . . . . . . 12
4.2.2. Padding Truncation . . . . . . . . . . . . . . . . . . 12 4.2.2. Padding Truncation . . . . . . . . . . . . . . . . . . 13
5. Possible Alternative . . . . . . . . . . . . . . . . . . . . . 13 5. Possible Alternative . . . . . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7.1. Registry Specification . . . . . . . . . . . . . . . . . . 16 7.1. Registry Specification . . . . . . . . . . . . . . . . . . 17
7.2. Registry Management . . . . . . . . . . . . . . . . . . . 16 7.2. Registry Management . . . . . . . . . . . . . . . . . . . 17
7.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 16 7.3. Experimental Numbers . . . . . . . . . . . . . . . . . . . 17
7.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 16 7.4. Registry Contents . . . . . . . . . . . . . . . . . . . . 17
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
9.1. Normative References . . . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . . 18
9.2. Informative References . . . . . . . . . . . . . . . . . . 17 9.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 TWAMP implementations at present, and wide-spread usage is number TWAMP implementations at present, and wide-spread usage is
skipping to change at page 10, line 13 skipping to change at page 10, line 13
shown below for unauthenticated mode: shown below for unauthenticated mode:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Estimate | MBZ (2 octets) | | Error Estimate | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| | | |
| Packet Padding (to be reflected) | | Packet Padding (to be reflected) |
. (length in octets specified elsewhere) . . (length in octets specified in command) .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. Additional Packet Padding . . Additional Packet Padding .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The "Packet Padding (to be reflected)" Field SHALL correspond to the The "Packet Padding (to be reflected)" Field SHALL correspond to the
length of octets specified in the Request-TW-Session "Length of length of octets specified in the Request-TW-Session "Length of
padding to reflect" Field to this test session. These are the octets padding to reflect" Field to this test session. These are the octets
that the Session-Sender expects will be returned by the Session- that the Session-Sender expects will be returned by the Session-
skipping to change at page 10, line 42 skipping to change at page 11, line 7
"Additional Packet Padding", in octets = "Additional Packet Padding", in octets =
"Padding Length" - "Length of padding to reflect" "Padding Length" - "Length of padding to reflect"
One possible use of the first 4 octets of the "Packet Padding (to be One possible use of the first 4 octets of the "Packet Padding (to be
reflected)" Field is shown below: reflected)" Field is shown below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Server octets |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client octets | Server octets | | Client octets | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Packet Padding (to be reflected) | | Packet Padding (to be reflected) |
. (length in octets specified elsewhere) . . (length in octets specified elsewhere) .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In this example, the "Client octets" and the "Server octets" fields In this example, the "Client octets" and the "Server octets" fields
contain the same information that the Client and Server exchanged in contain the same information that the Client and Server exchanged in
the Request-TW-Session and Accept-Session messages corresponding to the Request-TW-Session and Accept-Session messages corresponding to
this specific test session. These octets would be reflected the same this specific test session. These octets would be reflected the same
as the rest of the "Packet Padding (to be reflected)" Field. as the rest of the "Packet Padding (to be reflected)" Field.
4.1.3. Padding Truncation 4.1.3. Padding Truncation
skipping to change at page 11, line 20 skipping to change at page 11, line 36
directions. The amount of padding needed depends on BOTH the directions. The amount of padding needed depends on BOTH the
security mode (Unauthenticated/Authenticated/Encrypted) and whether security mode (Unauthenticated/Authenticated/Encrypted) and whether
the Reflect Octets mode is selected simultaneously. the Reflect Octets mode is selected simultaneously.
When using the Truncate Padding mode, the Session-Sender MUST append When using the Truncate Padding mode, the Session-Sender MUST append
sufficient Packet Padding octets to allow the same IP packet payload sufficient Packet Padding octets to allow the same IP packet payload
lengths to be used in each direction of transmission (this is usually lengths to be used in each direction of transmission (this is usually
desirable). To compensate for the Session-Reflector's larger test desirable). To compensate for the Session-Reflector's larger test
packet format, the Session-Sender MUST append at least 27 octets of packet format, the Session-Sender MUST append at least 27 octets of
padding in Unauthenticated mode, and at least 56 octets in padding in Unauthenticated mode, and at least 56 octets in
Authenticated and Encrypted modes. Authenticated and Encrypted modes. The sizes of TWAMP Test protocol
packets and the resulting truncated padding to achieve equal packet
sizes in both directions are shown in the table below:
+-------------------+----------------------+---------------------+
| Octets in: | Unauthenticated Mode | Auth/Encrypted Mode |
+-------------------+----------------------+---------------------+
| Reflector Header | 41 | 104 |
| Sender Header | 14 | 48 |
| Truncated Padding | 27 | 56 |
+-------------------+----------------------+---------------------+
TWAMP-Test Padding Trucation
When using the Reflect Octets mode simultaneously with the Truncate When using the Reflect Octets mode simultaneously with the Truncate
Padding mode, the Session-Sender MUST append at least 27 octets of Padding mode, the Session-Sender MUST append at least 27 octets of
padding plus the "Length of the padding to reflect" octets when padding plus the "Length of the padding to reflect" octets when
operating in Unauthenticated mode. The Session-Sender MUST append at operating in Unauthenticated mode. The Session-Sender MUST append at
least 56 octets of padding plus the "Length of the padding to least 56 octets of padding plus the "Length of the padding to
reflect" octets when operating in Authenticated and Encrypted modes. reflect" octets when operating in Authenticated and Encrypted modes.
4.2. Reflector Behavior 4.2. Reflector Behavior
skipping to change at page 12, line 28 skipping to change at page 13, line 28
| Sender Sequence Number | | Sender Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Timestamp | | Sender Timestamp |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Error Estimate | MBZ | | Sender Error Estimate | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender TTL | Packet Padding (from Session-Sender) | | Sender TTL | Packet Padding (from Session-Sender) |
+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+ +
. . . .
. Packet Padding (from Session-Sender) . + +-+-+-+-+-+-+-+-+
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Packet Padding (from Session-Sender) | |
| | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
+-+-+-+-+-+-+-+-+ + | |
| |
. Additional Packet Padding . . Additional Packet Padding .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The "Packet Padding (from Session-Sender)" field MUST be the same The "Packet Padding (from Session-Sender)" field MUST be the same
octets as the "Packet Padding (to be reflected)" field in the octets as the "Packet Padding (to be reflected)" field in the
Session-Sender's test packet, and therefore MUST conform to the Session-Sender's test packet, and therefore MUST conform to the
length specified in the Request-TW-Session message. length specified in the Request-TW-Session message.
IF the test packet length is truncated within the padding fields in IF the test packet length is truncated within the padding fields in
conformance with the RECOMMENDED truncation process in TWAMP section conformance with the RECOMMENDED truncation process in TWAMP section
4.2.1 [RFC5357], THEN ALL padding designated to be reflected MUST be 4.2.1 [RFC5357], THEN ALL padding designated to be reflected MUST be
skipping to change at page 17, line 16 skipping to change at page 18, line 16
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Walt Steverson for helpful review and The authors would like to thank Walt Steverson for helpful review and
comments. comments.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-ippm-more-twamp] [I-D.ietf-ippm-more-twamp]
Morton, A. and K. Hedayat, "More Features for TWAMP", Morton, A. and K. Hedayat, "More Features for the Two-Way
draft-ietf-ippm-more-twamp-00 (work in progress), Active Measurement Protocol - TWAMP",
October 2008. draft-ietf-ippm-more-twamp-02 (work in progress),
May 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
 End of changes. 11 change blocks. 
31 lines changed or deleted 47 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/