1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Internet Engineering Task Force (IETF) A. Morton
Request for Comments: 7718 AT&T Labs
Updates: <a href="./rfc4656">4656</a> December 2015
Category: Standards Track
ISSN: 2070-1721
<span class="h1">Registries for the One-Way Active Measurement Protocol (OWAMP)</span>
Abstract
This memo describes the registries for OWAMP -- the One-Way Active
Measurement Protocol. The registries allow assignment of Mode bit
positions and OWAMP Command numbers. Per this memo, IANA has
established the registries for new features, called the OWAMP-Modes
registry and the OWAMP Control Command Number registry. This memo
updates <a href="./rfc4656">RFC 4656</a>.
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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7718">http://www.rfc-editor.org/info/rfc7718</a>.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Morton Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7718">RFC 7718</a> OWAMP Registries December 2015</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Requirements Language . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. IANA Considerations for OWAMP-Control Registries . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Control Command Number Registry . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1.1">3.1.1</a>. Registry Specification . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1.2">3.1.2</a>. Registry Management . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1.3">3.1.3</a>. Experimental Numbers . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1.4">3.1.4</a>. OWAMP-Control Command Numbers Initial Contents . . . <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a>. OWAMP-Modes . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.2.1">3.2.1</a>. Registry Specification . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.2.2">3.2.2</a>. Registry Management . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.2.3">3.2.3</a>. Experimental Numbers . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.2.4">3.2.4</a>. OWAMP-Modes Initial Contents . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5.1">5.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5.2">5.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The One-Way Active Measurement Protocol (OWAMP) [<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>] was
prepared to support measurements of metrics specified by the IP
Performance Metrics (IPPM) working group in the IETF. The Two-Way
Active Measurement Protocol (TWAMP) [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>] is an extension of
OWAMP. The TWAMP specification gathered wide review as it approached
completion, and the by-products were several recommendations for new
features in TWAMP. As a result, a registry of new features was
established for TWAMP. However, there were no new features proposed
for OWAMP until recently [<a href="./rfc7717" title=""IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)"">RFC7717</a>].
This memo establishes the needed registries for OWAMP and updates
[<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>].
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Morton Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7718">RFC 7718</a> OWAMP Registries December 2015</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Purpose and Scope</span>
The purpose and scope of this memo is to describe and request the
establishment of registries for future OWAMP [<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>] extensions.
IANA already administers the "Two-way Active Measurement Protocol
(TWAMP) Parameters", and this request follows a similar form (with
one exception identified below).
This memo also provides the initial contents for the OWAMP
registries.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations for OWAMP-Control Registries</span>
The OWAMP-Control protocol coordinates the measurement capability.
All OWAMP-Control messages follow specifications defined in <a href="./rfc4656#section-3">Section 3
of [RFC4656]</a>.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Control Command Number Registry</span>
IANA has created an OWAMP-Control Command Number registry.
OWAMP-Control Commands follow specifications defined in <a href="./rfc4656#section-3.4">Section 3.4
of [RFC4656]</a>.
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Registry Specification</span>
OWAMP-Control Command Numbers are specified in the first octet of
OWAMP-Control-Client command messages consistent with <a href="./rfc4656#section-3">Section 3 of
[RFC4656]</a>. There are a maximum of 256 command numbers.
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Registry Management</span>
Because the "OWAMP-Control Command Numbers" registry can contain only
256 values, and because OWAMP is an IETF protocol, these registries
MUST be updated only by "IETF Review" as specified in [<a href="./rfc5226" title="">RFC5226</a>] (an
RFC that documents registry use and is approved by the IESG).
<span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>. Experimental Numbers</span>
One experimental value is currently assigned in the Command Numbers
Registry, as indicated in the initial contents below.
<span class="h4"><a class="selflink" id="section-3.1.4" href="#section-3.1.4">3.1.4</a>. OWAMP-Control Command Numbers Initial Contents</span>
OWAMP-Control Commands follows the procedure defined in <a href="./rfc4656#section-3.5">Section 3.5
of [RFC4656]</a> and in the remainder of <a href="#section-3">Section 3</a> of that document.
<span class="grey">Morton Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7718">RFC 7718</a> OWAMP Registries December 2015</span>
The complete set of OWAMP-Control Command Numbers are as follows
(including two reserved values):
OWAMP-Control Command Numbers
Value Description Semantics Reference
Definition
==========================================================
0 Reserved <a href="#section-3.1.4">Section 3.1.4</a> <a href="./rfc7718">RFC 7718</a>
1 Request-Session <a href="#section-3.5">Section 3.5</a> <a href="./rfc4656">RFC 4656</a>
2 Start-Sessions <a href="#section-3.7">Section 3.7</a> <a href="./rfc4656">RFC 4656</a>
3 Stop-Sessions <a href="#section-3.8">Section 3.8</a> <a href="./rfc4656">RFC 4656</a>
4 Fetch-Sessions <a href="#section-3.9">Section 3.9</a> <a href="./rfc4656">RFC 4656</a>
5-253 Unassigned
254 Experimentation <a href="#section-3.1.4">Section 3.1.4</a> <a href="./rfc7718">RFC 7718</a>
255 Reserved <a href="#section-3.1.4">Section 3.1.4</a> <a href="./rfc7718">RFC 7718</a>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. OWAMP-Modes</span>
IANA has created an OWAMP-Modes registry.
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Registry Specification</span>
OWAMP-Modes are specified in OWAMP Server Greeting messages and Set-
up Response messages consistent with <a href="./rfc4656#section-3.1">Section 3.1 of [RFC4656]</a>. Modes
are currently indicated by setting single bits in the 32-bit Modes
field. However, more complex encoding may be used in the future.
<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Registry Management</span>
Because the "OWAMP-Modes" are based on only 32 bit positions with
each position conveying a unique feature, and because OWAMP is an
IETF protocol, these registries MUST be updated only by "IETF Review"
as specified in [<a href="./rfc5226" title="">RFC5226</a>] (an RFC that documents registry use and is
approved by the IESG). IANA SHOULD allocate monotonically increasing
bit positions when requested.
<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. Experimental Numbers</span>
No experimental bit positions are currently assigned in the Modes
registry, as indicated in the initial contents below.
<span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. OWAMP-Modes Initial Contents</span>
OWAMP-Control connection establishment follows the procedure defined
in <a href="./rfc4656#section-3.1">Section 3.1 of [RFC4656]</a>.
<span class="grey">Morton Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7718">RFC 7718</a> OWAMP Registries December 2015</span>
In the OWAMP-Modes registry, assignments are straightforward on the
basis of bit positions, and there are no references to values -- this
is a difference from the comparable TWAMP registry (and a topic for
improvement in the TWAMP-Modes registry that is reconciled in
[<a href="./rfc7717" title=""IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)"">RFC7717</a>]).
An extension of the OWAMP-Modes is proposed in [<a href="./rfc7717" title=""IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)"">RFC7717</a>]. With this
extension, the complete set of OWAMP Mode bit positions are as
follows (including one reserved bit position):
OWAMP-Modes
Bit Semantics
Pos. Description Definition Reference
=======================================================
0 Unauthenticated <a href="#section-3.1">Section 3.1</a> <a href="./rfc4656">RFC 4656</a>
1 Authenticated <a href="#section-3.1">Section 3.1</a> <a href="./rfc4656">RFC 4656</a>
2 Encrypted <a href="#section-3.1">Section 3.1</a> <a href="./rfc4656">RFC 4656</a>
3 Reserved <a href="#section-3.2.4">Section 3.2.4</a> <a href="./rfc7718">RFC 7718</a>
------------------------------------------------------
4 IKEv2-derived Shared <a href="#section-3.2.4">Section 3.2.4</a> <a href="./rfc7718">RFC 7718</a>
Secret Key of <a href="./rfc7718./rfc7717#section-5">RFC 7718,
Section 5 of RFC 7717</a>
of <a href="./rfc7717">RFC 7717</a>
------------------------------------------------------
5-31 Unassigned
In the original OWAMP Modes field, setting bit position 0, 1, or 2
indicated the security mode of the Control protocol, and the Test
protocol inherited the same mode (see <a href="./rfc4656#section-4">Section 4 of [RFC4656]</a>).
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
it is willing to support during this session. Thus, the five least
significant bits of the 32-bit Modes field are used. When no other
features are activated, the 27 most significant bits MUST be zero. A
Control-Client conforming to [<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>] MAY ignore the values in the
29 most significant bits of the Modes field, or it MAY support
features that are communicated in other bit positions, such as the
IKEv2-derived Shared Secret Key extension [<a href="./rfc7717" title=""IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)"">RFC7717</a>].
OWAMP and TWAMP registries for Modes may grow to contain different
features and functions due to the inherent differences in one-way and
two-way measurement configurations and the metrics they measure. No
attempt will be made to coordinate them unnecessarily, except for the
Reserved bit position 3 above. This is available for assignment if a
mixed security mode similar to [<a href="./rfc5618" title=""Mixed Security Mode for the Two-Way Active Measurement Protocol (TWAMP)"">RFC5618</a>] is defined for OWAMP; it
would allow alignment with the comparable TWAMP feature.
<span class="grey">Morton Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7718">RFC 7718</a> OWAMP Registries December 2015</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
As this memo simply documents the creation of OWAMP registries, it
presents no new security or privacy issues for the Internet.
The security considerations that apply to any active measurement of
live networks are relevant here as well. See [<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>] and
[<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>].
Privacy considerations for measurement systems, particularly when
Internet users participate in the tests in some way, are described in
[<a href="./rfc7594" title=""A Framework for Large-Scale Measurement of Broadband Performance (LMAP)"">RFC7594</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC4656">RFC4656</a>] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M.
Zekauskas, "A One-way Active Measurement Protocol
(OWAMP)", <a href="./rfc4656">RFC 4656</a>, DOI 10.17487/RFC4656, September 2006,
<<a href="http://www.rfc-editor.org/info/rfc4656">http://www.rfc-editor.org/info/rfc4656</a>>.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
DOI 10.17487/RFC5226, May 2008,
<<a href="http://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>>.
[<a id="ref-RFC5357">RFC5357</a>] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
<a href="./rfc5357">RFC 5357</a>, DOI 10.17487/RFC5357, October 2008,
<<a href="http://www.rfc-editor.org/info/rfc5357">http://www.rfc-editor.org/info/rfc5357</a>>.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-RFC5618">RFC5618</a>] Morton, A. and K. Hedayat, "Mixed Security Mode for the
Two-Way Active Measurement Protocol (TWAMP)", <a href="./rfc5618">RFC 5618</a>,
DOI 10.17487/RFC5618, August 2009,
<<a href="http://www.rfc-editor.org/info/rfc5618">http://www.rfc-editor.org/info/rfc5618</a>>.
<span class="grey">Morton Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7718">RFC 7718</a> OWAMP Registries December 2015</span>
[<a id="ref-RFC7594">RFC7594</a>] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,
Aitken, P., and A. Akhter, "A Framework for Large-Scale
Measurement of Broadband Performance (LMAP)", <a href="./rfc7594">RFC 7594</a>,
DOI 10.17487/RFC7594, September 2015,
<<a href="http://www.rfc-editor.org/info/rfc7594">http://www.rfc-editor.org/info/rfc7594</a>>.
[<a id="ref-RFC7717">RFC7717</a>] Pentikousis, K., Ed., Zhang, E., and Y. Cui,
"IKEv2-Derived Shared Secret Key for the One-Way Active
Measurement Protocol (OWAMP) and Two-Way Active
Measurement Protocol (TWAMP)", <a href="./rfc7717">RFC 7717</a>,
DOI 10.17487/RFC7717, December 2015,
<<a href="http://www.rfc-editor.org/info/rfc7717">http://www.rfc-editor.org/info/rfc7717</a>>.
Acknowledgements
The author would like to thank Kostas Pentikousis, Nalini Elkins,
Mike Ackermann, and Greg Mirsky for insightful reviews and comments.
We thought Spencer Dawkins caught the last of the small errors in his
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
[<a href="./rfc5226" title="">RFC5226</a>]. Michelle Cotton helped to clarify the IANA
considerations.
Author's Address
Al Morton
AT&T Labs
200 Laurel Avenue South
Middletown,, NJ 07748
United States
Phone: +1 732 420 1571
Fax: +1 732 368 1192
Email: acmorton@att.com
URI: <a href="http://home.comcast.net/~acmacm/">http://home.comcast.net/~acmacm/</a>
Morton Standards Track [Page 7]
</pre>
|
