Well-Known Port Assignments for the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP)
RFC 8545
Internet Engineering Task Force (IETF) A. Morton, Ed.
Request for Comments: 8545 AT&T Labs
Updates: 4656, 5357 G. Mirsky, Ed.
Category: Standards Track ZTE Corp.
ISSN: 2070-1721 March 2019
Well-Known Port Assignments 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 reassignment of
well-known ports for the One-Way Active Measurement Protocol (OWAMP)
and the Two-Way Active Measurement Protocol (TWAMP) for control and
measurement. It also clarifies the meaning and composition of these
Standards Track protocol names for the industry.
This memo updates RFCs 4656 and 5357, in terms of the UDP well-known
port assignments, and it clarifies the complete OWAMP and TWAMP
protocol composition for the industry.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8545.
Morton & Mirsky Standards Track [Page 1]
RFC 8545 OWAMP/TWAMP Well-Known Ports March 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
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 ....................................................3
2. Requirements Language ...........................................3
3. Scope ...........................................................3
4. Definitions and Background ......................................3
5. New Well-Known Ports ............................................5
5.1. Impact on TWAMP-Control Protocol ...........................5
5.2. Impact on OWAMP-Control Protocol ...........................6
5.3. Impact on OWAMP-Test/TWAMP-Test Protocols ..................6
6. Security Considerations .........................................7
7. IANA Considerations .............................................8
8. References ......................................................8
8.1. Normative References .......................................8
8.2. Informative References .....................................9
Appendix A. Background on TWAMP Light .............................10
Acknowledgements ..................................................11
Contributors ......................................................11
Authors' Addresses ................................................11
Morton & Mirsky Standards Track [Page 2]
RFC 8545 OWAMP/TWAMP Well-Known Ports March 2019
1. Introduction
The IETF IP Performance Metrics (IPPM) Working Group first developed
the One-Way Active Measurement Protocol (OWAMP), as specified in
[RFC4656]. Further protocol development to support testing resulted
in the Two-Way Active Measurement 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) 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.
The IETF recognizes the value of assigning a well-known UDP port to
the OWAMP-Test and TWAMP-Test protocols and also recognizes that this
goal can be easily arranged through port reassignments.
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Show full document text