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
|
<pre>Network Working Group D. Meyer
Request for Comments: 3138 Sprint
Category: Informational June 2001
<span class="h1">Extended Assignments in 233/8</span>
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
This memo provides describes the mapping of the GLOP addresses
corresponding to the private AS space.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
<a href="./rfc2770">RFC 2770</a> [<a href="./rfc2770" title=""GLOP Addressing in 233/8"">RFC2770</a>] describes an experimental policy for use of the
class D address space using 233/8. The technique described there
maps 16 bits of Autonomous System number (AS) into the middle two
octets of 233/8 to yield a /24. While this technique has been
successful, the assignments are inefficient in those cases in which a
/24 is too small or the user doesn't have its own AS.
<a href="./rfc1930">RFC 1930</a> [<a href="./rfc1930" title=""Guidelines for creation, selection, and registration of an Autonomous System (AS)"">RFC1930</a>] defines the private AS space to be 64512 through
65535. This memo expands on <a href="./rfc2770">RFC 2770</a> to allow routing registries to
assign multicast addresses from the GLOP space corresponding to the
<a href="./rfc1930">RFC 1930</a> private AS space. This space will be referred to as the
EGLOP (Extended GLOP) address space.
This memo is a product of the Multicast Deployment Working Group
(MBONED) in the Operations and Management Area of the Internet
Engineering Task Force. Submit comments to <mboned@ns.uoregon.edu>
or the authors.
The terms "Specification Required", "Expert Review", "IESG Approval",
"IETF Consensus", and "Standards Action", are used in this memo to
refer to the processes described in [<a href="./rfc2434">RFC2434</a>]. The keywords MUST,
MUST NOT, MAY, OPTIONAL, REQUIRED, RECOMMENDED, SHALL, SHALL NOT,
SHOULD, SHOULD NOT are to be interpreted as defined 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">Meyer Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3138">RFC 3138</a> Extended Assignments in 233/8 June 2001</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview</span>
<a href="http://www.iana.org/assignments/multicast-addresses">http://www.iana.org/assignments/multicast-addresses</a> defines a
mechanism for assignment of multicast addresses that are generally
for use in network control applications. It is envisioned that those
addresses assigned from the EGLOP space (233.252.0.0 -
233.255.255.255) will be used by applications that cannot use
Administratively Scoped Addressing [<a href="./rfc2365" title=""Administratively Scoped IP Multicast"">RFC2365</a>], GLOP Addressing
[<a href="./rfc2770" title=""GLOP Addressing in 233/8"">RFC2770</a>], or Source Specific Multicast (Source Specific Multicast,
or SSM, is an extension of IP Multicast in which traffic is forwarded
to receivers from only those multicast sources for which the
receivers have explicitly expressed interest, and is primarily
targeted at one-to-many (broadcast) applications).
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Assignment Criteria</span>
Globally scoped IPv4 multicast addresses in the EGLOP space are
assigned by a Regional Registry (RIR). An applicant MUST, as per
[<a href="#ref-IANA">IANA</a>], show that the request cannot be satisfied using
Administratively Scoped addressing [<a href="./rfc2365" title=""Administratively Scoped IP Multicast"">RFC2365</a>], GLOP addressing
[<a href="./rfc2770" title=""GLOP Addressing in 233/8"">RFC2770</a>], or SSM. The fine-grained assignment policy is left to the
assigning RIR.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
The assignment scheme described in this document does not effect the
security properties of the the single source or any source multicast
service models.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
Kurt Kayser, Mirjam Kuehne, Michelle Schipper and Randy Bush provided
many insightful comments on earlier versions of this document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Author's Address</span>
David Meyer
Sprint
12502 Sunrise Valley Dr
Reston VA, 20191
EMail: dmm@sprint.net
<span class="grey">Meyer Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3138">RFC 3138</a> Extended Assignments in 233/8 June 2001</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
[<a id="ref-IANA">IANA</a>] <a href="http://www.iana.org/assignments/multicast-addresses">http://www.iana.org/assignments/multicast-addresses</a>
[<a id="ref-RFC1930">RFC1930</a>] Hawkinson J. and T. Bates, "Guidelines for
creation, selection, and registration of an
Autonomous System (AS)", <a href="./rfc1930">RFC 1930</a>, March 1996.
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process --
Revision 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
[<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>,
March 1997.
[<a id="ref-RFC2365">RFC2365</a>] Meyer, D., "Administratively Scoped IP Multicast",
<a href="./rfc2365">RFC 2365</a>, July 1998.
[<a id="ref-RFC2770">RFC2770</a>] Meyer, D. and P. Lothberg, "GLOP Addressing in
233/8", <a href="./rfc2770">RFC 2770</a>, February 2000.
[<a id="ref-RFC2780">RFC2780</a>] Bradner, S. and V. Paxson, "IANA Allocation
Guidelines For Values In the Internet Protocol
and Related Headers", <a href="https://www.rfc-editor.org/bcp/bcp37">BCP 37</a>, <a href="./rfc2780">RFC 2780</a>, March
2000.
<span class="grey">Meyer Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3138">RFC 3138</a> Extended Assignments in 233/8 June 2001</span>
Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Meyer Informational [Page 4]
</pre>
|
