rfc9038v2.txt		rfc9038.txt
	skipping to change at line 192 ¶		skipping to change at line 192 ¶
	The unhandled namespace MUST be declared in the child element or		The unhandled namespace MUST be declared in the child element or
	any containing element, including the root element. XML		any containing element, including the root element. XML
	processing of the <value> element is disabled by the XML schema		processing of the <value> element is disabled by the XML schema
	in [RFC5730], so the information can safely be returned in the		in [RFC5730], so the information can safely be returned in the
	<value> element.		<value> element.
	<reason>: A formatted, human-readable message that indicates the		<reason>: A formatted, human-readable message that indicates the
	reason the unhandled namespace data was not returned in the		reason the unhandled namespace data was not returned in the
	appropriate location of the response. The formatted reason		appropriate location of the response. The formatted reason
	SHOULD follow the Augmented Backus-Naur Form (ABNF) grammar		SHOULD follow the Augmented Backus-Naur Form (ABNF) grammar
	[RFC5234] format: NAMESPACE-URI "not in login services", where		[RFC5234] format: NAMESPACE-URI " not in login services", where
	NAMESPACE-URI is the unhandled XML namespace like		NAMESPACE-URI is the unhandled XML namespace like
	"urn:ietf:params:xml:ns:domain-1.0" in [RFC5731].		"urn:ietf:params:xml:ns:domain-1.0" in [RFC5731].
	This document applies to the handling of unsupported namespaces for		This document applies to the handling of unsupported namespaces for
	object-level extensions and command-response extensions [RFC3735].		object-level extensions and command-response extensions [RFC3735].
	This document does not apply to the handling of unsupported		This document does not apply to the handling of unsupported
	namespaces for protocol-level extensions or authentication-		namespaces for protocol-level extensions or authentication-
	information extensions [RFC3735]. Refer to the following sections on		information extensions [RFC3735]. Refer to the following sections on
	how to handle an unsupported object-level extension namespace or an		how to handle an unsupported object-level extension namespace or an
	unsupported command-response extension namespace.		unsupported command-response extension namespace.
	skipping to change at line 763 ¶		skipping to change at line 763 ¶
	TLDs: Any		TLDs: Any
	IPR Disclosure: None		IPR Disclosure: None
	Status: Active		Status: Active
	Notes: None		Notes: None
	9. Security Considerations		9. Security Considerations
	This document does not provide any security services beyond those		This document does not provide any security services beyond those
	described by EPP [RFC5730] and protocol layers used by EPP. The		described by EPP [RFC5730] and protocol layers used by EPP. The
	security considerations described in these other specifications apply		security considerations described in these other specifications apply
	to this specification as well. Since the unhandled namespace context		to this specification as well. Since the unhandled namespace content
	is XML that is not processed in the first pass by the XML parser, the		is XML that is not processed in the first pass by the XML parser, the
	client SHOULD validate the XML when the content is processed to		client SHOULD validate the XML when the content is processed to
	protect against the inclusion of malicious content.		protect against the inclusion of malicious content.
	10. References		10. References
	10.1. Normative References		10.1. 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,
	skipping to change at line 848 ¶		skipping to change at line 848 ¶
	Authors' Addresses		Authors' Addresses
	James Gould		James Gould
	VeriSign, Inc.		VeriSign, Inc.
	12061 Bluemont Way		12061 Bluemont Way
	Reston, VA 20190		Reston, VA 20190
	United States of America		United States of America
	Email: jgould@verisign.com		Email: jgould@verisign.com
	URI: http://www.verisigninc.com		URI: http://www.verisign.com
	Martin Casanova		Martin Casanova
	SWITCH		SWITCH
	P.O. Box		P.O. Box
	CH-8021 Zurich		CH-8021 Zurich
	Switzerland		Switzerland
	Email: martin.casanova@switch.ch		Email: martin.casanova@switch.ch
	URI: http://www.switch.ch		URI: http://www.switch.ch
End of changes. 3 change blocks.
	3 lines changed or deleted		3 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/