draft-ietf-regext-validate-02.txt		draft-ietf-regext-validate-03.txt
	Registration Protocols Extensions R. Carney		Registration Protocols Extensions R. Carney
	Internet-Draft J. Snitker		Internet-Draft J. Snitker
	Intended status: Standards Track GoDaddy Inc.		Intended status: Standards Track GoDaddy Inc.
	Expires: February 4, 2018 August 3, 2017		Expires: August 6, 2018 February 2, 2018
	Validate Mapping for the Extensible Provisioning Protocol (EPP)		Validate Mapping for the Extensible Provisioning Protocol (EPP)
	draft-ietf-regext-validate-02		draft-ietf-regext-validate-03
	Abstract		Abstract
	This document describes an Extensible Provisioning Protocol (EPP)		This document describes an Extensible Provisioning Protocol (EPP)
	mapping for the validation of contact and eligibility data.		mapping for the validation of contact and eligibility data.
	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 https://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 February 4, 2018.		This Internet-Draft will expire on August 6, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2018 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		(https://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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	skipping to change at page 2, line 31 ¶		skipping to change at page 2, line 31 ¶
	3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 8		3.2.5. EPP <update> Command . . . . . . . . . . . . . . . . 8
	4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 8		4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 8
	4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8		4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 11		5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11		6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11
	7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 12		7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 12
	7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 12		7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 12
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
	9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12		9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12
	9.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 12		9.1. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 12
	9.2. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 13		9.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 13
	9.3. Change from carney-regext 01 to ietf-regext 00 . . . . . 13		9.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 13
			9.4. Change from carney-regext 01 to ietf-regext 00 . . . . . 13
	10. Normative References . . . . . . . . . . . . . . . . . . . . 13		10. Normative References . . . . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
	1. Introduction		1. Introduction
	This document describes a Validate mapping for version 1.0 of the		This document describes a Validate mapping for version 1.0 of the
	Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping		Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping
	specifies a flexible schema by which EPP clients and servers can		specifies a flexible schema by which EPP clients and servers can
	reliably validate contact and eligibility data.		reliably validate contact and eligibility data.
	skipping to change at page 12, line 45 ¶		skipping to change at page 12, line 45 ¶
	The authors wish to thank the following persons for their feedback		The authors wish to thank the following persons for their feedback
	and suggestions:		and suggestions:
	o Kevin Allendorf of GoDaddy Inc.		o Kevin Allendorf of GoDaddy Inc.
	o Jody Kolker of GoDaddy Inc.		o Jody Kolker of GoDaddy Inc.
	o James Gould of Verisign Inc		o James Gould of Verisign Inc
	9. Change History		9. Change History
	9.1. Change from 00 to 01		9.1. Change from 02 to 03
	Corrected some formatting issues		Corrected some formatting issues.
	9.2. Change from 00 to 01		9.2. Change from 01 to 02
			Corrected some formatting issues.
			9.3. Change from 00 to 01
	After review and broad feedback, extensive changes have been made		After review and broad feedback, extensive changes have been made
	transforming the original document from a standalone extension		transforming the original document from a standalone extension
	command to using the <check> command and response framework. Stubbed		command to using the <check> command and response framework. Stubbed
	in an Implementation section for later documentation.		in an Implementation section for later documentation.
	9.3. Change from carney-regext 01 to ietf-regext 00		9.4. Change from carney-regext 01 to ietf-regext 00
	Updated miscellaneous verbiage to reflect the change from an		Updated miscellaneous verbiage to reflect the change from an
	extension and changed to ietf naming as REGEXT WG will assume this		extension and changed to ietf naming as REGEXT WG will assume this
	work.		work.
	10. Normative References		10. Normative References
	[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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	DOI 10.17487/RFC3688, January 2004,		DOI 10.17487/RFC3688, January 2004,
	<http://www.rfc-editor.org/info/rfc3688>.		<https://www.rfc-editor.org/info/rfc3688>.
	[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",		[RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
	STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,		STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
	<http://www.rfc-editor.org/info/rfc5730>.		<https://www.rfc-editor.org/info/rfc5730>.
	Authors' Addresses		Authors' Addresses
	Roger Carney		Roger Carney
	GoDaddy Inc.		GoDaddy Inc.
	14455 N. Hayden Rd. #219		14455 N. Hayden Rd. #219
	Scottsdale, AZ 85260		Scottsdale, AZ 85260
	US		US
	Email: rcarney@godaddy.com		Email: rcarney@godaddy.com
End of changes. 14 change blocks.
	16 lines changed or deleted		21 lines changed or added
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/