rfc9803v1.txt		rfc9803.txt
	skipping to change at line 184 ¶		skipping to change at line 184 ¶
	"custom"		"custom"
	If the value of the "for" attribute is "custom", then the		If the value of the "for" attribute is "custom", then the
	<ttl:ttl> element MUST also have a "custom" attribute containing a		<ttl:ttl> element MUST also have a "custom" attribute containing a
	DNS record type conforming with the regular expression in		DNS record type conforming with the regular expression in
	Section 3.1 of [RFC6895]. Additionally, the record type MUST be		Section 3.1 of [RFC6895]. Additionally, the record type MUST be
	registered with IANA in [IANA-RRTYPES].		registered with IANA in [IANA-RRTYPES].
	"min"		"min"
	MUST NOT be present in EPP commands but MAY be present in EPP		MUST NOT be present in EPP commands but MAY be present in EPP
	responses (see Section 2.1.1). It is also used by the server to		responses (see Section 2.1.1). It is used by the server to
	indicate the lowest value that may be set.		indicate the lowest value that may be set.
	"default"		"default"
	MUST NOT be present in EPP commands but MAY be present in EPP		MUST NOT be present in EPP commands but MAY be present in EPP
	responses (see Section 2.1.1). It is also used by the server to		responses (see Section 2.1.1). It is used by the server to
	indicate the default value.		indicate the default value.
	"max"		"max"
	MUST NOT be present in EPP commands but MAY be present in EPP		MUST NOT be present in EPP commands but MAY be present in EPP
	responses (see Section 2.1.1). It is also used by the server to		responses (see Section 2.1.1). It is used by the server to
	indicate the highest value that may be set.		indicate the highest value that may be set.
	When present, the value of the "min" attribute MUST be lower than the		When present, the value of the "min" attribute MUST be lower than the
	value of the "max" attribute. The "default" attribute MUST be		value of the "max" attribute. The "default" attribute MUST be
	between the "min" and "max" values, inclusively.		between the "min" and "max" values, inclusively.
	1.2.1.1. Element Content		1.2.1.1. Element Content
	The XML schema found in Section 8 of this document restricts the		The XML schema found in Section 8 of this document restricts the
	content of <ttl:ttl> elements to be either:		content of <ttl:ttl> elements to be either:
	skipping to change at line 272 ¶		skipping to change at line 272 ¶
	The <ttl:info> element is used by clients to request that the server		The <ttl:info> element is used by clients to request that the server
	include additional information in <info> responses for domain and		include additional information in <info> responses for domain and
	host objects.		host objects.
	It has a single OPTIONAL "policy" attribute, which takes a boolean		It has a single OPTIONAL "policy" attribute, which takes a boolean
	value with a default value of "false".		value with a default value of "false".
	The semantics of this element are described in Section 2.1.1.		The semantics of this element are described in Section 2.1.1.
	1.2.1.3.1. Example		Below is an example of a <ttl:info> element with an explicit "policy"
			attribute:
	<ttl:info policy="true"/>		<ttl:info policy="true"/>
	1.2.2. Examples		1.2.2. Examples
	1.2.2.1. Explicit TTL Value (<create> or <update> Command)		1.2.2.1. Explicit TTL Value (<create> or <update> Command)
	<ttl:ttl for="NS">3600</ttl:ttl>		<ttl:ttl for="NS">3600</ttl:ttl>
	1.2.2.2. Explicit TTL Value (<info> Policy Mode)		1.2.2.2. Explicit TTL Value (<info> Policy Mode)
	skipping to change at line 610 ¶		skipping to change at line 611 ¶
	2.2.1. EPP <create> Command		2.2.1. EPP <create> Command
	This extension defines an additional element for EPP <create>		This extension defines an additional element for EPP <create>
	commands for domain and host objects.		commands for domain and host objects.
	The <command> element of the <create> command MAY contain an		The <command> element of the <create> command MAY contain an
	<extension> element that MAY contain a <ttl:create> element. This		<extension> element that MAY contain a <ttl:create> element. This
	element MUST contain one or more <ttl:ttl> records as described in		element MUST contain one or more <ttl:ttl> records as described in
	Section 1.2.		Section 1.2.
			If an EPP server receives a <create> command containing a TTL value
			that is outside the server's permitted range, it MUST reject the
			command with a 2004 "Parameter value range error" response.
	Below is an example domain <create> command:		Below is an example domain <create> command:
	C: <?xml version="1.0" encoding="UTF-8" standalone="no"?>		C: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">		C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>		C: <command>
	C: <create>		C: <create>
	C: <domain:create		C: <domain:create
	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">		C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	C: <domain:name>example.com</domain:name>		C: <domain:name>example.com</domain:name>
	C: <domain:period unit="y">1</domain:period>		C: <domain:period unit="y">1</domain:period>
	skipping to change at line 673 ¶		skipping to change at line 678 ¶
	C: <ttl:create		C: <ttl:create
	C: xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0">		C: xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0">
	C: <ttl:ttl for="A"/>		C: <ttl:ttl for="A"/>
	C: <ttl:ttl for="AAAA">86400</ttl:ttl>		C: <ttl:ttl for="AAAA">86400</ttl:ttl>
	C: </ttl:create>		C: </ttl:create>
	C: </extension>		C: </extension>
	C: <clTRID>ABC-12345</clTRID>		C: <clTRID>ABC-12345</clTRID>
	C: </command>		C: </command>
	C: </epp>		C: </epp>
	If an EPP server receives a <create> command containing a TTL value
	that is outside the server's permitted range, it MUST reject the
	command with a 2004 "Parameter value range error" response.
	2.2.2. EPP <update> Command		2.2.2. EPP <update> Command
	This extension defines an additional element for EPP <update>		This extension defines an additional element for EPP <update>
	commands for domain and host objects.		commands for domain and host objects.
	The <command> element of the <update> command MAY contain an		The <command> element of the <update> command MAY contain an
	<extension> element that MAY contain a <ttl:update> element. This		<extension> element that MAY contain a <ttl:update> element. This
	element MUST contain one or more <ttl:ttl> records as described in		element MUST contain one or more <ttl:ttl> records as described in
	Section 1.2.		Section 1.2.
			If an EPP server receives an <update> command containing a TTL value
			that is outside the server's permitted range, it MUST reject the
			command with a 2004 "Parameter value range error" response.
	Below is an example domain <update> command:		Below is an example domain <update> command:
	C: <?xml version="1.0" encoding="UTF-8" standalone="no"?>		C: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
	C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">		C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
	C: <command>		C: <command>
	C: <update>		C: <update>
	C: <domain:update		C: <domain:update
	C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">		C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
	C: <domain:name>example.com</domain:name>		C: <domain:name>example.com</domain:name>
	C: </domain:update>		C: </domain:update>
	skipping to change at line 733 ¶		skipping to change at line 738 ¶
	C: <ttl:update		C: <ttl:update
	C: xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0">		C: xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0">
	C: <ttl:ttl for="A">86400</ttl:ttl>		C: <ttl:ttl for="A">86400</ttl:ttl>
	C: <ttl:ttl for="AAAA">3600</ttl:ttl>		C: <ttl:ttl for="AAAA">3600</ttl:ttl>
	C: </ttl:update>		C: </ttl:update>
	C: </extension>		C: </extension>
	C: <clTRID>ABC-12345</clTRID>		C: <clTRID>ABC-12345</clTRID>
	C: </command>		C: </command>
	C: </epp>		C: </epp>
	If an EPP server receives an <update> command containing a TTL value
	that is outside the server's permitted range, it MUST reject the
	command with a 2004 "Parameter value range error" response.
	3. Server Processing of TTL Values		3. Server Processing of TTL Values
	3.1. Permitted Record Types		3.1. Permitted Record Types
	EPP servers MAY restrict the supported DNS record types. For		EPP servers MAY restrict the supported DNS record types. For
	example, a server MAY allow clients to specify TTL values for DS		example, a server MAY allow clients to specify TTL values for DS
	records only.		records only.
	A server that receives a <create> or <update> command that includes a		A server that receives a <create> or <update> command that includes a
	restricted record type MUST respond with a 2306 "Parameter value		restricted record type MUST respond with a 2306 "Parameter value
	skipping to change at line 865 ¶		skipping to change at line 866 ¶
	7. IANA Considerations		7. IANA Considerations
	7.1. XML Namespace		7.1. XML Namespace
	This document uses URNs to describe XML namespaces and XML schemas		This document uses URNs to describe XML namespaces and XML schemas
	conforming to a registry mechanism described in [RFC3688]. The		conforming to a registry mechanism described in [RFC3688]. The
	following URI assignments have been made by IANA:		following URI assignments have been made by IANA:
	Registration for the TTL namespace:		Registration for the TTL namespace:
	*URI:* urn:ietf:params:xml:ns:epp:ttl-1.0		URI: urn:ietf:params:xml:ns:epp:ttl-1.0
	*Registrant Contact:* IESG		Registrant Contact: IESG
	*XML:* None. Namespace URIs do not represent an XML specification.		XML: None. Namespace URIs do not represent an XML specification.
	Registration for the TTL XML schema:		Registration for the TTL XML schema:
	*URI:* urn:ietf:params:xml:schema:epp:ttl-1.0		URI: urn:ietf:params:xml:schema:epp:ttl-1.0
	*Registrant Contact:* IESG		Registrant Contact: IESG
	*XML:* See Section 8 of this document.		XML: See Section 8 of this document.
	7.2. EPP Extension Registry		7.2. EPP Extension Registry
	The EPP extension described in this document has been registered by		The EPP extension described in this document has been registered by
	IANA in the "Extensions for the Extensible Provisioning Protocol		IANA in the "Extensions for the Extensible Provisioning Protocol
	(EPP)" registry described in [RFC7451]. The details of the		(EPP)" registry described in [RFC7451]. The details of the
	registration are as follows:		registration are as follows:
	*Name of Extension:* Extensible Provisioning Protocol (EPP) Mapping		Name of Extension: Extensible Provisioning Protocol (EPP) Mapping
	for DNS Time-To-Live (TTL) values		for DNS Time-to-Live (TTL) Values
	*Document Status:* Standards Track		Document Status: Standards Track
	*Reference:* RFC 9803		Reference: RFC 9803
	*Registrant:* IESG		Registrant: IESG
	*TLDs:* Any		TLDs: Any
	*IPR Disclosure:* None		IPR Disclosure: None
	*Status:* Active		Status: Active
	*Notes:* None		Notes: None
	8. Formal Syntax		8. Formal Syntax
	The formal syntax presented here is a complete schema representation		The formal syntax presented here is a complete schema representation
	of the extension suitable for automated validation of EPP XML		of the extension suitable for automated validation of EPP XML
	instances.		instances.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<schema		<schema
	xmlns="http://www.w3.org/2001/XMLSchema"		xmlns="http://www.w3.org/2001/XMLSchema"
	targetNamespace="urn:ietf:params:xml:ns:epp:ttl-1.0"		targetNamespace="urn:ietf:params:xml:ns:epp:ttl-1.0"
	xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"		xmlns:ttl="urn:ietf:params:xml:ns:epp:ttl-1.0"
	elementFormDefault="qualified">		elementFormDefault="qualified">
	<annotation>		<annotation>
	<documentation>		<documentation>
	Extensible Provisioning Protocol v1.0 extension		Extensible Provisioning Protocol v1.0 extension
	schema for Time-To-Live (TTL) values for domain		schema for Time-to-Live (TTL) Values for domain
	and host objects.		and host objects.
	</documentation>		</documentation>
	</annotation>		</annotation>
	<element name="info">		<element name="info">
	<complexType>		<complexType>
	<attribute name="policy" type="boolean" default="false"/>		<attribute name="policy" type="boolean" default="false"/>
	</complexType>		</complexType>
	</element>		</element>
End of changes. 12 change blocks.
	28 lines changed or deleted		29 lines changed or added
This html diff was produced by rfcdiff 1.48.