< draft-ietf-provreg-epp-host-06.txt		draft-ietf-provreg-epp-host-07.txt >
	Internet Engineering Task Force S. Hollenbeck		Internet Engineering Task Force S. Hollenbeck
	Internet-Draft VeriSign, Inc.		Internet-Draft VeriSign, Inc.
	January 29, 2003 Expires: July 29, 2003		April 24, 2003 Expires: October 24, 2003
	Extensible Provisioning Protocol Host Mapping		Extensible Provisioning Protocol Host Mapping
	<draft-ietf-provreg-epp-host-06.txt>		<draft-ietf-provreg-epp-host-07.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with all		This document is an Internet-Draft and is in full conformance with all
	provisions of Section 10 of RFC2026.		provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering Task		Internet-Drafts are working documents of the Internet Engineering Task
	Force (IETF), its areas, and its working groups. Note that other		Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.		groups may also distribute working documents as Internet-Drafts.
	skipping to change at page 6, line 20 ¶		skipping to change at page 6, line 20 ¶
	Coordinated Time (UTC) using the Gregorian calendar. The extended		Coordinated Time (UTC) using the Gregorian calendar. The extended
	date-time form using upper case "T" and "Z" characters defined in		date-time form using upper case "T" and "Z" characters defined in
	[RFC3339] MUST be used to represent date-time values as XML Schema		[RFC3339] MUST be used to represent date-time values as XML Schema
	does not support truncated date-time forms or lower case "T" and "Z"		does not support truncated date-time forms or lower case "T" and "Z"
	characters.		characters.
	2.5 IP Addresses		2.5 IP Addresses
	The syntax for IPv4 addresses described in this document MUST conform		The syntax for IPv4 addresses described in this document MUST conform
	to [RFC791]. The syntax for IPv6 addresses described in this document		to [RFC791]. The syntax for IPv6 addresses described in this document
	MUST conform to [RFC2373]. Practical considerations for publishing		MUST conform to [RFC3513]. Practical considerations for publishing
	IPv6 address information in zone files are documented in [RFC1886],		IPv6 address information in zone files are documented in [RFC1886],
	[RFC2874], and [RFC3152]. A server MAY reject IP addresses that have		[RFC2874], and [RFC3152]. A server MAY reject IP addresses that have
	not been allocated for public use by IANA. When a host object is		not been allocated for public use by IANA. When a host object is
	provisioned for use as a DNS name server, IP addresses SHOULD be		provisioned for use as a DNS name server, IP addresses SHOULD be
	required only as needed to generate DNS glue records.		required only as needed to generate DNS glue records.
	3. EPP Command Mapping		3. EPP Command Mapping
	A detailed description of the EPP syntax and semantics can be found in		A detailed description of the EPP syntax and semantics can be found in
	[EPP]. The command mappings described here are specifically for use		[EPP]. The command mappings described here are specifically for use
	skipping to change at page 30, line 31 ¶		skipping to change at page 30, line 31 ¶
	[RFC1035] P. Mockapetris: "DOMAIN NAMES - IMPLEMENTATION AND		[RFC1035] P. Mockapetris: "DOMAIN NAMES - IMPLEMENTATION AND
	SPECIFICATION", RFC 1035, STD 13, November 1987.		SPECIFICATION", RFC 1035, STD 13, November 1987.
	[RFC1123] R. Braden: "Requirements for Internet Hosts -- Application		[RFC1123] R. Braden: "Requirements for Internet Hosts -- Application
	and Support", RFC 1123, October 1989.		and Support", RFC 1123, October 1989.
	[RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate		[RFC2119] S. Bradner: "Key Words for Use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2373] R. Hinden, S. Deering: "IP Version 6 Addressing
	Architecture", RFC 2373, July 1998.
	[RFC3339] G. Klyne, C. Newman: "Date and Time on the Internet:		[RFC3339] G. Klyne, C. Newman: "Date and Time on the Internet:
	Timestamps", RFC 3339, July 2002.		Timestamps", RFC 3339, July 2002.
			[RFC3513] R. Hinden, S. Deering: "IP Version 6 Addressing
			Architecture", RFC 3513, April 2003.
	[XML] Editor T. Bray et al.: "Extensible Markup Language (XML) 1.0		[XML] Editor T. Bray et al.: "Extensible Markup Language (XML) 1.0
	(Second Edition)", W3C Recommendation 6 October 2000.		(Second Edition)", W3C Recommendation 6 October 2000.
	[XMLS-1] Editors H. Thompson et al.: "XML Schema Part 1: Structures",		[XMLS-1] Editors H. Thompson et al.: "XML Schema Part 1: Structures",
	W3C Recommendation 2 May 2001.		W3C Recommendation 2 May 2001.
	[XMLS-2] Editors P. Biron, A. Malhotra: "XML Schema Part 2:		[XMLS-2] Editors P. Biron, A. Malhotra: "XML Schema Part 2:
	Datatypes", W3C Recommendation 2 May 2001.		Datatypes", W3C Recommendation 2 May 2001.
	Informative References:		Informative References:
	skipping to change at page 32, line 10 ¶		skipping to change at page 32, line 10 ¶
	21345 Ridgetop Circle		21345 Ridgetop Circle
	Dulles, VA 20166-6503		Dulles, VA 20166-6503
	USA		USA
	shollenbeck@verisign.com		shollenbeck@verisign.com
	A. Revisions From Previous Version		A. Revisions From Previous Version
	(Note to RFC editor: please remove this section completely before		(Note to RFC editor: please remove this section completely before
	publication as an RFC.)		publication as an RFC.)
	-05 to -06 (IESG review):		-06 to -07 (IESG review):
	Changed domain name examples throughout to use conventions described
	in RFC 2606 (BCP 32).
	Removed "This document is being discussed" paragraph from section 1.
	Reworded the description of external hosts in section 1.1 and added a
	new paragraph with an example.
	Added a new sentence to the second paragraph of section 2.3 and
	clarified how "ok" status is set.
	Modified text in sections 1.1 and 3.2.5 to update external host
	processing.
	Fixed schema in section 4 to note that the maximum number of status
	values that can be set at once is 7, not 6.
	Slight rewording of the last sentence of the first paragraph in		Updated references to use RFC 3513 instead of 2373. 3513 obsoletes
	section 5.		2373.
	B. Full Copyright Statement		B. Full Copyright Statement
	Copyright (C) The Internet Society 2002. All Rights Reserved.		Copyright (C) The Internet Society 2003. All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published and		or assist in its implementation may be prepared, copied, published and
	distributed, in whole or in part, without restriction of any kind,		distributed, in whole or in part, without restriction of any kind,
	provided that the above copyright notice and this paragraph are		provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of developing		Internet organizations, except as needed for the purpose of developing
End of changes. 8 change blocks.
	27 lines changed or deleted		10 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/