-
Notifications
You must be signed in to change notification settings - Fork 1
/
draft-jabley-multicast-ptr-01.txt
672 lines (393 loc) · 21.4 KB
/
draft-jabley-multicast-ptr-01.txt
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
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
Network Working Group J. Abley
Internet-Draft Dyn, Inc.
Intended status: Best Current Practice M. Richardson
Expires: January 15, 2015 Sandelman Software Works Corp.
T. Wicinski
Salesforce, Inc.
July 14, 2014
DNS Reverse Mapping for Multicast Addresses
draft-jabley-multicast-ptr-01
Abstract
The mapping of IPv4 and IPv6 addresses to names using the Domain Name
System (DNS) is colloquially known as "Reverse Mapping". Reverse
Mapping support for registered multicast address assignments in IPv4
is currently incomplete and ad-hoc; in IPv6 there is no support at
all.
This document describes procedures to be followed that will result in
more systematic and predictable support for Reverse Mapping for IPv4
multicast address assignments, and introduces analogous support for
IPv6.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 15, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
Abley, et al. Expires January 15, 2015 [Page 1]
Internet-Draft Reverse Mapping for Multicast July 2014
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. General Approach . . . . . . . . . . . . . . . . . . . . . . 3
3. Naming Scheme . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. IPv4 Multicast Addresses . . . . . . . . . . . . . . . . 3
3.2. IPv6 Multicast Addresses . . . . . . . . . . . . . . . . 4
4. Use of MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 4
5. IAB Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6.1. Registry Changes . . . . . . . . . . . . . . . . . . . . 5
6.1.1. IPv6 Multicast Scope Registry . . . . . . . . . . . . 5
6.1.2. IPv4 Multicast Address Space Registries . . . . . . . 6
6.1.3. IPv6 Multicast Address Space Registries . . . . . . . 7
6.2. Delegation of MCAST.ARPA and MCAST6.ARPA . . . . . . . . 7
6.3. Initial Zone Contents . . . . . . . . . . . . . . . . . . 7
6.4. Process Changes . . . . . . . . . . . . . . . . . . . . . 9
6.5. Ongoing Support for MCAST.NET . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. Editorial Notes . . . . . . . . . . . . . . . . . . 11
A.1. Change History . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
The Domain Name System (DNS), as originally specified in [RFC1034]
and [RFC1035], provides support for the mapping of IPv4 addresses to
names using a namespace convention within the IN-ADDR.ARPR domain and
the PTR resoure record type.
The analogous mapping of IPv6 addresses to names is specified in
[RFC3596], and adopts a similar namespace convention within the
IP6.ARPA domain.
Abley, et al. Expires January 15, 2015 [Page 2]
Internet-Draft Reverse Mapping for Multicast July 2014
Multicast addresses are assigned by the IANA, and assignments are
documented in various IANA registries.
For IPv4, Reverse Mapping of assigned multicast addresses to names
has historically been provided in an ad-hoc and incomplete fashion,
without tight coordination with the IANA multicast address assignment
processes. Names assigned to IPv4 multicast addresses have been
chosen somewhat arbitrarily within the MCAST.NET domain. For IPv6,
no Reverse Mapping is provided.
This document describes procedures to be followed by the IANA to
support predictable and consistent Reverse Mapping for registered
multicast addresses in both IPv4 and IPv6.
2. General Approach
This document specifies extensions to existing IPv4 and IPv6
multicast registries to include a mandatory column titled "DNS
Label". This field is required to be popluated with a unique, valid
DNS Label for all future multicast address assignments, except in the
case where reverse mapping for an address is explicitly not
desirable.
The procedures at the IANA relating to multicast address assignment
are extended to include the provisioning of appropriate changes in
the DNS at the time of registration or de-registration of any
multicast addresses. Specific actions requested of the IANA are
described in Section 6.
Names for multicast addresses are assigned under MCAST.ARPA for IPv4
addresses, and MCAST6.ARPA for IPv6 addresses. The naming schemes to
bs used in each case are described in Section 3. The use of
MCAST.ARPA rather than MCAST.NET is discussed in Section 4.
3. Naming Scheme
3.1. IPv4 Multicast Addresses
Each assigned IPv4 multicast address has an accompanying DNS Label.
The name associated with an IPv4 multicast address with DNS Label
SOMENAME is SOMENAME.MCAST.ARPA.
For example, suppose the assigned IPv4 multicast address 224.0.1.1
has the DNS Label "NTP". The address 224.0.1.1 maps to the name
"NTP.MCAST.ARPA"; the name "NTP.MCAST.ARPA" maps to the address
224.0.1.1.
Abley, et al. Expires January 15, 2015 [Page 3]
Internet-Draft Reverse Mapping for Multicast July 2014
3.2. IPv6 Multicast Addresses
Each assigned IPv6 multicast address has an accompanying DNS Label
("Address Label").
IPv6 multicast addresses may be of fixed or variable scope. The
naming scheme for these addresses incorporates a scope identifier
using an additional DNS Label ("Scope Label"), specified in a
dedicated registry (see Section 6.1.1). Both fixed and variable
scope multicast addresses use the same naming scheme.
The name associated with an IPv6 multicast address with Scope Label
SCOPE and Address Label SOMENAME is SOMENAME.SCOPE.MCAST6.ARPA.
For example, suppose ff01::1 is an assigned IPv6 multicast address
with Scope Label "NODE-LOCAL" and Address Label "ALL-NODES". The
address ff01::1 maps to the name "ALL-NODES.NODES-LOCAL.MCAST6.ARPA";
the name "ALL-NODES.NODES-LOCAL.MCAST6.ARPA" maps to the address
ff01::1.
The variable-scope multicast address ff0x::fb will have different
Reverse Mapping depending on the scope specified in the address (i.e.
the value of x), although the Address Label in each case will be the
same ("MDNSV6"). The Site-Local address ff05::fb has an associated
Scope Label "SITE-LOCAL", and is therefore named MDNSV6.SITE-
LOCAL.MCAST6.ARPA. The Link-Local address ff02::fb has an associated
Scope Label "LINK-LOCAL" and hence is named MDNSV6.LINK-
LOCAL.MCAST6.ARPA.
4. Use of MCAST.ARPA
Use of the MCAST.ARPA domain rather than MCAST.NET for IPv4 multicast
addresses is specified for the same reasons that led IP6.INT to be
superceded by "IP6.ARPA" [RFC3152].
It is prudent to assume that hard-coded assumptions about names in
MCAST.NET exist, and will persist for some time. This document
specifies that names in the MCAST.ARPA domain also be available in
the MCAST.NET domain, to provide support for software with those
assumptions. Ongoing support for the MCAST.NET zone is described in
Section 6.5.
It is possible that in the future empirical measurement will confirm
that the use of names under MCAST.NET is no longer required and that
provisioning of the MCAST.NET domain can safely cease. This document
provides no such measurement and makes no such recommendation,
however.
Abley, et al. Expires January 15, 2015 [Page 4]
Internet-Draft Reverse Mapping for Multicast July 2014
5. IAB Considerations
This document proposes a delegation within the ARPA domain, and, in
accordance with [RFC3172], IAB review and approval of the delegation
of MCAST.ARPA and MCAST6.ARPA as described in Section 6.2 is
required.
Once IAB approval has been obtained, this section may be removed
prior to publication or updated to include text that confirms the
IAB's decision, at the IAB's discretion.
6. IANA Considerations
6.1. Registry Changes
6.1.1. IPv6 Multicast Scope Registry
The IANA is directed to create a new registry as follows:
Registry Name: IPv6 Multicast Scopes
Registration Procedure: Standards Action
Reference: This document
Schema: See initial contents, below. Note that the Scope Value and
DNS Label fields are mandatory for all rows, and that values
chosen for future DNS Label fields are required to be unique
within this registry.
The initial contents of this new registry should be:
Abley, et al. Expires January 15, 2015 [Page 5]
Internet-Draft Reverse Mapping for Multicast July 2014
+------+-----------+------------------+-----------------------------+
| Scop | DNS Label | Scope Name | Reference |
| e Va | | | |
| lue | | | |
+------+-----------+------------------+-----------------------------+
| 0x0 | (none) | Reserved | [RFC4291] |
| | | | |
| 0x1 | NODE- | Node-Local Scope | [RFC4291] |
| | LOCAL | | |
| | | | |
| 0x2 | LINK- | Link-Local Scope | [RFC4291] |
| | LOCAL | | |
| | | | |
| 0x3 | REALM- | Realm-Local | [I-D.ietf-6man-multicast-sc |
| | LOCAL | Scope | opes] |
| | | | |
| 0x4 | ADMIN- | Admin-Local | [RFC4291] |
| | LOCAL | Scope | |
| | | | |
| 0x5 | SITE- | Site-Local Scope | [RFC4291] |
| | LOCAL | | |
| | | | |
| 0x8 | ORG-LOCAL | Organisation- | [RFC4291] |
| | | Local Scope | |
| | | | |
| 0xE | GLOBAL | Global Scope | [RFC4291] |
+------+-----------+------------------+-----------------------------+
Additionally, The IANA SHOULD add "Date Registered" and "Last
Revised" columns to the schema.
6.1.2. IPv4 Multicast Address Space Registries
The IANA is directed to add a mandatory "DNS Label" column to all
IPv4 Multicast Address Space registries. The initial contents of the
DNS Label field for each row should be taken from the corresponding
MCAST.NET zone owner names where available; addresses with no
existing mapping in MCAST.NET should have DNS Labels assigned by the
IANA at their discretion.
All existing assignments should have a DNS Label assigned. A DNS
Label should be mandatory for all future registrations. DNS Labels
are required to be unique for all IPv4 multicast address assignments.
Abley, et al. Expires January 15, 2015 [Page 6]
Internet-Draft Reverse Mapping for Multicast July 2014
6.1.3. IPv6 Multicast Address Space Registries
The IANA is directed to add a mandatory "DNS Label" column to all
IPv6 Multicast Address Space registries. The initial contents of the
DNS Label field for each row should be assigned by the IANA at their
discretion.
All existing assignments should have a DNS Label assigned. A DNS
Label should be mandatory for all future registrations. DNS Labels
are required to be unique for all IPv6 multicast address assignments.
6.2. Delegation of MCAST.ARPA and MCAST6.ARPA
The IANA is directed to create and host the MCAST.ARPA and
MCAST6.ARPA zones on name servers of their choosing. The MCAST.ARPA
and MCAST6.ARPA zones should be signed using DNSSEC, with DNSSEC
parameters chosen by the IANA. The initial zone contents should be
as described in Section 6.3.
The IANA is directed to provision secure delegations for the
MCAST.ARPA and MCAST6.ARPA zones from the ARPA zone (i.e. delegations
with accompanying DS RRSets).
6.3. Initial Zone Contents
The IANA is directed to populate the MCAST.ARPA and MCAST6.ARPA
zones, and the corresponding reverse mapping zones under IN-ADDR.ARPA
and IP6.ARPA, directly from the IPv4 and IPv6 Multicast Address
Registries, amended as described in Section 6.1.
As an example, if the IPv6 Variable Scope Multicast Addresses sub-
registry contained the following entry:
+-------------+-------------+-----------+
| Address(es) | Description | DNS Label |
+-------------+-------------+-----------+
| FF0X::FB | mDNSv6 | MDNSV6 |
+-------------+-------------+-----------+
then the following DNS records would be required:
Abley, et al. Expires January 15, 2015 [Page 7]
Internet-Draft Reverse Mapping for Multicast July 2014
$ORIGIN MCAST6.ARPA.
;
; all scoped addresses for mDNSv6
;
MDNSV6.NODE-LOCAL AAAA FF01::FB
MDNSV6.LINK-LOCAL AAAA FF02::FB
MDNSV6.ADMIN-LOCAL AAAA FF04::FB
MDNSV6.SITE-LOCAL AAAA FF05::FB
MDNSV6.ORG-LOCAL AAAA FF08::FB
MDNSV6.GLOBAL AAAA FF0E::FB
$ORIGIN 0.F.F.IP6.ARPA.
;
; all scoped addresses for mDNSv6 (split across lines for clarity)
;
B.F.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1 \
PTR MDNSV6.NODE-LOCAL.MCAST6.ARPA.
B.F.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2 \
PTR MDNSV6.LINK-LOCAL.MCAST6.ARPA.
B.F.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4 \
PTR MDNSV6.ADMIN-LOCAL.MCAST6.ARPA.
B.F.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5 \
PTR MDNSV6.SITE-LOCAL.MCAST6.ARPA.
B.F.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8 \
PTR MDNSV6.ORG-LOCAL.MCAST6.ARPA.
B.F.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.E \
PTR MDNSV6.GLOBAL.MCAST6.ARPA.
As a further example, if the IPv4 Internetwork Control Block
Multicast Address Registry contained the following entry:
+-------------+--------------+-----------+
| Address(es) | Description | DNS Label |
+-------------+--------------+-----------+
| 224.0.1.2 | SGI-Dogfight | SGI-DOG |
+-------------+--------------+-----------+
then the following DNS records would be required:
Abley, et al. Expires January 15, 2015 [Page 8]
Internet-Draft Reverse Mapping for Multicast July 2014
$ORIGIN MCAST.ARPA.
;
; SGI-Dogfight address
;
SGI-DOG A 224.0.1.2
$ORIGIN 224.IN-ADDR.ARPA.
;
; SGI-Dogfight address
;
2.1.0 PTR SGI-DOG.MCAST.ARPA.
6.4. Process Changes
The IANA is directed to require a valid and unique DNS Label to be
specified within the existing processes of multicast address
assignment in IPv4 and IPv6.
The IANA is further directed to maintain the MCAST.ARPA, MCAST6.ARPA
and related domains under IP6.ARPA and IN-ADDR.ARPA such that any
additions, changes or deletions from the corresponding address
registries are reflected accurately in the DNS.
6.5. Ongoing Support for MCAST.NET
IANA is directed to remove all non-apex resource records from the
MCAST.NET zone and to add an apex DNAME [RFC6672] with target
MCAST.ARPA. The intention is to provide backwards compatibility for
software that has hard-coded assumptions about naming conventions for
IPv4 multicast addresses.
For example, the following describes the result of this change for
MCAST.NET SOA serial 2012123836, with DNSSEC resource records omitted
for clarity:
Abley, et al. Expires January 15, 2015 [Page 9]
Internet-Draft Reverse Mapping for Multicast July 2014
$ORIGIN MCAST.NET.
; beginning of zone
@ SOA SNS.DNS.ICANN.ORG. NOC.DNS.ICANN.ORG. (
2012123836
7200
3600
604800
3600 )
NS A.IANA-SERVERS.NET.
NS B.IANA-SERVERS.NET.
NS C.IANA-SERVERS.NET.
NS NS.ICANN.ORG.
DNAME MCAST.ARPA.
; end of zone
7. Security Considerations
This document presents no known additional security concerns to the
Internet.
8. Acknowledgements
Your name here, etc.
9. References
9.1. Normative References
[I-D.ietf-6man-multicast-scopes]
Droms, R., "IPv6 Multicast Address Scopes", draft-ietf-
6man-multicast-scopes-07 (work in progress), June 2014.
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987.
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
"DNS Extensions to Support IP Version 6", RFC 3596,
October 2003.
Abley, et al. Expires January 15, 2015 [Page 10]
Internet-Draft Reverse Mapping for Multicast July 2014
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
9.2. Informative References
[RFC3152] Bush, R., "Delegation of IP6.ARPA", BCP 49, RFC 3152,
August 2001.
[RFC3172] Huston, G., "Management Guidelines & Operational
Requirements for the Address and Routing Parameter Area
Domain ("arpa")", BCP 52, RFC 3172, September 2001.
[RFC6672] Rose, S. and W. Wijngaards, "DNAME Redirection in the
DNS", RFC 6672, June 2012.
Appendix A. Editorial Notes
This section (and sub-sections) to be removed prior to publication.
A.1. Change History
00 Initial draft, circulated for the purposes of entertainment.
01 Bumped draft number and updated date to resurrect, based on
possibility of renewed interest. Added Michael and Tim as co-
authors.
Authors' Addresses
Joe Abley
Dyn, Inc.
470 Moore Street
London, ON N6C 2C2
Canada
Phone: +1 519 670 9327
Email: [email protected]
Michael C. Richardson
Sandelman Software Works Corp.
470 Dawson Avenue
Ottawa, ON K1Z 5V7
Canada
Phone: +1 613 276 6809
Email: [email protected]
Abley, et al. Expires January 15, 2015 [Page 11]
Internet-Draft Reverse Mapping for Multicast July 2014
Tim Wicinski
Salesforce, Inc.
1 Market St #300
San Francisco, CA 94105
US
Phone: +1.571.449.1550
Email: [email protected]
Abley, et al. Expires January 15, 2015 [Page 12]