draft-ietf-ippm-owamp-registry-02.txt | draft-ietf-ippm-owamp-registry-03.txt | |||
---|---|---|---|---|
Network Working Group A. Morton | Network Working Group A. Morton | |||
Internet-Draft AT&T Labs | Internet-Draft AT&T Labs | |||
Updates: 4656 (if approved) August 27, 2015 | Updates: 4656 (if approved) September 11, 2015 | |||
Intended status: Standards Track | Intended status: Standards Track | |||
Expires: February 28, 2016 | Expires: March 14, 2016 | |||
Registries for the One-Way Active Measurement Protocol - OWAMP | Registries for the One-Way Active Measurement Protocol - OWAMP | |||
draft-ietf-ippm-owamp-registry-02 | draft-ietf-ippm-owamp-registry-03 | |||
Abstract | Abstract | |||
This memo describes the registries for OWAMP - the One-Way Active | This memo describes the registries for OWAMP - the One-Way Active | |||
Measurement Protocol. The registries allow assignment of MODE bit | Measurement Protocol. The registries allow assignment of MODE bit | |||
positions and OWAMP Command numbers. The memo also requests that | positions and OWAMP Command numbers. The memo also requests that | |||
IANA establish the registries for new features, called the OWAMP- | IANA establish the registries for new features, called the OWAMP- | |||
Modes registry and the OWAMP Control Command Number registry. This | Modes registry and the OWAMP Control Command Number registry. This | |||
memo updates RFC 4656. | memo updates RFC 4656. | |||
skipping to change at page 1, line 42 | skipping to change at page 1, line 42 | |||
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 February 28, 2016. | This Internet-Draft will expire on March 14, 2016. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 2, line 29 | skipping to change at page 2, line 29 | |||
3. IANA Considerations for OWAMP Control Registries . . . . . . 3 | 3. IANA Considerations for OWAMP Control Registries . . . . . . 3 | |||
3.1. Control Command Number Registry . . . . . . . . . . . . . 3 | 3.1. Control Command Number Registry . . . . . . . . . . . . . 3 | |||
3.1.1. Registry Specification . . . . . . . . . . . . . . . 3 | 3.1.1. Registry Specification . . . . . . . . . . . . . . . 3 | |||
3.1.2. Registry Management . . . . . . . . . . . . . . . . . 3 | 3.1.2. Registry Management . . . . . . . . . . . . . . . . . 3 | |||
3.1.3. Experimental Numbers . . . . . . . . . . . . . . . . 3 | 3.1.3. Experimental Numbers . . . . . . . . . . . . . . . . 3 | |||
3.1.4. OWAMP-Control Command Numbers Initial Contents . . . 3 | 3.1.4. OWAMP-Control Command Numbers Initial Contents . . . 3 | |||
3.2. OWAMP-Modes . . . . . . . . . . . . . . . . . . . . . . . 4 | 3.2. OWAMP-Modes . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
3.2.1. Registry Specification . . . . . . . . . . . . . . . 4 | 3.2.1. Registry Specification . . . . . . . . . . . . . . . 4 | |||
3.2.2. Registry Management . . . . . . . . . . . . . . . . . 4 | 3.2.2. Registry Management . . . . . . . . . . . . . . . . . 4 | |||
3.2.3. Experimental Numbers . . . . . . . . . . . . . . . . 4 | 3.2.3. Experimental Numbers . . . . . . . . . . . . . . . . 4 | |||
3.2.4. OWAMP-Modes Initial Contents . . . . . . . . . . . . 4 | 3.2.4. OWAMP-Modes Initial Contents . . . . . . . . . . . . 5 | |||
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 | 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 | |||
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
6.1. Normative References . . . . . . . . . . . . . . . . . . 6 | 6.1. Normative References . . . . . . . . . . . . . . . . . . 6 | |||
6.2. Informative References . . . . . . . . . . . . . . . . . 7 | 6.2. Informative References . . . . . . . . . . . . . . . . . 7 | |||
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
1. Introduction | 1. Introduction | |||
The One-way Active Measurement Protocol, OWAMP [RFC4656] was prepared | The One-way Active Measurement Protocol, OWAMP [RFC4656] was prepared | |||
skipping to change at page 3, line 9 | skipping to change at page 3, line 9 | |||
TWAMP. However, there were no new features proposed for OWAMP until | TWAMP. However, there were no new features proposed for OWAMP until | |||
recently [I-D.ietf-ippm-ipsec]. | recently [I-D.ietf-ippm-ipsec]. | |||
This memo establishes the needed registries for OWAMP, and updates | This memo establishes the needed registries for OWAMP, and updates | |||
[RFC4656]. | [RFC4656]. | |||
2. Purpose and Scope | 2. Purpose and Scope | |||
The purpose and scope of this memo is to describe and request the | The purpose and scope of this memo is to describe and request the | |||
establishment of registries for future OWAMP [RFC4656] extensions. | establishment of registries for future OWAMP [RFC4656] extensions. | |||
IANA already administrates the "Two-way Active Measurement Protocol | IANA already administers the "Two-way Active Measurement Protocol | |||
(TWAMP) Parameters", and this request follows a similar form (with | (TWAMP) Parameters", and this request follows a similar form (with | |||
one exception identified below). | one exception identified below). | |||
This memo also provides the initial contents for the OWAMP | This memo also provides the initial contents for the OWAMP | |||
registries. | registries. | |||
3. IANA Considerations for OWAMP Control Registries | 3. IANA Considerations for OWAMP Control Registries | |||
OWAMP-Control protocol coordinates the measurement capability. All | OWAMP-Control protocol coordinates the measurement capability. All | |||
OWAMP-Control messages follow specifications defined in section 3 of | OWAMP-Control messages follow specifications defined in section 3 of | |||
[RFC4656]. | [RFC4656]. | |||
3.1. Control Command Number Registry | 3.1. Control Command Number Registry | |||
IANA is requested to create a OWAMP-Control Command Number registry. | IANA is requested to create an OWAMP-Control Command Number registry. | |||
OWAMP-Control Commands follow specifications defined in section 3.4 | OWAMP-Control Commands follow specifications defined in section 3.4 | |||
of [RFC4656]. | of [RFC4656]. | |||
3.1.1. Registry Specification | 3.1.1. Registry Specification | |||
OWAMP-Control Commands Numbers are specified in the first octet of | OWAMP-Control Command Numbers are specified in the first octet of | |||
OWAMP-Control-Client command messages consistent with section 3 of | OWAMP-Control-Client command messages consistent with section 3 of | |||
[RFC4656]. There are a maximum of 256 command numbers. | [RFC4656]. There are a maximum of 256 command numbers. | |||
3.1.2. Registry Management | 3.1.2. Registry Management | |||
Because the "OWAMP-Control Command Numbers" registry can contain only | Because the "OWAMP-Control Command Numbers" registry can contain only | |||
256 values, and because OWAMP is an IETF protocol, these registries | 256 values, and because OWAMP is an IETF protocol, these registries | |||
MUST be updated only by "IETF Consensus" as specified in [RFC5226] | MUST be updated only by "IETF Review" as specified in [RFC5226] (an | |||
(an RFC that documents registry use and is approved by the IESG). | RFC that documents registry use and is approved by the IESG). | |||
3.1.3. Experimental Numbers | 3.1.3. Experimental Numbers | |||
One experimental value is currently assigned in the Command Numbers | One experimental value is currently assigned in the Command Numbers | |||
Registry, as indicated in the initial contents below. | Registry, as indicated in the initial contents below. | |||
3.1.4. OWAMP-Control Command Numbers Initial Contents | 3.1.4. OWAMP-Control Command Numbers Initial Contents | |||
OWAMP-Control Commands follows the procedure defined in section 3.5 | OWAMP-Control Commands follows the procedure defined in section 3.5 | |||
of [RFC4656] (and in the remainder of section 3). | of [RFC4656] (and in the remainder of section 3). | |||
skipping to change at page 4, line 19 | skipping to change at page 4, line 19 | |||
Value Description Semantics Reference | Value Description Semantics Reference | |||
Definition | Definition | |||
========================================================== | ========================================================== | |||
0 Reserved | 0 Reserved | |||
1 Request-Session Section 3.5 RFC 4656 | 1 Request-Session Section 3.5 RFC 4656 | |||
2 Start-Sessions Section 3.7 RFC 4656 | 2 Start-Sessions Section 3.7 RFC 4656 | |||
3 Stop-Sessions Section 3.8 RFC 4656 | 3 Stop-Sessions Section 3.8 RFC 4656 | |||
4 Fetch-Sessions Section 3.9 RFC 4656 | 4 Fetch-Sessions Section 3.9 RFC 4656 | |||
5-253 Unassigned | 5-253 Unassigned | |||
254 Experimentation This Memo | 254 Experimentation Section 3.1.4 This Memo | |||
255 Reserved | 255 Reserved | |||
where "This Memo" is the published version of draft-ietf-ippm-owamp- | ||||
registry | ||||
3.2. OWAMP-Modes | 3.2. OWAMP-Modes | |||
IANA is requested to create an OWAMP-Modes registry. | IANA is requested to create an OWAMP-Modes registry. | |||
3.2.1. Registry Specification | 3.2.1. Registry Specification | |||
OWAMP-Modes are specified in OWAMP Server Greeting messages and Set- | OWAMP-Modes are specified in OWAMP Server Greeting messages and Set- | |||
up Response messages consistent with section 3.1 of [RFC4656]. Modes | up Response messages consistent with section 3.1 of [RFC4656]. Modes | |||
are currently indicated by setting single bits in the 32-bit Modes | are currently indicated by setting single bits in the 32-bit Modes | |||
Field. However, more complex encoding may be used in the future. | Field. However, more complex encoding may be used in the future. | |||
3.2.2. Registry Management | 3.2.2. Registry Management | |||
Because the "OWAMP-Modes" are based on only 32 bit positions with | Because the "OWAMP-Modes" are based on only 32 bit positions with | |||
each position conveying a unique feature, and because OWAMP is an | each position conveying a unique feature, and because OWAMP is an | |||
IETF protocol, these registries MUST be updated only by "IETF | IETF protocol, these registries MUST be updated only by "IETF Review" | |||
Consensus" as specified in [RFC5226] (an RFC that documents registry | as specified in [RFC5226] (an RFC that documents registry use and is | |||
use and is approved by the IESG). IANA SHOULD allocate monotonically | approved by the IESG). IANA SHOULD allocate monotonically increasing | |||
increasing bit positions when requested. | bit positions when requested. | |||
3.2.3. Experimental Numbers | 3.2.3. Experimental Numbers | |||
No experimental bit positions are currently assigned in the Modes | No experimental bit positions are currently assigned in the Modes | |||
Registry, as indicated in the initial contents below. | Registry, as indicated in the initial contents below. | |||
3.2.4. OWAMP-Modes Initial Contents | 3.2.4. OWAMP-Modes Initial Contents | |||
OWAMP-Control connection establishment follows the procedure defined | OWAMP-Control connection establishment follows the procedure defined | |||
in section 3.1 of [RFC4656]. | in section 3.1 of [RFC4656]. | |||
skipping to change at page 5, line 18 | skipping to change at page 5, line 23 | |||
improvement in the TWAMP-Modes registry which is reconciled in | improvement in the TWAMP-Modes registry which is reconciled in | |||
[I-D.ietf-ippm-ipsec]). | [I-D.ietf-ippm-ipsec]). | |||
An Extension of the OWAMP-Modes is proposed in [I-D.ietf-ippm-ipsec]. | An Extension of the OWAMP-Modes is proposed in [I-D.ietf-ippm-ipsec]. | |||
With this extension, the complete set of OWAMP Mode bit positions are | With this extension, the complete set of OWAMP Mode bit positions are | |||
as follows (including one reserved bit position): | as follows (including one reserved bit position): | |||
OWAMP-Modes Registry | OWAMP-Modes Registry | |||
Bit Semantics | Bit Semantics | |||
Pos. Description Definition Reference | Pos. Description Definition Reference | |||
===================================================== | ===================================================== | |||
0 Unauthenticated Section 3.1 RFC4656 | 0 Unauthenticated Section 3.1 RFC4656 | |||
1 Authenticated Section 3.1 RFC4656 | 1 Authenticated Section 3.1 RFC4656 | |||
2 Encrypted Section 3.1 RFC4656 | 2 Encrypted Section 3.1 RFC4656 | |||
3 Reserved this memo | 3 Reserved Section 3.2.4 This Memo | |||
4 IKEv2-derived Shared this memo and | ------------------------------------------------------ | |||
Secret Key Section 5 RFC_TBD | 4 IKEv2-derived Shared Section 3.2.4 This Memo | |||
Secret Key and Section 5 RFC-to-be | ||||
------------------------------------------------------ | ||||
5-31 Unassigned | 5-31 Unassigned | |||
(where RFC_TBD the published version of draft-ietf-ippm-ipsec) | (where RFC-to-be is the published version of draft-ietf-ippm-ipsec, | |||
and where "This Memo" is draft-ietf-ippm-owamp-registry ) | ||||
In the original OWAMP Modes field, setting bit position 0, 1 or 2 | In the original OWAMP Modes field, setting bit position 0, 1 or 2 | |||
indicated the security mode of the Control protocol, and the Test | indicated the security mode of the Control protocol, and the Test | |||
protocol inherited the same mode (see section 4 of [RFC4656]). | protocol inherited the same mode (see section 4 of [RFC4656]). | |||
The value of the Modes Field sent by the Server in the Server- | The value of the Modes Field sent by the Server in the Server- | |||
Greeting message is the bit-wise OR of the modes (bit positions) that | Greeting message is the bit-wise OR of the modes (bit positions) that | |||
it is willing to support during this session. Thus, the five least | it is willing to support during this session. Thus, the five least | |||
significant bits of the Modes 32-bit Field are used. When no other | significant bits of the Modes 32-bit Field are used. When no other | |||
features are activated, the 27 most significant bits MUST be zero. A | features are activated, the 27 most significant bits MUST be zero. A | |||
skipping to change at page 6, line 22 | skipping to change at page 6, line 30 | |||
[RFC5357]. | [RFC5357]. | |||
Privacy considerations for measurement systems, particularly when | Privacy considerations for measurement systems, particularly when | |||
Internet users participate in the tests in some way, are described in | Internet users participate in the tests in some way, are described in | |||
[I-D.ietf-lmap-framework]. | [I-D.ietf-lmap-framework]. | |||
5. Acknowledgements | 5. Acknowledgements | |||
The author would like to thank Kostas Pentikousis, Nalini Elkins, | The author would like to thank Kostas Pentikousis, Nalini Elkins, | |||
Mike Ackermann, and Greg Mirsky for insightful reviews and comments. | Mike Ackermann, and Greg Mirsky for insightful reviews and comments. | |||
Spencer Dawkins caught the last of the small errors (hopefully) in | We thought Spencer Dawkins caught the last of the small errors in his | |||
his AD review. | AD review, but Nevil Brownlee found a few more during OPS-DIR review. | |||
Roni Even found our use of "IETF Consensus" was out of date with | ||||
[RFC5226]. Michelle Cotton helped to clarify the IANA | ||||
considerations. | ||||
6. References | 6. References | |||
6.1. Normative References | 6.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, | Requirement Levels", BCP 14, RFC 2119, | |||
DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
<http://www.rfc-editor.org/info/rfc2119>. | <http://www.rfc-editor.org/info/rfc2119>. | |||
End of changes. 16 change blocks. | ||||
25 lines changed or deleted | 34 lines changed or added | |||
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |