wdiff rfc8545.alt-original rfc8545.txt

Network Working Group
Internet Engineering Task Force (IETF) A. Morton, Ed.
Internet-Draft
Request for Comments: 8545 AT&T Labs
Updates: 4656 and 4656, 5357 (if approved) G. Mirsky, Ed.
Intended status:
Category: Standards Track ZTE Corp.
Expires: June 12,
ISSN: 2070-1721 March 2019 December 9, 2018

OWAMP and TWAMP

Well-Known Port Assignments
draft-ietf-ippm-port-twamp-test-04 for the One-Way Active Measurement Protocol
(OWAMP) and the Two-Way Active Measurement Protocol (TWAMP)

Abstract

This memo explains the motivation and describes the re-assignment reassignment of
well-known ports for the One-way One-Way Active Measurement Protocol (OWAMP)
and Two-
way the Two-Way Active Measurement Protocol (OWAMP and TWAMP) protocols (TWAMP) for control and measurement, and
measurement. It also clarifies the meaning and composition of these standards track
Standards Track protocol names for the industry.

The

This memo updates RFC RFCs 4656 and RFC 5357, in terms of the UDP well-
known well-known
port assignments, and it clarifies the complete OWAMP and TWAMP
protocol composition for the industry.

Status of This Memo

This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents an Internet Standards Track document.

This document is a product of the Internet Engineering Task Force
(IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list It represents the consensus of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid the IETF community. It has
received public review and has been approved for a maximum publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of six months RFC 7841.

Information about the current status of this document, any errata,
and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

This Internet-Draft will expire on June 12, 2019.
https://www.rfc-editor.org/info/rfc8545.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2
3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Definitions and Background . . . . . . . . . . . . . . . . . 3
5. New Well-Known Ports . . . . . . . . . . . . . . . . . . . . 4
5.1. Impact on TWAMP-Control Protocol . . . . . . . . . . . . 4
5.2. Impact on OWAMP-Control Protocol . . . . . . . . . . . . 5
5.3. Impact on OWAMP/TWAMP-Test OWAMP-Test/TWAMP-Test Protocols . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 7
8. Contributors . . . . . . References . . . . . . . . . . . . . . . . . . 7
9. Appendix A . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
10. Acknowledgements
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Background on TWAMP Light . . . . . 8
11. References . . . . . . . . 8
Acknowledgements . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . 9
Contributors . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9

1. Introduction

The IETF IP Performance Metrics (IPPM) working group Working Group first developed
the One-Way Active Measurement Protocol, OWAMP, Protocol (OWAMP), as specified in
[RFC4656]. Further protocol development to support testing resulted
in the Two-Way Active Measurement Protocol, TWAMP, Protocol (TWAMP), as specified in
[RFC5357].

Both OWAMP and TWAMP require the implementation of a control and mode
negotiation protocol (OWAMP-Control and TWAMP-Control) which that employs
the reliable transport services of TCP (including security
configuration and key derivation). The control protocols arrange for
the configuration and management of test sessions using the
associated test protocol (OWAMP-Test or TWAMP-Test) on UDP transport.

In this memo,

The IETF recognizes the value of assigning a well-known UDP port to
the *-Test protocols, OWAMP-Test and TWAMP-Test protocols and also recognizes that this
goal can easily be easily arranged through port re-assignments. reassignments.

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.

3. Scope

The scope of this memo is twofold: (1) to re-allocate reallocate the well-known
ports for the UDP
Test test protocols that compose necessary parts of
their respective
standards track protocols, OWAMP Standards Track protocols (OWAMP and TWAMP, along with clarifications
of TWAMP) and
(2) to clarify the complete protocol meaning and composition of these Standards Track
protocol names for the industry.

The

This memo updates [RFC4656] and [RFC5357], in terms of the UDP well-
known
well-known port assignments.

4. Definitions and Background

This section defines key terms and clarifies the required composition
of the OWAMP and TWAMP standards-track Standards Track protocols.

OWAMP-Control

"OWAMP-Control" is the protocol defined in Section 3 of [RFC4656].

OWAMP-Test

"OWAMP-Test" is the protocol defined in Section 4 of [RFC4656].

OWAMP is described in a this direct quote from Section 1.1 of[RFC4656]: of
[RFC4656]: "OWAMP actually consists of two inter-related protocols: OWAMP-
Control
OWAMP-Control and OWAMP-Test." A similar sentence appears in
Section 2 of [RFC4656]. For avoidance of doubt, the implementation
of both OWAMP-
Control OWAMP-Control and OWAMP-Test are is REQUIRED for standards-track Standards Track
OWAMP as specified in [RFC4656] (aplying (applying the consensus of many
dictionary definitions of "consist").

TWAMP-Control

"TWAMP-Control" is the protocol defined in Section 3 of [RFC5357].

TWAMP-Test

"TWAMP-Test" is the protocol defined in Section 4 of [RFC5357].

TWAMP is described in a this direct quote from Section 1.1 of
[RFC5357]: "Similar to OWAMP [RFC4656], TWAMP consists of two
inter-related protocols: TWAMP-Control and TWAMP-Test." For
avoidance of doubt, the implementation of both TWAMP-Control and
TWAMP-Test are is REQUIRED for
standards-track Standards Track TWAMP as specified in
[RFC5357] (aplying (applying the consensus of many dictionary definitions of
"consist").

TWAMP Light

"TWAMP Light" is an idea described in Informative Appendix I ("TWAMP Light
(Informative)") of
[RFC5357], and [RFC5357]; TWAMP Light includes an un-specified unspecified
control protocol combined with the TWAMP-Test protocol. The In
[RFC5357], the TWAMP Light idea was relegated to
the Appendix I because it
TWAMP Light failed to meet the requirements for IETF protocols (there
are no specifications for negotiating this form of
operation, operation and no
specifications for mandatory-to-implement security features), as
described in Appendix A of this memo, which cites memo. See also [LarsAD] and [TimDISCUSS] .
[TimDISCUSS].

Since the idea of TWAMP Light clearly includes the TWAMP-Test
component of TWAMP, it is considered reasonable for future systems to
use the TWAMP-Test well-known UDP port (whose re-allocated reallocated assignment
is requested here). specified in this document). Clearly, the TWAMP Light idea
envisions many components and communication capabilities beyond
TWAMP-Test (implementing the security requirements, for example), otherwise example);
otherwise, Appendix I of [RFC5357] would be one sentence long (equivocating
(equating TWAMP Light with TWAMP-Test only).

5. New Well-Known Ports

Originally, both TCP and UDP well-known ports were assigned to the
control protocols that are essential components of standards track Standards Track
OWAMP and TWAMP.

Since OWAMP-Control and TWAMP-Control require TCP transport, they
cannot make use of the UDP ports which that were originally assigned.
However, test sessions using OWAMP-Test or TWAMP-Test operate on UDP
transport.

This memo requests re-assignment of

Per this memo, IANA has reassigned the UDP well-known port from the
Control
control protocol to the Test test protocol (see the IANA Considerations Section 7). Use 7 ("IANA
Considerations")). The use of this UDP port is OPTIONAL in standards-track Standards
Track OWAMP and TWAMP. It may simplify some operations to have a well-
known
well-known port available for the Test protocols, test protocols or for future
specifications involving TWAMP-Test to use this port as a default
port. For example, [TR-390] is a specification for testing at the
customer edge of IP networks, and whose implememntations should
benefit. conforming implementations will
benefit from reallocation of the well-known UDP port to the test
protocol.

5.1. Impact on TWAMP-Control Protocol

Section 3.5 of [RFC5357] describes the detailed process of
negotiating the Receiver Port number, on which the TWAMP
Session-Reflector will send and receive TWAMP-Test packets. packets; see the
quoted text below. The Control-Client, acting on behalf of the
Session-Sender, proposes the Receiver port Port number from the Dynamic Port
Ports range [RFC6335]:

"The

The Receiver Port is the desired UDP port to which TWAMP-Test
packets will be sent by the Session-Sender (the port where the
Session-Reflector is asked to receive test packets). The Receiver
Port is also the UDP port from which TWAMP-Test packets will be
sent by the Session-Reflector (the Session-Reflector will use the
same UDP port to send and receive packets)." packets).

It is possible that the proposed Receiver Port may be not be available,
e.g., the port is in use by another test session or another
application. In this case:

"... case, we update the last paragraph of
Section 3.5 of [RFC5357] per Erratum ID 1587 (see
<https://www.rfc-editor.org/errata/eid1587>) as follows:

... the Server at the Session-Reflector MAY suggest an alternate
and available port for this session in the Port field. The
Control-Client either accepts the alternate port, port or composes a new
Session-Request message with suitable parameters. Otherwise, the
Server uses the Accept field to convey other forms of session
rejection or failure to the Control Client Control-Client and MUST NOT suggest an
alternate port; in this case, the Port field MUST be set to zero." zero.

A Control Client Control-Client that supports the use of the allocated TWAMP-Test
Receiver Port Section 7 (Section 7) MAY request to use that port number in the
Request-TW-Session Command. command. If the Server does not support the
allocated TWAMP-Test Receiver Port, then it sends an alternate port
number in the Accept-Session message with Accept field = 0. Thus Thus,
the deployment of the allocated TWAMP Receiver Port number is
backward compatible with existing TWAMP-Control solutions that are
based on [RFC5357]. Of course, use of using a UDP port number chosen from
the Dynamic Port Ports range [RFC6335] will help to avoid the situation when where
the Control-Client or Server finds that the proposed port being is already
in use.

5.2. Impact on OWAMP-Control Protocol

As described above, an OWAMP Control Client OWAMP-Control client that supports the use of
the allocated OWAMP-Test Receiver Port Section 7 (Section 7) MAY request to use
that port number in the Request-Session Command. command. If the Server does
not support the allocated OWAMP-Test Receiver Port (or does not have
the port available), then it sends an alternate port number in the
Accept-Session message with Accept field = 0. Further exchanges
proceed as already specified.

5.3. Impact on OWAMP/TWAMP-Test OWAMP-Test/TWAMP-Test Protocols

OWAMP/TWAMP-Test

OWAMP-Test/TWAMP-Test may be used to measure IP performance metrics
in an
Equal Cost Equal-Cost Multipath (ECMP) environment. Though algorithms to
balance IP flows among available paths have not been standardized,
the most common is the five-tuple that uses destination IP address,
source IP address, protocol type, destination port number, and source
port number. When attempting to monitor different paths in an ECMP
network, it is sufficient to vary only one of five parameters, e.g. e.g.,
the source port number. Thus, there will be no negative impact on
the ability to arrange concurrent OWAMP/TWAMP test sessions between
the same test points to monitor different paths in the ECMP network
when using the re-allocated reallocated UDP port number as the Receiver Port, as use
of
using the port is optional.

6. Security Considerations

The security considerations that apply to any active measurement of
live paths are relevant here as well (see [RFC4656] and [RFC5357]).

When considering the privacy of those involved in measurement or
those whose traffic is measured, the sensitive information available
to potential observers is greatly reduced when using active
techniques
which that are within this scope of work. Passive observations
of user traffic for measurement purposes raise many privacy issues.
We refer the reader to the security and privacy considerations
described in the Large Scale Large-Scale Measurement of Broadband Performance
(LMAP) Framework framework [RFC7594], which covers both active and passive
techniques.

The registered UDP port as the Receiver Port for OWAMP/TWAMP-Test OWAMP-Test/
TWAMP-Test could become a target of denial-of-service (DoS), denial of service (DoS) or could
be used to aid man-
in-the-middle man-in-the-middle (MITM) attacks. To improve
protection from against DoS, the DoS following methods are recommended:

o filtering access to the OWAMP/TWAMP Receiver Port by via an
access list; list.

o using a non-globally routable IP address for the OWAMP/TWAMP
Session-Reflector address.

A MITM attack attacker may try to modify the content contents of the OWAMP/TWAMP-Test OWAMP-Test/
TWAMP-Test packets in order to alter the measurement results.
However, an implementation can use authenticated mode to detect
modification of data. In addition, an implementation can use
encrypted mode to prevent eavesdropping and
un-detected undetected modification
of the OWAMP/TWAMP-Test OWAMP-Test/TWAMP-Test packets.

There is also a the risk of a network under test giving special
treatment to flows involving the well-known UDP port, with or without
knowing source and destination addresses of measurement systems, and
thus biasing the results through preferential or detrimental
processing.

7. IANA Considerations

This memo requests re-allocation of

IANA has reallocated two UDP port numbers from the System Ports range
of the "Service Name and Transport Protocol Port Number Registry"
[RFC6335]. Specifically, this memo requests that IANA re-allocate has reallocated UDP ports 861 and 862
as shown below, leaving the TCP port assignments as-is:

+------------+-------+---------+----------------------+-------------+ as is. IANA has
also updated the Assignee and Contact for these ports (both UDP and
TCP) to be the IESG and the IETF Chair, respectively.

+---------------+--------+-----------+------------------+-----------+
| Service | Port | Transp. Transport | Description | Reference |
| Name | Num. | Protocol| | |
| | Number | Protocol | | |
+------------+-------+---------+----------------------+-------------+
+---------------+--------+-----------+------------------+-----------+
| owamp- owamp-control | 861 | tcp | OWAMP-Control | [RFC4656] |
| control | | | | RFC 4656 |
| owamp-test | 861 | udp | OWAMP-Test | [RFCXXXX] RFC 8545 |
| | | | Receiver Port | |
| twamp- | 862 | tcp | TWAMP-Control | [RFC5357] |
| control twamp-control | 862 | tcp | TWAMP-Control | RFC 5357 |
| twamp-test | 862 | udp | TWAMP-Test Receiver | [RFCXXXX] RFC 8545 |
| | | | Receiver Port | |
+------------+-------+---------+----------------------+-------------+

Table 1 Re-allocated OWAMP and TWAMP Ports

where RFCXXXX is this memo when published. The Assignee and Contact
should information be updated as follows:

Assignee: IESG

Contact: IETF Chair

11.
+---------------+--------+-----------+------------------+-----------+

8. References

11.1.

8.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.

[RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M.
Zekauskas, "A One-way Active Measurement Protocol
(OWAMP)", RFC 4656, DOI 10.17487/RFC4656, September 2006,
<https://www.rfc-editor.org/info/rfc4656>.

[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, DOI 10.17487/RFC5357, October 2008,
<https://www.rfc-editor.org/info/rfc5357>.

[RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S.
Cheshire, "Internet Assigned Numbers Authority (IANA)
Procedures for the Management of the Service Name and
Transport Protocol Port Number Registry", BCP 165,
RFC 6335, DOI 10.17487/RFC6335, August 2011,
<https://www.rfc-editor.org/info/rfc6335>.

[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,
Aitken, P., and A. Akhter, "A Framework for Large-Scale
Measurement of Broadband Performance (LMAP)", RFC 7594,
DOI 10.17487/RFC7594, September 2015,
<https://www.rfc-editor.org/info/rfc7594>.

[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.

11.2.

8.2. Informative References

[IPPM-TWAMP-06]
Hedayat, K., Krzanowski, R., Yum, K., Morton, A., and J.
Babiarz, "A Two-way Active Measurement Protocol (TWAMP)",
Work in Progress, draft-ietf-ippm-twamp-06, December 2007.

[LarsAD] "https://mailarchive.ietf.org/arch/msg/ippm/
LzcTPYhPhWhbb5-ncR046XKpnzo", Eggert, L., "Subject: [ippm] AD review: draft-ietf-ippm-
twamp-06.txt", message to the ippm mailing list, April 2008.
2008, <https://mailarchive.ietf.org/arch/msg/ippm/
LzcTPYhPhWhbb5-ncR046XKpnzo>.

[TimDISCUSS]
"https://datatracker.ietf.org/doc/rfc5357/history/",
"Tim Polk's Ballot discuss", July
2008. 2008,
<https://datatracker.ietf.org/doc/rfc5357/history>.

[TR-390] "TR-390 Broadband Forum, "TR-390: Performance Measurement from IP
Edge to Custom er Customer Equipment using TWAMP Light, Light", Issue: 1", 1,
May 2017,
<https://www.broadband-forum.org/technical/download/
TR-390.pdf>.

9. <https://www.broadband-
forum.org/technical/download/TR-390.pdf>.

Appendix A A. Background on TWAMP Light

This informative Appendix appendix provides the Background background on the decision to
move the TWAMP Light idea to an informative Appendix appendix in [RFC5357].

The

As also noted in Section 4, the TWAMP Light idea was relegated to the
Appendix I of [RFC5357] because it failed to meet the requirements
for IETF protocols (there are no specifications for negotiating this
form of operation, operation and no specifications for mandatory-to-implement
security features), as described in the references cited below:

o Lars Eggert's Area Director review [LarsAD], where he pointed out
that having two variants of TWAMP, TWAMP (TWAMP Light and Complete (called
standards track TWAMP here), required TWAMP)
requires a protocol mechanism to negotiate which variant will be
used. Note that "Complete TWAMP" is called "Standards Track
TWAMP" in this document. See Lars' Lars's "Section 5.2, paragraph 0"
comment on Sec
5.2. [LarsAD], which refers to a section in [IPPM-TWAMP-06].

The working group consensus was to place the TWAMP Light
description in Appendix I, I and to refer to the Appendix that appendix only as an
"incremental path to adopting TWAMP, by implementing the TWAMP-
Test
TWAMP-Test protocol first". first."

o Tim Polk's DISCUSS Ballot, "Ballot discuss" of 2008-07-16 [TimDISCUSS], which
points out that TWAMP Light was an incomplete specification
because the key required for authenticated and encrypted modes
depended on the TWAMP-Control Session key. See Tim's DISCUSS on 2008-07-16 [TimDISCUSS]. Additional requirement
statements were added in the Appendix I to address Tim's DISCUSS Ballot
discuss (see the last three paragraphs of Appendix I in
[RFC5357]).

Since the idea of TWAMP Light clearly includes the TWAMP-Test
protocol and other undefined facilities, Appendix I of [RFC5357]
simply describes ideas of for how TWAMP-Test might be used ouside outside of
the context of Standards-Track Standards Track TWAMP.

10.

Acknowledgements

The authors thank the IPPM working group Working Group for their rapid review;
thanks also to Muthu Arul Mozhi Perumal and Luay Jalil for their
participation and suggestions.

Contributors

Richard Foote and Luis M. Contreras made notable contributions on
this topic.

Authors' Addresses

Al Morton (editor)
AT&T Labs
200 Laurel Avenue South
Middletown, NJ 07748
USA
United States of America

Phone: +1 732 420 1571
Fax: +1 732 368 1192
Email: acmorton@att.com

Greg Mirsky (editor)
ZTE Corp.

Email: gregimirsky@gmail.com