draft-ietf-mboned-mcast-arpa-00.txt		draft-ietf-mboned-mcast-arpa-01.txt
	Network Working Group P. Koch		Network Working Group P. Koch
	Internet-Draft DENIC eG		Internet-Draft DENIC eG
	Expires: August 30, 2007 February 26, 2007		Intended status: Best Current July 9, 2007
			Practice
			Expires: January 10, 2008
	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-00		draft-ietf-mboned-mcast-arpa-01
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 33		skipping to change at page 1, line 35
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on August 30, 2007.		This Internet-Draft will expire on January 10, 2008.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2007).
	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 that is dedicated to infrastructure support. It
	also provides for a maintenance policy and covers migration issues		also provides for a maintenance policy and covers migration issues
	and caveats.		and caveats. This document updates RFC 3171.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . 3
	1.1. The ARPA top level domain . . . . . . . . . . . . . . . 3		1.1. The ARPA top level domain . . . . . . . . . . . . . . . 3
	2. Current Use . . . . . . . . . . . . . . . . . . . . . . 3		2. Current Use . . . . . . . . . . . . . . . . . . . . . . 3
	3. Registration Policy . . . . . . . . . . . . . . . . . . 3		3. Registration Policy . . . . . . . . . . . . . . . . . . 3
	3.1. Names and Addresses eligible for Registration in		3.1. Names and Addresses eligible for Registration in
	MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 3		MCAST.ARPA . . . . . . . . . . . . . . . . . . . . . . 3
	3.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4		3.2. Subdomains of MCAST.ARPA . . . . . . . . . . . . . . . 4
			3.3. Corresponding Reverse Mapping . . . . . . . . . . . . . 4
	4. Migration Issues . . . . . . . . . . . . . . . . . . . 4		4. Migration Issues . . . . . . . . . . . . . . . . . . . 4
	4.1. Migration Strategies . . . . . . . . . . . . . . . . . 4		4.1. Migration Strategies . . . . . . . . . . . . . . . . . 4
	4.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 4		4.1.1. Freeze . . . . . . . . . . . . . . . . . . . . . . . . 4
	4.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 4		4.1.2. Phase Out . . . . . . . . . . . . . . . . . . . . . . . 5
	4.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 4		4.1.3. Continue . . . . . . . . . . . . . . . . . . . . . . . 5
	5. Security Considerations . . . . . . . . . . . . . . . . 4		5. Security Considerations . . . . . . . . . . . . . . . . 5
	6. IANA Considerations . . . . . . . . . . . . . . . . . . 5		6. IANA Considerations . . . . . . . . . . . . . . . . . . 5
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . 5		7. Acknowledgements . . . . . . . . . . . . . . . . . . . 5
	8. References . . . . . . . . . . . . . . . . . . . . . . 5		8. References . . . . . . . . . . . . . . . . . . . . . . 5
	8.1. Normative References . . . . . . . . . . . . . . . . . 5		8.1. Normative References . . . . . . . . . . . . . . . . . 5
	8.2. Informative References . . . . . . . . . . . . . . . . 5		8.2. Informative References . . . . . . . . . . . . . . . . 6
	Appendix A. Document Revision History . . . . . . . . . . . . . . . 6		Appendix A. Document Revision History . . . . . . . . . . . . . . . 6
	A.1. Initial Document . . . . . . . . . . . . . . . . . . . 6		A.1. Changes from -00 to -01 . . . . . . . . . . . . . . . . 6
	Author's Address . . . . . . . . . . . . . . . . . . . 6		A.2. Initial Document . . . . . . . . . . . . . . . . . . . 7
	Intellectual Property and Copyright Statements . . . . 7		Author's Address . . . . . . . . . . . . . . . . . . . 7
			Intellectual Property and Copyright Statements . . . . 8
	1. Introduction		1. Introduction
	This document describes a maintenance policy and migration strategy		This document describes a maintenance policy and migration strategy
	for the MCAST.NET (MCAST.ARPA) domain that contains names for a		for the MCAST.NET (MCAST.ARPA) domain that contains names for a
	subset of the multicast groups assigned by the IANA.		subset of the multicast groups assigned by the IANA.
	Comments should be sent to the mboned working group.		Comments should be sent to the mboned working group.
	1.1. The ARPA top level domain		1.1. The ARPA top level domain
	skipping to change at page 4, line 5		skipping to change at page 3, line 48
	Names within MCAST.ARPA will consist of one additional label and will		Names within MCAST.ARPA will consist of one additional label and will
	adhere to the hostname syntax requirements of [RFC1123]. These names		adhere to the hostname syntax requirements of [RFC1123]. These names
	will own a single A RR, a single AAAA RR, or both. Addresses will be		will 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.
	3.1. Names and Addresses eligible for Registration in MCAST.ARPA		3.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
			Control Block) and 224.0.1/24 (Internetwork Control Block) will have
			names assigned.
	3.2. Subdomains of MCAST.ARPA		3.2. Subdomains of MCAST.ARPA
	There might be subdomains below MCAST.ARPA that serve special		The namespace under MCAST.ARPA is considered flat, i.e., all direct
	purposes.		descendants of MCAST.ARPA are leaves in the DNS tree. Future
			extensions might want to define subdomains that serve special
			purposes. Any such designation needs IETF consensus [RFC2434].
			3.3. Corresponding Reverse Mapping
			The DNS Reverse Mapping for those multicast groups that appear as
			addresses in MCAST.ARPA is to be kept consistent with the forward
			namespace. 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 name name within MCAST.ARPA.
			The zones 225.IN-ADDR.ARPA through 239.IN-ADDR.ARPA will be delegated
			but shall remain empty (except necessary infrastructure RRs).
			[How to deal with IPv6 multicast reverse mapping is TBD.]
	4. Migration Issues		4. Migration Issues
	The current content of the MCAST.NET zone shall be brought in line		The current content of the MCAST.NET zone shall be brought in line
	with the multicast address registry.		with the multicast address registry.
	Since legacy systems may use MCAST.NET for quite some time, there		Since legacy systems may use MCAST.NET for quite some time, there
	needs to be a mapping/forwarding solution to answer those queries in		needs to be a mapping/forwarding solution to answer those queries in
	a useful manner without discouraging migration.		a useful manner without discouraging migration.
	skipping to change at page 5, line 12		skipping to change at page 5, line 27
	There is no Security Problem associated with the migration itself.		There is no Security Problem associated with the migration itself.
	MCAST.ARPA. should be signed with DNSSEC as soon as the ARPA zone is		MCAST.ARPA. should be signed with DNSSEC as soon as the ARPA zone is
	signed.		signed.
	{This section needs more work.}		{This section needs more work.}
	6. IANA Considerations		6. IANA Considerations
	This document makes a recommendation to IANA.		This document amends [RFC3171] to add a mandatory entry in the
			MCAST.ARPA domain and a corresponding reverse mapping entry. The
	{This section needs more work.}		officially registered multicast group name is made subject to DNS
			hostname syntax rules.
	7. Acknowledgements		7. Acknowledgements
	The author would like to thank David Conrad for his input.		The author would like to thank David Conrad for his input.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",		[RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
	STD 13, RFC 1034, November 1987.		STD 13, RFC 1034, November 1987.
	[RFC1035] Mockapetris, P., "Domain names - implementation and		[RFC1035] Mockapetris, P., "Domain names - implementation and
	specification", STD 13, RFC 1035, November 1987.		specification", STD 13, RFC 1035, November 1987.
	[RFC1123] Braden, R., "Requirements for Internet Hosts - Application		[RFC1123] Braden, R., "Requirements for Internet Hosts - Application
	and Support", STD 3, RFC 1123, October 1989.		and Support", STD 3, RFC 1123, October 1989.
			[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
			IANA Considerations Section in RFCs", BCP 26, RFC 2434,
			October 1998.
	[RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper,		[RFC3171] Albanna, Z., Almeroth, K., Meyer, D., and M. Schipper,
	"IANA Guidelines for IPv4 Multicast Address Assignments",		"IANA Guidelines for IPv4 Multicast Address Assignments",
	BCP 51, RFC 3171, August 2001.		BCP 51, RFC 3171, August 2001.
	[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.
	8.2. Informative References		8.2. Informative References
	skipping to change at page 6, line 23		skipping to change at page 6, line 45
	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.
	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. Initial Document		A.1. Changes from -00 to -01
			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
			requirement for MCAST.ARPA subdomains.
			A.2. 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
	Author's Address		Author's Address
	Peter Koch		Peter Koch
	DENIC eG		DENIC eG
	Wiesenhuettenplatz 26		Wiesenhuettenplatz 26
	Frankfurt 60329		Frankfurt 60329
End of changes. 13 change blocks.
	17 lines changed or deleted		51 lines changed or added
This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/