< draft-hollenbeck-epp-rfc3733bis-05.txt		draft-hollenbeck-epp-rfc3733bis-06.txt >
	Network Working Group S. Hollenbeck		Network Working Group S. Hollenbeck
	Internet-Draft VeriSign, Inc.		Internet-Draft VeriSign, Inc.
	Obsoletes: 3733 (if approved) November 17, 2006		Obsoletes: 3733 (if approved) January 9, 2007
	Intended status: Standards Track		Intended status: Standards Track
	Expires: May 21, 2007		Expires: July 13, 2007
	Extensible Provisioning Protocol (EPP) Contact Mapping		Extensible Provisioning Protocol (EPP) Contact Mapping
	draft-hollenbeck-epp-rfc3733bis-05.txt		draft-hollenbeck-epp-rfc3733bis-06.txt
	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 35 ¶		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 May 21, 2007.		This Internet-Draft will expire on July 13, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The IETF Trust (2006).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document describes an Extensible Provisioning Protocol (EPP)		This document describes an Extensible Provisioning Protocol (EPP)
	mapping for the provisioning and management of individual or		mapping for the provisioning and management of individual or
	organizational social information identifiers (known as "contacts")		organizational social information identifiers (known as "contacts")
	stored in a shared central repository. Specified in Extensible		stored in a shared central repository. Specified in Extensible
	Markup Language (XML), the mapping defines EPP command syntax and		Markup Language (XML), the mapping defines EPP command syntax and
	semantics as applied to contacts. This document obsoletes RFC 3733		semantics as applied to contacts. This document obsoletes RFC 3733
	if approved.		if approved.
	skipping to change at page 2, line 41 ¶		skipping to change at page 2, line 41 ¶
	3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 21		3.2.4. EPP <transfer> Command . . . . . . . . . . . . . . . . 21
	3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 23		3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . . 23
	3.3. Offline Review of Requested Actions . . . . . . . . . . . 27		3.3. Offline Review of Requested Actions . . . . . . . . . . . 27
	4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 29		4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 29
	5. Internationalization Considerations . . . . . . . . . . . . . 38		5. Internationalization Considerations . . . . . . . . . . . . . 38
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 39		7. Security Considerations . . . . . . . . . . . . . . . . . . . 39
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 39		9.1. Normative References . . . . . . . . . . . . . . . . . . . 39
	9.2. Informative References . . . . . . . . . . . . . . . . . . 41		9.2. Informative References . . . . . . . . . . . . . . . . . . 40
	Appendix A. Changes from RFC 3733 . . . . . . . . . . . . . . . . 41		Appendix A. Changes from RFC 3733 . . . . . . . . . . . . . . . . 41
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 42		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 42
	Intellectual Property and Copyright Statements . . . . . . . . . . 43		Intellectual Property and Copyright Statements . . . . . . . . . . 43
	1. Introduction		1. Introduction
	This document describes a personal and organizational identifier		This document describes a personal and organizational identifier
	mapping for version 1.0 of the Extensible Provisioning Protocol		mapping for version 1.0 of the Extensible Provisioning Protocol
	(EPP). This mapping is specified using the Extensible Markup		(EPP). This mapping is specified using the Extensible Markup
	Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML		Language (XML) 1.0 as described in [W3C.REC-xml-20040204] and XML
	skipping to change at page 6, line 27 ¶		skipping to change at page 6, line 27 ¶
	length.		length.
	2.4.3. Country		2.4.3. Country
	Contact country identifiers are represented using two-character		Contact country identifiers are represented using two-character
	identifiers specified in [ISO.3166.1997].		identifiers specified in [ISO.3166.1997].
	2.5. Telephone Numbers		2.5. Telephone Numbers
	Contact telephone number structure is derived from structures defined		Contact telephone number structure is derived from structures defined
	in [ITU.E164.2006]. Telephone numbers described in this mapping are		in [ITU.E164.2005]. Telephone numbers described in this mapping are
	character strings that MUST begin with a plus sign ("+", ASCII value		character strings that MUST begin with a plus sign ("+", ASCII value
	0x002B), followed by a country code defined in [ITU.E164.2006],		0x002B), followed by a country code defined in [ITU.E164.2005],
	followed by a dot (".", ASCII value 0x002E), followed by a sequence		followed by a dot (".", ASCII value 0x002E), followed by a sequence
	of digits representing the telephone number. An optional "x"		of digits representing the telephone number. An optional "x"
	attribute is provided to note telephone extension information.		attribute is provided to note telephone extension information.
	2.6. Email Addresses		2.6. Email Addresses
	Email address syntax is defined in [RFC0822]. This mapping does not		Email address syntax is defined in [RFC0822]. This mapping does not
	prescribe minimum or maximum lengths for character strings used to		prescribe minimum or maximum lengths for character strings used to
	represent email addresses.		represent email addresses.
	skipping to change at page 38, line 13 ¶		skipping to change at page 38, line 13 ¶
	END		END
	5. Internationalization Considerations		5. Internationalization Considerations
	EPP is represented in XML, which provides native support for encoding		EPP is represented in XML, which provides native support for encoding
	information using the Unicode character set and its more compact		information using the Unicode character set and its more compact
	representations, including UTF-8. Conformant XML processors		representations, including UTF-8. Conformant XML processors
	recognize both UTF-8 and UTF-16 [RFC2781]. Though XML includes		recognize both UTF-8 and UTF-16 [RFC2781]. Though XML includes
	provisions to identify and use other character encodings through use		provisions to identify and use other character encodings through use
	of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is		of an "encoding" attribute in an <?xml?> declaration, use of UTF-8 is
	RECOMMENDED in environments where parser encoding support		REQUIRED with this specification.
	incompatibility exists.
	All date-time values presented via EPP MUST be expressed in Universal		All date-time values presented via EPP MUST be expressed in Universal
	Coordinated Time using the Gregorian calendar. The XML Schema allows		Coordinated Time using the Gregorian calendar. The XML Schema allows
	use of time zone identifiers to indicate offsets from the zero		use of time zone identifiers to indicate offsets from the zero
	meridian, but this option MUST NOT be used with EPP. The extended		meridian, but this option MUST NOT be used with EPP. 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
	[W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time		[W3C.REC-xmlschema-2-20041028] MUST be used to represent date-time
	values as the XML Schema does not support truncated date-time forms		values as the XML Schema does not support truncated date-time forms
	or lower case "T" and "Z" characters.		or lower case "T" and "Z" characters.
	skipping to change at page 40, line 11 ¶		skipping to change at page 40, line 8 ¶
	Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",		Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
	draft-hollenbeck-epp-rfc3730bis-04 (work in progress),		draft-hollenbeck-epp-rfc3730bis-04 (work in progress),
	November 2006.		November 2006.
	[ISO.3166.1997]		[ISO.3166.1997]
	International Organization for Standardization, "Codes for		International Organization for Standardization, "Codes for
	the representation of names of countries and their		the representation of names of countries and their
	subdivisions -- Part 1: Country codes", ISO Standard 3166,		subdivisions -- Part 1: Country codes", ISO Standard 3166,
	October 1997.		October 1997.
	[ITU.E164.2006]		[ITU.E164.2005]
	International Telephone and Telegraph Consultative		International Telecommunication Union, "The international
	Committee, "Criteria and procedures for the reservation,		public telecommunication numbering plan", ITU-
	assignment and reclamation of E.164 country codes and		T Recommendation E.164, February 2005.
	associated identification codes (ICs)", ITU Recommendation
	E.164, May 2006.
	[RFC0822] Crocker, D., "Standard for the format of ARPA Internet		[RFC0822] Crocker, D., "Standard for the format of ARPA Internet
	text messages", STD 11, RFC 822, August 1982.		text messages", STD 11, RFC 822, August 1982.
	[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.
	[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO		[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
	10646", STD 63, RFC 3629, November 2003.		10646", STD 63, RFC 3629, November 2003.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	January 2004.		January 2004.
	[W3C.REC-xml-20040204]		[W3C.REC-xml-20040204]
	Paoli, J., Maler, E., Sperberg-McQueen, C., Bray, T., and		Maler, E., Sperberg-McQueen, C., Bray, T., Yergeau, F.,
	F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third		and J. Paoli, "Extensible Markup Language (XML) 1.0 (Third
	Edition)", World Wide Web Consortium Recommendation REC-		Edition)", World Wide Web Consortium FirstEdition REC-xml-
	xml-20040204, February 2004,		20040204, February 2004,
	<http://www.w3.org/TR/2004/REC-xml-20040204>.		<http://www.w3.org/TR/2004/REC-xml-20040204>.
	[W3C.REC-xmlschema-1-20041028]		[W3C.REC-xmlschema-1-20041028]
	Beech, D., Thompson, H., Maloney, M., and N. Mendelsohn,		Beech, D., Thompson, H., Maloney, M., and N. Mendelsohn,
	"XML Schema Part 1: Structures Second Edition", World Wide		"XML Schema Part 1: Structures Second Edition", World Wide
	Web Consortium Recommendation REC-xmlschema-1-20041028,		Web Consortium Recommendation REC-xmlschema-1-20041028,
	October 2004,		October 2004,
	<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.		<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
	[W3C.REC-xmlschema-2-20041028]		[W3C.REC-xmlschema-2-20041028]
	skipping to change at page 42, line 14 ¶		skipping to change at page 42, line 5 ¶
	"The server operator reviews the request offline, and informs		"The server operator reviews the request offline, and informs
	the client of the outcome of the review by either queuing a		the client of the outcome of the review by either queuing a
	service message for retrieval via the <poll> command or by using		service message for retrieval via the <poll> command or by using
	an out-of-band mechanism to inform the client of the request."		an out-of-band mechanism to inform the client of the request."
	8. Removed text describing use of the XML Schema schemaLocation		8. Removed text describing use of the XML Schema schemaLocation
	attribute. This is an optional attribute that doesn't need to		attribute. This is an optional attribute that doesn't need to
	be mandated for use in EPP.		be mandated for use in EPP.
	9. Removed references to RFC 3339 and replaced them with references		9. Updated text describing a requirement to use UTF-8 encoding in
			the "Internationalization Considerations" section.
			10. Removed references to RFC 3339 and replaced them with references
	to the W3C XML Schema specification.		to the W3C XML Schema specification.
	10. Updated EPP and XML references. Updated reference from RFC 2279		11. Updated the E.164 reference.
			12. Updated EPP and XML references. Updated reference from RFC 2279
	to RFC 3629.		to RFC 3629.
	Author's Address		Author's Address
	Scott Hollenbeck		Scott Hollenbeck
	VeriSign, Inc.		VeriSign, Inc.
	21345 Ridgetop Circle		21345 Ridgetop Circle
	Dulles, VA 20166-6503		Dulles, VA 20166-6503
	US		US
	Email: shollenbeck@verisign.com		Email: shollenbeck@verisign.com
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2006).		Copyright (C) The IETF Trust (2007).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
End of changes. 14 change blocks.
	23 lines changed or deleted		25 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/