draft-ietf-ippm-twamp-value-added-octets-02.txt   draft-ietf-ippm-twamp-value-added-octets-03.txt 
Network Working Group S. Baillargeon Network Working Group S. Baillargeon
INTERNET-DRAFT C. Flinta INTERNET-DRAFT C. Flinta
Intended Status: Informational A. Johnsson Intended Status: Informational A. Johnsson
Expires: October 6, 2012 S. Ekelin Expires: October 26, 2012 S. Ekelin
Ericsson Ericsson
April 4, 2012 April 26, 2012
Ericsson TWAMP Value-Added Octets Ericsson TWAMP Value-Added Octets
draft-ietf-ippm-twamp-value-added-octets-02.txt draft-ietf-ippm-twamp-value-added-octets-03.txt
Abstract Abstract
This memo describes an extension to the TWAMP test protocol for This memo describes an extension to the TWAMP test protocol for
identifying and managing packet trains, which enables measuring identifying and managing packet trains, which enables measuring
capacity metrics like the available path capacity, tight section capacity metrics like the available path capacity, tight section
capacity and UDP delivery rate in the forward and reverse path capacity and UDP delivery rate in the forward and reverse path
directions. directions.
This memo contains the description of a working prototype. It does This memo contains the description of a working prototype. It does
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on October 6, 2012. This Internet-Draft will expire on October 26, 2012.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 21 skipping to change at page 3, line 21
4 TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . . 7 4 TWAMP Control Extensions . . . . . . . . . . . . . . . . . . . . 7
5 Extended TWAMP Test . . . . . . . . . . . . . . . . . . . . . . 7 5 Extended TWAMP Test . . . . . . . . . . . . . . . . . . . . . . 7
5.1 Sender Behavior . . . . . . . . . . . . . . . . . . . . . . 8 5.1 Sender Behavior . . . . . . . . . . . . . . . . . . . . . . 8
5.1.1 Packet Timings . . . . . . . . . . . . . . . . . . . . 8 5.1.1 Packet Timings . . . . . . . . . . . . . . . . . . . . 8
5.1.2 Session-Sender Packet Format . . . . . . . . . . . . . 8 5.1.2 Session-Sender Packet Format . . . . . . . . . . . . . 8
5.2 Reflector behavior . . . . . . . . . . . . . . . . . . . 12 5.2 Reflector behavior . . . . . . . . . . . . . . . . . . . 12
5.2.1 Session-Reflector Packet Format . . . . . . . . . . 14 5.2.1 Session-Reflector Packet Format . . . . . . . . . . 14
5.3 Additional Considerations . . . . . . . . . . . . . . . . 14 5.3 Additional Considerations . . . . . . . . . . . . . . . . 14
6 Experiments . . . . . . . . . . . . . . . . . . . . . . . . . 14 6 Experiments . . . . . . . . . . . . . . . . . . . . . . . . . 14
7 Security Considerations . . . . . . . . . . . . . . . . . . . 15 7 Security Considerations . . . . . . . . . . . . . . . . . . . 15
8 References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8.1 Normative References . . . . . . . . . . . . . . . . . . 15 9 References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.2 Informative References . . . . . . . . . . . . . . . . . 16 9.1 Normative References . . . . . . . . . . . . . . . . . . 15
9.2 Informative References . . . . . . . . . . . . . . . . . 16
Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1 Introduction 1 Introduction
The notion of embedding a number of meaningful fields in the padding The notion of embedding a number of meaningful fields in the padding
octets has been established as a viable methodology for carrying octets has been established as a viable methodology for carrying
additional information within the TWAMP-Test protocol running between additional information within the TWAMP-Test protocol running between
a Session-Sender and a Session-Reflector [RFC5357] [RFC6038]. a Session-Sender and a Session-Reflector [RFC5357] [RFC6038].
This memo describes an optional extension to the Two-Way Active This memo describes an optional extension to the Two-Way Active
skipping to change at page 4, line 44 skipping to change at page 4, line 44
consensus on the preferred method for measuring capacity metrics. consensus on the preferred method for measuring capacity metrics.
1.1 Requirements Language 1.1 Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"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].
2 Purpose and scope 2 Purpose and scope
The purpose of this memo is to describe the Ericsson Valued-Added The purpose of this memo is to describe the Ericsson TWAMP Valued-
Octets feature (version 1) for TWAMP [RFC5357]. Added Octets feature (version 1) 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
enhancements: enhancements:
o The definition of a structure for embedding a sequence of o The definition of a structure for embedding a sequence of
value-added fields at the beginning of the Packet Padding field value-added fields at the beginning of the Packet Padding field
[RFC5037] or Packet Padding (to be reflected) field [RFC6038] [RFC5357] or Packet Padding (to be reflected) field [RFC6038]
in the TWAMP test packets and, in the TWAMP test packets and,
o The definition of new Session-Sender and Session-Reflector o The definition of new Session-Sender and Session-Reflector
behaviors behaviors
The motivation for this feature is to enable the measurements of The motivation for this feature is to enable the measurements of
capacity metrics on both the forward and reverse paths using a single capacity metrics on both the forward and reverse paths using a single
TWAMP test session. Multiple TWAMP test sessions between a controller TWAMP test session. Multiple TWAMP test sessions between a controller
and a responder with different DSCPs may also be used to evaluate the and a responder with different DSCPs may also be used to evaluate the
QoS impacts on the capacity metrics. QoS impacts on the capacity metrics.
skipping to change at page 13, line 44 skipping to change at page 13, line 44
incomplete train when it receives a packet with a Last SeqNo incomplete train when it receives a packet with a Last SeqNo
in Train belonging to the another train (e.g. next train) of in Train belonging to the another train (e.g. next train) of
the test session, or after a timeout. The timeout MAY be the the test session, or after a timeout. The timeout MAY be the
REFWAIT timer specified in section 4.2 of [RFC5357]. REFWAIT timer specified in section 4.2 of [RFC5357].
- Packets arriving out-of-order within a train MUST be - Packets arriving out-of-order within a train MUST be
buffered at the Session-Reflector if the train is not yet buffered at the Session-Reflector if the train is not yet
transmitted to the Session-Sender. If the train is already transmitted to the Session-Sender. If the train is already
transmitted, the test packet SHOULD be returned to the transmitted, the test packet SHOULD be returned to the
Session-Sender as quickly as possible. The Session-Reflector Session-Sender as quickly as possible. The Session-Reflector
MUST not reorder the test packets if they happen to arrive MUST NOT reorder the test packets if they happen to arrive
out-of-sequence. out-of-sequence.
- Duplicate packets within a train MUST be buffered at the - Duplicate packets within a train MUST be buffered at the
Session-Reflector if the train is not yet transmitted to the Session-Reflector if the train is not yet transmitted to the
Session-Sender. If the train is already transmitted, the Session-Sender. If the train is already transmitted, the
duplicate test packet SHOULD be returned to the Session- duplicate test packet SHOULD be returned to the Session-
Sender as quickly as possible. The Session-Reflector MUST Sender as quickly as possible. The Session-Reflector MUST
not discard duplicate test packets. NOT discard duplicate test packets.
For any other combinations of the Version field and the L and I For any other combinations of the Version field and the L and I
flags, the Session-Reflector SHOULD return the test packet to the flags, the Session-Reflector SHOULD return the test packet to the
Session-Sender as quickly as possible. Session-Sender as quickly as possible.
The Session-Reflector MUST implement the changes described above when The Session-Reflector MUST implement the changes described above when
the Value-Added Octets Version 1 mode is selected. the Value-Added Octets Version 1 mode is selected.
5.2.1 Session-Reflector Packet Format 5.2.1 Session-Reflector Packet Format
skipping to change at page 15, line 37 skipping to change at page 15, line 37
7 Security Considerations 7 Security Considerations
The value-added padding octets permit DoS attacks on the responder The value-added padding octets permit DoS attacks on the responder
host communicating with core TWAMP [RFC5357]. The responder host MUST host communicating with core TWAMP [RFC5357]. The responder host MUST
provide a mechanism to protect or limit the use of its local memory, provide a mechanism to protect or limit the use of its local memory,
buffer space or maximum transmission time for a train. buffer space or maximum transmission time for a train.
The security considerations that apply to any active measurement of The security considerations that apply to any active measurement of
live networks are relevant here as well. See [RFC4656] and [RFC5357]. live networks are relevant here as well. See [RFC4656] and [RFC5357].
8 References 8 IANA Considerations
8.1 Normative References This document has no actions for IANA.
9 References
9.1 Normative References
[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.
[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 Zekauskas, "A One-way Active Measurement
Protocol(OWAMP)", RFC 4656, September 2006. Protocol(OWAMP)", RFC 4656, September 2006.
[RFC5136] Chimento, P. and Ishac,J., "Defining Network Capacity", [RFC5136] Chimento, P. and Ishac,J., "Defining Network Capacity",
RFC 5136, February 2008. RFC 5136, February 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.
skipping to change at page 16, line 12 skipping to change at page 16, line 18
[RFC5136] Chimento, P. and Ishac,J., "Defining Network Capacity", [RFC5136] Chimento, P. and Ishac,J., "Defining Network Capacity",
RFC 5136, February 2008. RFC 5136, February 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.
[RFC6038] Morton, A., Ciavattone, L., TWAMP Reflect Octets and [RFC6038] Morton, A., Ciavattone, L., TWAMP Reflect Octets and
Symmetrical Size Features, RFC6038 , October 2010. Symmetrical Size Features, RFC6038 , October 2010.
8.2 Informative References 9.2 Informative References
[RRBNC] Ribeiro, V., Riedi, R., Baraniuk, R., Navratil, J., [RRBNC] Ribeiro, V., Riedi, R., Baraniuk, R., Navratil, J.,
Cottrel, L., Pathchirp: Efficient available bandwidth Cottrel, L., Pathchirp: Efficient available bandwidth
estimation for network paths, Passive and Active estimation for network paths, Passive and Active
Measurement Workshop, 2003. Measurement Workshop, 2003.
[PDM] Dovrolis, C., Ramanathan, P., and Moore D., Packet [PDM] Dovrolis, C., Ramanathan, P., and Moore D., Packet
Dispersion Techniques and a Capacity Estimation Dispersion Techniques and a Capacity Estimation
Methodology, IEEE/ACM Transactions on Networking, Methodology, IEEE/ACM Transactions on Networking,
December 2004. December 2004.
skipping to change at page 16, line 38 skipping to change at page 16, line 44
Operations and Management Symposium, 2006. Operations and Management Symposium, 2006.
[SBW] Sommers, J., Barford, P., Willinger, W., Laboratory-based [SBW] Sommers, J., Barford, P., Willinger, W., Laboratory-based
calibration of available bandwidth estimation tools, calibration of available bandwidth estimation tools,
Microprocess Microsyst., 2007. Microprocess Microsyst., 2007.
[Y1540] ITU-T Y.1540, Internet protocol data communication service [Y1540] ITU-T Y.1540, Internet protocol data communication service
- IP packet transfer and availability performance - IP packet transfer and availability performance
parameters, 2011. parameters, 2011.
[MRM] Morton, A., Ramachandran, G., Maguluri, G., Reporting
Metrics Different Points of View, draft-ietf-ippm-
reporting-metrics-03, June 2010.
Author's Addresses Author's Addresses
Steve Baillargeon Steve Baillargeon
Ericsson Ericsson
3500 Carling Avenue 3500 Carling Avenue
Ottawa, Ontario K2H 8E9 Ottawa, Ontario K2H 8E9
Canada Canada
EMail: steve.baillargeon@ericsson.com EMail: steve.baillargeon@ericsson.com
Christofer Flinta Christofer Flinta
Ericsson Ericsson
Farogatan 6 Farogatan 6
Stockholm, 164 80 Stockholm, 164 80
Sweden Sweden
EMail: christofer.flinta@ericsson.com EMail: christofer.flinta@ericsson.com
Andreas Johnsson Andreas Johnsson
Ericsson Ericsson
Farogatan 6 Farogatan 6
 End of changes. 15 change blocks. 
19 lines changed or deleted 22 lines changed or added

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