< draft-ietf-mboned-mcast-arpa-02.txt		draft-ietf-mboned-mcast-arpa-03.txt >
	Network Working Group P. Koch		Network Working Group P. Koch
	Internet-Draft DENIC eG		Internet-Draft DENIC eG
	Intended status: BCP L. Vegoda		Updates: 5771 (if approved) L. Vegoda
	Expires: December 16, 2010 ICANN		Intended status: BCP ICANN
	June 14, 2010		Expires: January 6, 2012 July 5, 2011
	Moving MCAST.NET into the ARPA infrastructure top level domain		Moving MCAST.NET into the ARPA infrastructure top level domain
	draft-ietf-mboned-mcast-arpa-02		draft-ietf-mboned-mcast-arpa-03
	Abstract		Abstract
	This document proposes to migrate the MCAST.NET domain into the ARPA		This document proposes to migrate the MCAST.NET domain into the ARPA
	top level domain that is dedicated to infrastructure support. It		top level domain, which is dedicated to infrastructure support. It
	also provides for a maintenance policy for the new MCAST.ARPA domain		also provides a maintenance policy for the new MCAST.ARPA domain,
	and covers migration issues and caveats. This document updates RFC		related registrations in IN-ADDR.ARPA and describes the migration
	5771 and forms part of BCP 51.		process. This document updates RFC 5771 and forms part of BCP 51.
	XXX reverse mapping
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 December 16, 2010.		This Internet-Draft will expire on January 6, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2011 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
	skipping to change at page 2, line 32 ¶		skipping to change at page 2, line 30 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . 3
	3. The ARPA top level domain . . . . . . . . . . . . . . . 3		3. The ARPA top level domain . . . . . . . . . . . . . . . 3
	4. Current Use . . . . . . . . . . . . . . . . . . . . . . 3		4. Current Use . . . . . . . . . . . . . . . . . . . . . . 3
	5. Registration Policy . . . . . . . . . . . . . . . . . . 3		5. Registration Policy . . . . . . . . . . . . . . . . . . 3
	5.1. Names and Addresses eligible for Registration in		5.1. Names and Addresses eligible for Registration in
	MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 4		MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 4
	5.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4		5.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4
	5.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4		5.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4
	5.3.1. Reverse Mapping for 224/4 . . . . . . . . . . . . . . . 4		5.3.1. Reverse Mapping for 224/4 . . . . . . . . . . . . . . . 4
	5.3.2. Reverse Mapping for FF0::/12 . . . . . . . . . . . . . 4		5.3.2. Reverse Mapping for ff00::/8 . . . . . . . . . . . . . 4
	6. Migration Issues . . . . . . . . . . . . . . . . . . . 4		6. Migration Issues . . . . . . . . . . . . . . . . . . . 5
	6.1. Migration Strategies . . . . . . . . . . . . . . . . . 5		6.1. Migration Strategies . . . . . . . . . . . . . . . . . 5
	6.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 5		6.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 5
	6.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 5		6.1.2. Removing Registrations from MCAST.NET while
	6.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 5		maintaining operational stability . . . . . . . . . . . 5
	7. Security Considerations . . . . . . . . . . . . . . . . 5		7. Security Considerations . . . . . . . . . . . . . . . . 5
	8. IANA Considerations . . . . . . . . . . . . . . . . . . 6		8. IANA Considerations . . . . . . . . . . . . . . . . . . 6
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . 6		9. Acknowledgements . . . . . . . . . . . . . . . . . . . 6
	10. References . . . . . . . . . . . . . . . . . . . . . . 6		10. References . . . . . . . . . . . . . . . . . . . . . . 6
	10.1. Normative References . . . . . . . . . . . . . . . . . 6		10.1. Normative References . . . . . . . . . . . . . . . . . 6
	10.2. Informative References . . . . . . . . . . . . . . . . 7		10.2. Informative References . . . . . . . . . . . . . . . . 7
	Appendix A. Document Revision History . . . . . . . . . . . . . . . 7		Appendix A. Document Revision History . . . . . . . . . . . . . . . 7
	A.1. Changes from -01 to -02 . . . . . . . . . . . . . . . . 7		A.1. Changes from -2 to -03 . . . . . . . . . . . . . . . . 7
	A.2. Changes from -00 to -01 . . . . . . . . . . . . . . . . 7		A.2. Changes from -01 to -02 . . . . . . . . . . . . . . . . 8
	A.3. Initial Document . . . . . . . . . . . . . . . . . . . 8		A.3. Changes from -00 to -01 . . . . . . . . . . . . . . . . 8
			A.4. Initial Document . . . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	This document describes a maintenance policy and migration strategy		This document describes the migration strategy from the MCAST.NET
	for the MCAST.NET (MCAST.ARPA) domain that contains names for a		domain to MCAST.ARPA, which MUST contains DNS names for a subset of
	subset of the multicast groups assigned by the IANA.		the multicast groups assigned by the IANA. It also specifies a
			maintenance policy for the MCAST.ARPA domain.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in BCP 14, [RFC2119].		document are to be interpreted as described in BCP 14, [RFC2119].
	3. The ARPA top level domain		3. The ARPA top level domain
	[RFC3172] designates the ARPA top level domain as "Address and		[RFC3172] designates the ARPA top level domain as "Address and
	Routing Parameters Area" to be used for infrastructure applications.		Routing Parameters Area" to be used for infrastructure applications.
	The MCAST.NET second level domain fulfills the criteria set out in		The MCAST.NET second level domain fulfills the criteria set out in
	section 2.1 of [RFC3172]. However, there is no standards track		section 2.1 of [RFC3172]. However, there is no standards track
	document explicitly designating this domain to a multicast group name		document explicitly designating this domain to a multicast group name
	to multicast group address mapping.		to multicast group address mapping.
	[RFC5771] defines the IPv4 multicast address assignment policy.		The assignment of IPv4 multicast addresses is governed by BCP51
			[RFC5771]. IPv6 multicast address assignment is dealt with in
	[RFC4291] defines the IPv6 multicast address assignment policy.		[RFC3307] and section 2.7 of [RFC4291].
	4. Current Use		4. Current Use
	Currently the zone MCAST.NET reflects the contents of parts the IANA		Currently the zone MCAST.NET reflects the contents of parts the IANA
	IPv4 multicast address registry. However, some names are missing		IPv4 multicast address registry. However, some names are missing
	from the DNS zone and some names used differ from the description		from the DNS zone and some names used differ from the description
	that appears in the registry file. Entries in the IPv6 multicast		that appears in the registry file. Entries in the IPv6 multicast
	address registry are not reflected in the MCAST.NET zone.		address registry are not reflected in the MCAST.NET zone.
	With few exceptions, only multicast group addresses from 224.0.0/24		With few exceptions, only multicast group addresses from 224.0.0/24
	and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do		and 224.0.1/24 are listed in MCAST.NET. Addresses outside 224/8 do
	not appear at all.		not appear at all.
	5. Registration Policy		5. Registration Policy
	Names within MCAST.ARPA will consist of one additional label and MUST		Names within MCAST.ARPA will consist of one additional label and MUST
	adhere to the hostname syntax requirements of [RFC1123]. These names		adhere to the hostname syntax requirements of [RFC1123]. These names
	MUST own a single A RR, a single AAAA RR, or both. Addresses will be		MUST own a single A RR, a single AAAA RR, or both. Addresses will be
	in the IPv4 or IPv6 multicast address space.		in the IPv4 or IPv6 multicast address space and recorded in the
			registry.
	5.1. Names and Addresses eligible for Registration in MCAST.ARPA		5.1. Names and Addresses eligible for Registration in MCAST.ARPA
	Only IANA multicast address registrations are eligible for being		Only IANA multicast address registrations are eligible for being
	listed in MCAST.ARPA.		listed in MCAST.ARPA.
	For IPv4, only multicast groups from 224.0.0/24 (Local Network		For IPv4, only multicast groups from 224.0.0/24 (Local Network
	Control Block) and 224.0.1/24 (Internetwork Control Block) will have		Control Block) and 224.0.1/24 (Internetwork Control Block) will have
	names assigned.		names assigned.
	skipping to change at page 4, line 28 ¶		skipping to change at page 4, line 30 ¶
	5.2. Subdomains of MCAST.ARPA		5.2. Subdomains of MCAST.ARPA
	The namespace under MCAST.ARPA is considered flat, i.e., all direct		The namespace under MCAST.ARPA is considered flat, i.e., all direct
	descendants of MCAST.ARPA are leaves in the DNS tree. Future		descendants of MCAST.ARPA are leaves in the DNS tree. Future
	extensions might want to define subdomains that serve special		extensions might want to define subdomains that serve special
	purposes. Any such designation needs IETF consensus [RFC5226].		purposes. Any such designation needs IETF consensus [RFC5226].
	5.3. Corresponding Reverse Mapping		5.3. Corresponding Reverse Mapping
	The DNS Reverse Mapping for those multicast groups that appear as		The DNS Reverse Mapping for those multicast groups that appear as
	addresses in MCAST.ARPA MUST be kept consistent with the forward		addresses in MCAST.ARPA MUST remain consistent with the forward
	namespace.		namespace.
	5.3.1. Reverse Mapping for 224/4		5.3.1. Reverse Mapping for 224/4
	A single DNS PTR record will be entered at the corresponding owner		A single DNS PTR record will be entered at the corresponding owner
	within the 224.IN-ADDR.ARPA domain that points to the multicast group		within the 224.IN-ADDR.ARPA domain that points to the multicast group
	name within MCAST.ARPA.		name within MCAST.ARPA.
	The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated		The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated
	but MUST remain empty (except necessary infrastructure RRs). The one		but MUST remain empty except for necessary infrastructure RRs. The
	exception is 233.IN-ADDR.ARPA. A mechanism for the delegation of		one exception is 233.IN-ADDR.ARPA. A mechanism for the delegation of
	reverse mapping for GLOP space [RFC3180] should be designed and		reverse mapping for GLOP space [RFC3180] will be specified and
	implemented.		documented on the IANA web site.
	5.3.2. Reverse Mapping for FF0::/12		5.3.2. Reverse Mapping for ff00::/8
	[How to deal with IPv6 multicast reverse mapping is TBD.]		Directions for this will be published as a separate document.
	6. Migration Issues		6. Migration Issues
	The current content of the MCAST.NET zone MUST be brought in line		As described below, the current content of the MCAST.NET zone MUST be
	with the multicast address registry.		brought in line with the multicast address registry.
	Since legacy systems may use MCAST.NET for quite some time, there		Since legacy systems are likely to use MCAST.NET for quite some time,
	needs to be a mapping/forwarding solution to answer those queries in		there needs to be a mapping/forwarding solution to answer those
	a useful manner without discouraging migration.		queries in a useful manner without discouraging migration.
	RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678].		RFCs mentioning MCAST.NET are [RFC3261] and [RFC3678].
	An updated multicast address architecture appears in		An updated multicast address architecture appears in [RFC6308].
	[I-D.ietf-mboned-addrarch].
	6.1. Migration Strategies		6.1. Migration Strategies
	After the move, several options are available for the future handling		After the move, several options are available for the future handling
	of MCAST.NET.		of MCAST.NET.
	[[The working group needs to choose one of the options.]]		[[The working group needs to choose one of the options.]]
	6.1.1. Freeze		6.1.1. Freeze
	The current MCAST.NET zone could be frozen, so that no additions,		The current MCAST.NET zone could be frozen, so that no additions,
	deletions or changes to the content (apart from those necessary for		deletions or changes to the content (apart from those necessary for
	maintenance, e.g. SOA and NS RRs) would be performed. New		maintenance, e.g. SOA and NS RRs) would be performed. New
	registrations would only be available in MCAST.ARPA, so this could be		registrations would only be available in MCAST.ARPA, so this could be
	an incentive for querying clients to alter their behavior as well.		an incentive for querying clients to alter their behavior as well.
	6.1.2. Phase Out		6.1.2. Removing Registrations from MCAST.NET while maintaining
			operational stability
	MCAST.NET would only see deletions. Even after the last record will
	have been deleted, the domain should be kept registered by the IANA
	to prevent redelegation ...
	6.1.3. Continue
	MCAST.NET could be further operated in parallel, either by		MCAST.NET will only see deletions but even after the last record has
	operational habit or per DNAME RR, as described in [RFC2672].		been deleted, the domain MUST be kept registered by the IANA. and
			should be operated in parallel using a DNAME RR, as described in
			[RFC2672].
	7. Security Considerations		7. Security Considerations
	The usual Security Considerations for the DNS [RFC3833]apply.		The usual Security Considerations for the DNS [RFC3833] apply.
	The MCAST.ARPA., MCAST.NET., and the Reverse mapping zones mentioned		The MCAST.ARPA., MCAST.NET., and the Reverse mapping zones mentioned
	in this document SHALL be DNSSEC signed by the IANA under direction		in this document MUST be DNSSEC signed by the IANA under direction
	from the IAB.		from the IAB.
	There is no Security Problem associated with the migration itself.		There is no security problem associated with the migration itself.
	XXX keeping MCAST.NET.
	{This section needs more work.}		{This section needs more work.}
	8. IANA Considerations		8. IANA Considerations
	This document amends [RFC5771] to add a mandatory entry in the		This document amends [RFC5771] to add a mandatory entry in the
	MCAST.ARPA domain and a corresponding reverse mapping entry. The		MCAST.ARPA domain and a corresponding reverse mapping entry, with
	officially registered multicast group name is made subject to DNS		relevant DNS names published in the registry. The officially
	hostname syntax rules.		registered multicast group name is made subject to DNS hostname
			syntax rules.
	9. Acknowledgements		9. Acknowledgements
	The authors would like to thank David Conrad and Joe Abley for their		The authors would like to thank David Conrad and Joe Abley for their
	input.		input.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	skipping to change at page 6, line 40 ¶		skipping to change at page 6, line 41 ¶
	[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, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC3172] Huston, G., "Management Guidelines & Operational		[RFC3172] Huston, G., "Management Guidelines & Operational
	Requirements for the Address and Routing Parameter Area		Requirements for the Address and Routing Parameter Area
	Domain ("arpa")", BCP 52, RFC 3172, September 2001.		Domain ("arpa")", BCP 52, RFC 3172, September 2001.
	[RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8",		[RFC3180] Meyer, D. and P. Lothberg, "GLOP Addressing in 233/8",
	BCP 53, RFC 3180, September 2001.		BCP 53, RFC 3180, September 2001.
			[RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast
			Addresses", RFC 3307, August 2002.
	[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing		[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
	Architecture", RFC 4291, February 2006.		Architecture", RFC 4291, February 2006.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for		[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for
	IPv4 Multicast Address Assignments", BCP 51, RFC 5771,		IPv4 Multicast Address Assignments", BCP 51, RFC 5771,
	March 2010.		March 2010.
			[RFC6308] Savola, P., "Overview of the Internet Multicast Addressing
			Architecture", RFC 6308, June 2011.
	10.2. Informative References		10.2. Informative References
	[I-D.ietf-mboned-addrarch]		[I-D.ietf-mboned-addrarch]
	Savola, P., "Overview of the Internet Multicast Addressing		Savola, P., "Overview of the Internet Multicast Addressing
	Architecture", draft-ietf-mboned-addrarch-06 (work in		Architecture", draft-ietf-mboned-addrarch-07 (work in
	progress), August 2009.		progress), October 2010.
	[RFC2672] Crawford, M., "Non-Terminal DNS Name Redirection",		[RFC2672] Crawford, M., "Non-Terminal DNS Name Redirection",
	RFC 2672, August 1999.		RFC 2672, August 1999.
			[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
			Values In the Internet Protocol and Related Headers",
			BCP 37, RFC 2780, March 2000.
	[RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet		[RFC2908] Thaler, D., Handley, M., and D. Estrin, "The Internet
	Multicast Address Allocation Architecture", RFC 2908,		Multicast Address Allocation Architecture", RFC 2908,
	September 2000.		September 2000.
	[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,		[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
	A., Peterson, J., Sparks, R., Handley, M., and E.		A., Peterson, J., Sparks, R., Handley, M., and E.
	Schooler, "SIP: Session Initiation Protocol", RFC 3261,		Schooler, "SIP: Session Initiation Protocol", RFC 3261,
	June 2002.		June 2002.
	[RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface		[RFC3678] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface
	Extensions for Multicast Source Filters", RFC 3678,		Extensions for Multicast Source Filters", RFC 3678,
	January 2004.		January 2004.
	[RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain		[RFC3833] Atkins, D. and R. Austein, "Threat Analysis of the Domain
	Name System (DNS)", RFC 3833, August 2004.		Name System (DNS)", RFC 3833, August 2004.
	Appendix A. Document Revision History		Appendix A. Document Revision History
	This section is to be removed should the draft be published.		This section is to be removed should the draft be published.
	A.1. Changes from -01 to -02		A.1. Changes from -2 to -03
			Added text on reverse delegation to the abstract
			Updated the order of text in the introduction
			Added a requirements to publish DNS names in the assignment registry
			in section 5
			Consigned ff0::/12 reverse delegation issues to a separate document
			Merged 6.1.2 and 6.1.3 with updated text
			A.2. Changes from -01 to -02
	Added text about v6 multicast.		Added text about v6 multicast.
	Added text about GLOP space		Added text about GLOP space
	Added terminology section and RFC 2119 language		Added terminology section and RFC 2119 language
	A.2. Changes from -00 to -01		A.3. Changes from -00 to -01
	Added text about DNS reverse mapping. Eligibility for an MCAST.ARPA		Added text about DNS reverse mapping. Eligibility for an MCAST.ARPA
	name now restricted to 224.0.0/24 and 224.0.1/24. Stronger		name now restricted to 224.0.0/24 and 224.0.1/24. Stronger
	requirement for MCAST.ARPA subdomains.		requirement for MCAST.ARPA subdomains.
	A.3. Initial Document		A.4. Initial Document
	First draft, taking over with only little changes from		First draft, taking over with only little changes from
	draft-koch-mboned-mcast-arpa-00.txt		draft-koch-mboned-mcast-arpa-00.txt
	Authors' Addresses		Authors' Addresses
	Peter Koch		Peter Koch
	DENIC eG		DENIC eG
	Kaiserstrasse 75-77		Kaiserstrasse 75-77
	Frankfurt 60329		Frankfurt 60329
End of changes. 31 change blocks.
	61 lines changed or deleted		80 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/