draft-ietf-ippm-owamp-registry-01.txt | draft-ietf-ippm-owamp-registry-02.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 26, 2015 | Updates: 4656 (if approved) August 27, 2015 | |||
Intended status: Standards Track | Intended status: Standards Track | |||
Expires: February 27, 2016 | Expires: February 28, 2016 | |||
Registries for the One-Way Active Measurement Protocol - OWAMP | Registries for the One-Way Active Measurement Protocol - OWAMP | |||
draft-ietf-ippm-owamp-registry-01 | draft-ietf-ippm-owamp-registry-02 | |||
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 27, 2016. | This Internet-Draft will expire on February 28, 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 | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
This document may contain material from IETF Documents or IETF | ||||
Contributions published or made publicly available before November | ||||
10, 2008. The person(s) controlling the copyright in some of this | ||||
material may not have granted the IETF Trust the right to allow | ||||
modifications of such material outside the IETF Standards Process. | ||||
Without obtaining an adequate license from the person(s) controlling | ||||
the copyright in such materials, this document may not be modified | ||||
outside the IETF Standards Process, and derivative works of it may | ||||
not be created outside the IETF Standards Process, except to format | ||||
it for publication as an RFC or to translate it into languages other | ||||
than English. | ||||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3 | |||
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 . . . . . . . . . . . . . . . . . 4 | 3.1.2. Registry Management . . . . . . . . . . . . . . . . . 3 | |||
3.1.3. Experimental Numbers . . . . . . . . . . . . . . . . 4 | 3.1.3. Experimental Numbers . . . . . . . . . . . . . . . . 3 | |||
3.1.4. OWAMP-Control Command Numbers Initial Contents . . . 4 | 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 . . . . . . . . . . . . . . . . . 5 | 3.2.2. Registry Management . . . . . . . . . . . . . . . . . 4 | |||
3.2.3. Experimental Numbers . . . . . . . . . . . . . . . . 5 | 3.2.3. Experimental Numbers . . . . . . . . . . . . . . . . 4 | |||
3.2.4. OWAMP-Modes Initial Contents . . . . . . . . . . . . 5 | 3.2.4. OWAMP-Modes Initial Contents . . . . . . . . . . . . 4 | |||
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 4, line 23 | skipping to change at page 4, line 6 | |||
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). | |||
The complete set of OWAMP-Control Command Numbers are as follows | The complete set of OWAMP-Control Command Numbers are as follows | |||
(including one reserved bit position): | (including two reserved values): | |||
OWAMP-Control Command Numbers Registry | OWAMP-Control Command Numbers Registry | |||
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 | |||
skipping to change at page 6, line 40 | skipping to change at page 6, line 22 | |||
[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 | ||||
his AD review. | ||||
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. 10 change blocks. | ||||
24 lines changed or deleted | 14 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/ |