Debian Codegraph @

rfc6222.html

raw
1 <pre>Internet Engineering Task Force (IETF) A. Begen
2 Request for Comments: 6222 Cisco
3 Updates: <a href="./rfc3550">3550</a> C. Perkins
4 Category: Standards Track University of Glasgow
5 ISSN: 2070-1721 D. Wing
6 Cisco
7 April 2011
8
9
10 <span class="h1">Guidelines for Choosing RTP Control Protocol (RTCP)</span>
11 <span class="h1">Canonical Names (CNAMEs)</span>
12
13 Abstract
14
15 The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a
16 persistent transport-level identifier for an RTP endpoint. While the
17 Synchronization Source (SSRC) identifier of an RTP endpoint may
18 change if a collision is detected or when the RTP application is
19 restarted, its RTCP CNAME is meant to stay unchanged, so that RTP
20 endpoints can be uniquely identified and associated with their RTP
21 media streams. For proper functionality, RTCP CNAMEs should be
22 unique within the participants of an RTP session. However, the
23 existing guidelines for choosing the RTCP CNAME provided in the RTP
24 standard are insufficient to achieve this uniqueness. This memo
25 updates those guidelines to allow endpoints to choose unique RTCP
26 CNAMEs.
27
28 Status of This Memo
29
30 This is an Internet Standards Track document.
31
32 This document is a product of the Internet Engineering Task Force
33 (IETF). It represents the consensus of the IETF community. It has
34 received public review and has been approved for publication by the
35 Internet Engineering Steering Group (IESG). Further information on
36 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
37
38 Information about the current status of this document, any errata,
39 and how to provide feedback on it may be obtained at
40 <a href="http://www.rfc-editor.org/info/rfc6222">http://www.rfc-editor.org/info/rfc6222</a>.
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Begen, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2011 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
75 <a href="#section-2">2</a>. Requirements Notation ...........................................<a href="#page-2">2</a>
76 3. Deficiencies with Earlier Guidelines for Choosing an
77 RTCP CNAME ......................................................<a href="#page-3">3</a>
78 <a href="#section-4">4</a>. Choosing an RTCP CNAME ..........................................<a href="#page-3">3</a>
79 <a href="#section-4.1">4.1</a>. Persistent RTCP CNAMEs versus Per-Session RTCP CNAMEs ......<a href="#page-4">4</a>
80 <a href="#section-4.2">4.2</a>. Requirements ...............................................<a href="#page-5">5</a>
81 <a href="#section-5">5</a>. Procedure to Generate a Unique Identifier .......................<a href="#page-6">6</a>
82 <a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-7">7</a>
83 <a href="#section-6.1">6.1</a>. Considerations on Uniqueness of RTCP CNAMEs ................<a href="#page-7">7</a>
84 <a href="#section-6.2">6.2</a>. Session Correlation Based on RTCP CNAMEs ...................<a href="#page-7">7</a>
85 <a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-8">8</a>
86 <a href="#section-8">8</a>. References ......................................................<a href="#page-8">8</a>
87 <a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-8">8</a>
88 <a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-9">9</a>
89
90 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
91
92 In <a href="#section-6.5.1">Section 6.5.1</a> of the RTP specification, [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], there are a
93 number of recommendations for choosing a unique RTCP CNAME for an RTP
94 endpoint. However, in practice, some of these methods are not
95 guaranteed to produce a unique RTCP CNAME. This memo updates
96 guidelines for choosing RTCP CNAMEs, superseding those presented in
97 <a href="./rfc3550#section-6.5.1">Section&nbsp;6.5.1 of [RFC3550]</a>.
98
99 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Notation</span>
100
101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
103 "OPTIONAL" in this document are to be interpreted as described in
104 [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
105
106
107
108 <span class="grey">Begen, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Deficiencies with Earlier Guidelines for Choosing an RTCP CNAME</span>
114
115 The recommendation in [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] is to generate an RTCP CNAME of the
116 form "user@host" for multiuser systems, or "host" if the username is
117 not available. The "host" part is specified to be the fully
118 qualified domain name (FQDN) of the host from which the real-time
119 data originates. While this guidance was appropriate at the time
120 [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] was written, FQDNs are no longer necessarily unique and can
121 sometimes be common across several endpoints in large service
122 provider networks. This document replaces the use of FQDN as an RTCP
123 CNAME by alternative mechanisms.
124
125 IPv4 addresses are also suggested for use in RTCP CNAMEs in
126 [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], where the "host" part of the RTCP CNAME is the numeric
127 representation of the IPv4 address of the interface from which the
128 RTP data originates. As noted in [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], the use of private
129 network address space [<a href="./rfc1918" title="&quot;Address Allocation for Private Internets&quot;">RFC1918</a>] can result in hosts having network
130 addresses that are not globally unique. Additionally, this shared
131 use of the same IPv4 address can also occur with public IPv4
132 addresses if multiple hosts are assigned the same public IPv4 address
133 and connected to a Network Address Translation (NAT) device
134 [<a href="./rfc3022" title="&quot;Traditional IP Network Address Translator (Traditional NAT)&quot;">RFC3022</a>]. When multiple hosts share the same IPv4 address, whether
135 private or public, using the IPv4 address as the RTCP CNAME leads to
136 RTCP CNAMEs that are not necessarily unique.
137
138 It is also noted in [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] that if hosts with private addresses
139 and no direct IP connectivity to the public Internet have their RTP
140 packets forwarded to the public Internet through an RTP-level
141 translator, they could end up having non-unique RTCP CNAMEs. The
142 suggestion in [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] is that such applications provide a
143 configuration option to allow the user to choose a unique RTCP CNAME;
144 this technique puts the burden on the translator to translate RTCP
145 CNAMEs from private addresses to public addresses if necessary to
146 keep private addresses from being exposed. Experience has shown that
147 this does not work well in practice.
148
149 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Choosing an RTCP CNAME</span>
150
151 It is difficult, and in some cases impossible, for a host to
152 determine if there is a NAT between itself and its RTP peer.
153 Furthermore, even some public IPv4 addresses can be shared by
154 multiple hosts in the Internet. Using the numeric representation of
155 the IPv4 address as the "host" part of the RTCP CNAME is NOT
156 RECOMMENDED.
157
158
159
160
161
162
163
164 <span class="grey">Begen, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
167
168
169 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Persistent RTCP CNAMEs versus Per-Session RTCP CNAMEs</span>
170
171 The RTCP CNAME can be either persistent across different RTP sessions
172 for an RTP endpoint or unique per session, meaning that an RTP
173 endpoint chooses a different RTCP CNAME for each RTP session.
174
175 An RTP endpoint that is emitting multiple related RTP streams that
176 require synchronization at the other endpoint(s) MUST use the same
177 RTCP CNAME for all streams that are to be synchronized. This
178 requires a short-term persistent RTCP CNAME that is common across
179 several RTP streams, and potentially across several related RTP
180 sessions. A common example of such use occurs when lip-syncing audio
181 and video streams in a multimedia session, where a single participant
182 has to use the same RTCP CNAME for its audio RTP session and for its
183 video RTP session. Another example might be to synchronize the
184 layers of a layered audio codec, where the same RTCP CNAME has to be
185 used for each layer.
186
187 A longer-term persistent RTCP CNAME is sometimes useful to facilitate
188 third-party monitoring, consistent with [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>]. One such use
189 might be to allow network management tools to correlate the ongoing
190 quality of service for a participant across multiple RTP sessions for
191 fault diagnosis, and to understand long-term network performance
192 statistics. An implementation that wishes to discourage this type of
193 third-party monitoring can generate a unique RTCP CNAME for each RTP
194 session, or group of related RTP sessions, that it joins. Such a
195 per-session RTCP CNAME cannot be used for traffic analysis, and so
196 provides some limited form of privacy (note that there are non-RTP
197 means that can be used by a third party to correlate RTP sessions, so
198 the use of per-session RTCP CNAMEs will not prevent a determined
199 traffic analyst from monitoring such sessions).
200
201 This memo defines several different ways by which an implementation
202 can choose an RTCP CNAME. It is possible, and legitimate, for
203 independent implementations to make different choices of RTCP CNAME
204 when running on the same host. This can hinder third-party
205 monitoring, unless some external means is provided to configure a
206 persistent choice of RTCP CNAME for those implementations.
207
208 Note that there is no backwards compatibility issue (with [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>]-
209 compatible implementations) introduced in this memo, since the RTCP
210 CNAMEs are opaque strings to remote peers.
211
212
213
214
215
216
217
218
219
220 <span class="grey">Begen, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
223
224
225 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Requirements</span>
226
227 RTP endpoints will choose to generate RTCP CNAMEs that are persistent
228 or per-session. An RTP endpoint that wishes to generate a persistent
229 RTCP CNAME MUST use one of the following two methods:
230
231 o To produce a long-term persistent RTCP CNAME, an RTP endpoint MUST
232 generate and store a Universally Unique IDentifier (UUID)
233 [<a href="./rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>] for use as the "host" part of its RTCP CNAME. The UUID
234 MUST be version 1, 2, or 4, as described in [<a href="./rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>], with the
235 "urn:uuid:" stripped, resulting in a 36-octet printable string
236 representation.
237
238 o To produce a short-term persistent RTCP CNAME, an RTP endpoint
239 MUST either (a) use the numeric representation of the layer-2
240 (Media Access Control (MAC)) address of the interface that is used
241 to initiate the RTP session as the "host" part of its RTCP CNAME
242 or (b) generate and use an identifier by following the procedure
243 described in <a href="#section-5">Section 5</a>. In either case, the procedure is
244 performed once per initialization of the software. After
245 obtaining an identifier by doing (a) or (b), the least significant
246 48 bits are converted to the standard colon-separated hexadecimal
247 format [<a href="./rfc5342" title="&quot;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters&quot;">RFC5342</a>], e.g., "00:23:32:af:9b:aa", resulting in a
248 17-octet printable string representation.
249
250 In the two cases above, the "user@" part of the RTCP CNAME MAY be
251 omitted on single-user systems and MAY be replaced by an opaque token
252 on multi-user systems, to preserve privacy.
253
254 An RTP endpoint that wishes to generate a per-session RTCP CNAME MUST
255 use the following method:
256
257 o For every new RTP session, a new CNAME is generated following the
258 procedure described in <a href="#section-5">Section 5</a>. After performing that
259 procedure, the least significant 96 bits are used to generate an
260 identifier (to compromise between packet size and security), which
261 is converted to ASCII using Base64 encoding [<a href="./rfc4648" title="&quot;The Base16, Base32, and Base64 Data Encodings&quot;">RFC4648</a>]. This
262 results in a 16-octet string representation. The RTCP CNAME
263 cannot change over the life of an RTP session [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>]; hence,
264 only the initial SSRC value chosen by the endpoint is used. The
265 "user@" part of the RTCP CNAME is omitted when generating
266 per-session RTCP CNAMEs.
267
268
269
270
271
272
273
274
275
276 <span class="grey">Begen, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
279
280
281 It is believed that obtaining uniqueness (with a high probability) is
282 an important property that requires careful evaluation of the method.
283 This document provides a number of methods, at least one of which
284 would be suitable for all deployment scenarios. This document
285 therefore does not provide for the implementor to define and select
286 an alternative method.
287
288 A future specification might define an alternative method for
289 generating RTCP CNAMEs, as long as the proposed method has
290 appropriate uniqueness and there is consistency between the methods
291 used for multiple RTP sessions that are to be correlated. However,
292 such a specification needs to be reviewed and approved before
293 deployment.
294
295 The mechanisms described in this document are to be used to generate
296 RTCP CNAMEs, and they are not to be used for generating general-
297 purpose unique identifiers.
298
299 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Procedure to Generate a Unique Identifier</span>
300
301 The algorithm described below is intended to be used for locally
302 generated unique identifiers.
303
304 1. Obtain the current time of day in 64-bit NTP format [<a href="./rfc5905" title="&quot;Network Time Protocol Version 4: Protocol and Algorithms Specification&quot;">RFC5905</a>].
305
306 2. Obtain a modified EUI-64 identifier from the system running this
307 algorithm [<a href="./rfc4291" title="&quot;IP Version 6 Addressing Architecture&quot;">RFC4291</a>]. If such a system does not exist, an
308 identifier can be created from a 48-bit MAC address, as specified
309 in [<a href="./rfc4291" title="&quot;IP Version 6 Addressing Architecture&quot;">RFC4291</a>]. If one cannot be obtained or created, a suitably
310 unique identifier, local to the node, should be used (e.g.,
311 system serial number).
312
313 3. Concatenate the time of day with the system-specific identifier
314 in order to create a key.
315
316 4. If generating a per-session CNAME, also concatenate the RTP
317 endpoint's initial SSRC, the source and destination IP addresses,
318 and ports to the key.
319
320 5. Compute the 256-bit output of the SHA-256 digest of the key, as
321 specified in [<a href="./rfc4634" title="&quot;US Secure Hash Algorithms (SHA and HMAC-SHA)&quot;">RFC4634</a>].
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Begen, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
335
336
337 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
338
339 The security considerations of [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] apply to this memo.
340
341 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Considerations on Uniqueness of RTCP CNAMEs</span>
342
343 The recommendations given in this document for RTCP CNAME generation
344 ensure that a set of cooperating participants in an RTP session will,
345 with very high probability, have unique RTCP CNAMEs. However,
346 neither [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] nor this document provides any way to ensure that
347 participants will choose RTCP CNAMEs appropriately, and thus
348 implementations MUST NOT rely on the uniqueness of CNAMEs for any
349 essential security services. This is consistent with [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>],
350 which does not require that RTCP CNAMEs are unique within a session
351 but instead says that condition SHOULD hold. As described in the
352 Security Considerations section of [<a href="./rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], because each
353 participant in a session is free to choose its own RTCP CNAME, they
354 can do so in such a way as to impersonate another participant. That
355 is, participants are trusted to not impersonate each other. No
356 recommendation for generating RTCP CNAMEs can prevent this
357 impersonation, because an attacker can neglect the stipulation.
358 Secure RTP (SRTP) [<a href="./rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>] keeps unauthorized entities out of an RTP
359 session, but it does not aim to prevent impersonation attacks from
360 unauthorized entities.
361
362 This document uses a hash function to ensure the uniqueness of RTCP
363 CNAMEs. A cryptographic hash function is used because such functions
364 provide the randomness properties that are needed. However, no
365 security assumptions are made on the hash function. The hash
366 function is not assumed to be collision resistant, preimage
367 resistant, or second preimage resistant in an adversarial setting; as
368 described above, an attacker attempting an impersonation attack could
369 merely set the RTCP CNAME directly rather than attacking the hash
370 function. Similarly, the hash function is not assumed to be a one-
371 way function or pseudorandom in a cryptographic sense.
372
373 No confidentiality is provided on the data used as input to the RTCP
374 CNAME generation algorithm. It might be possible for an attacker who
375 observes an RTCP CNAME to determine the inputs that were used to
376 generate that value.
377
378 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Session Correlation Based on RTCP CNAMEs</span>
379
380 In some environments, notably telephony, a fixed RTCP CNAME value
381 allows separate RTP sessions to be correlated and eliminates the
382 obfuscation provided by IPv6 privacy addresses [<a href="./rfc4941" title="&quot;Privacy Extensions for Stateless Address Autoconfiguration in IPv6&quot;">RFC4941</a>] or IPv4
383 Network Address Port Translation (NAPT) [<a href="./rfc3022" title="&quot;Traditional IP Network Address Translator (Traditional NAT)&quot;">RFC3022</a>]. SRTP [<a href="./rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>]
384 can help prevent such correlation by encrypting Secure RTCP (SRTCP),
385
386
387
388 <span class="grey">Begen, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
391
392
393 but it should be noted that SRTP only mandates SRTCP integrity
394 protection (not encryption). Thus, RTP applications used in such
395 environments should consider encrypting their SRTCP or generate a
396 per-session RTCP CNAME as discussed in <a href="#section-4.1">Section 4.1</a>.
397
398 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
399
400 Thanks to Marc Petit-Huguenin, who suggested using UUIDs in
401 generating RTCP CNAMEs. Also, thanks to David McGrew for providing
402 text for the Security Considerations section.
403
404 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
405
406 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
407
408 [<a id="ref-RFC3550">RFC3550</a>] Schulzrinne, H., Casner, S., Frederick, R., and V.
409 Jacobson, "RTP: A Transport Protocol for Real-Time
410 Applications", STD 64, <a href="./rfc3550">RFC 3550</a>, July 2003.
411
412 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
413 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
414
415 [<a id="ref-RFC4122">RFC4122</a>] Leach, P., Mealling, M., and R. Salz, "A Universally
416 Unique IDentifier (UUID) URN Namespace", <a href="./rfc4122">RFC 4122</a>,
417 July 2005.
418
419 [<a id="ref-RFC4634">RFC4634</a>] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms
420 (SHA and HMAC-SHA)", <a href="./rfc4634">RFC 4634</a>, July 2006.
421
422 [<a id="ref-RFC4648">RFC4648</a>] Josefsson, S., "The Base16, Base32, and Base64 Data
423 Encodings", <a href="./rfc4648">RFC 4648</a>, October 2006.
424
425 [<a id="ref-RFC5905">RFC5905</a>] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
426 "Network Time Protocol Version 4: Protocol and Algorithms
427 Specification", <a href="./rfc5905">RFC 5905</a>, June 2010.
428
429 [<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
430 Architecture", <a href="./rfc4291">RFC 4291</a>, February 2006.
431
432 [<a id="ref-RFC5342">RFC5342</a>] Eastlake 3rd, D., "IANA Considerations and IETF Protocol
433 Usage for IEEE 802 Parameters", <a href="https://www.rfc-editor.org/bcp/bcp141">BCP 141</a>, <a href="./rfc5342">RFC 5342</a>,
434 September 2008.
435
436
437
438
439
440
441
442
443
444 <span class="grey">Begen, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6222">RFC 6222</a> Choosing an RTCP CNAME April 2011</span>
447
448
449 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
450
451 [<a id="ref-RFC1918">RFC1918</a>] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
452 and E. Lear, "Address Allocation for Private Internets",
453 <a href="https://www.rfc-editor.org/bcp/bcp5">BCP 5</a>, <a href="./rfc1918">RFC 1918</a>, February 1996.
454
455 [<a id="ref-RFC3022">RFC3022</a>] Srisuresh, P. and K. Egevang, "Traditional IP Network
456 Address Translator (Traditional NAT)", <a href="./rfc3022">RFC 3022</a>,
457 January 2001.
458
459 [<a id="ref-RFC3711">RFC3711</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
460 Norrman, "The Secure Real-time Transport Protocol (SRTP)",
461 <a href="./rfc3711">RFC 3711</a>, March 2004.
462
463 [<a id="ref-RFC4941">RFC4941</a>] Narten, T., Draves, R., and S. Krishnan, "Privacy
464 Extensions for Stateless Address Autoconfiguration in
465 IPv6", <a href="./rfc4941">RFC 4941</a>, September 2007.
466
467 Authors' Addresses
468
469 Ali Begen
470 Cisco
471 181 Bay Street
472 Toronto, ON M5J 2T3
473 CANADA
474
475 EMail: [email protected]
476
477
478 Colin Perkins
479 University of Glasgow
480 School of Computing Science
481 Glasgow G12 8QQ
482 UK
483
484 EMail: [email protected]
485
486
487 Dan Wing
488 Cisco Systems, Inc.
489 170 West Tasman Dr.
490 San Jose, CA 95134
491 USA
492
493 EMail: [email protected]
494
495
496
497
498
499
500 Begen, et al. Standards Track [Page 9]
501 </pre>