rfc9361v2.txt		rfc9361.txt
	skipping to change at line 125 ¶		skipping to change at line 125 ¶
	9. Security Considerations		9. Security Considerations
	10. Privacy Considerations		10. Privacy Considerations
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	11.2. Informative References		11.2. Informative References
	Acknowledgements		Acknowledgements
	Author's Address		Author's Address
	1. Introduction		1. Introduction
	Domain Name Registries (DNRs) may operate in special modes for		Domain Name Registries may operate in special modes for certain
	certain periods of time, enabling Trademark Holders to protect their		periods of time, enabling Trademark Holders to protect their rights
	rights during the introduction of a Top-Level Domain (TLD).		during the introduction of a Top-Level Domain (TLD).
	Along with the introduction of new generic TLDs (gTLDs), two special		Along with the introduction of new generic TLDs (gTLDs), two special
	modes came into effect:		modes came into effect:
	* Sunrise Period: The Sunrise Period allows Trademark Holders an		* Sunrise Period: The Sunrise Period allows Trademark Holders an
	advance opportunity to register domain names corresponding to		advance opportunity to register domain names corresponding to
	their marks before names are generally available to the public.		their marks before names are generally available to the public.
	* Trademark Claims Period: The Trademark Claims Period follows the		* Trademark Claims Period: The Trademark Claims Period follows the
	Sunrise Period and runs for at least the first 90 days of an		Sunrise Period and runs for at least the first 90 days of an
	skipping to change at line 1045 ¶		skipping to change at line 1045 ¶
	by ICANN policy. In the gTLD round of 2012, Registrars		by ICANN policy. In the gTLD round of 2012, Registrars
	verified that the acceptance datetime was less than or equal		verified that the acceptance datetime was less than or equal
	to 48 hours in the past, as there were no defined ICANN		to 48 hours in the past, as there were no defined ICANN
	policies at that time. Implementers should be aware that		policies at that time. Implementers should be aware that
	ICANN policy may define this value in the future.		ICANN policy may define this value in the future.
	4. The TCN Checksum is computed using the leftmost DNL of the DN		4. The TCN Checksum is computed using the leftmost DNL of the DN
	being effectively allocated, the expiration datetime provided		being effectively allocated, the expiration datetime provided
	by the Registrar, and the TMDB Notice Identifier extracted		by the Registrar, and the TMDB Notice Identifier extracted
	from the TCNID provided by the Registrar. Verify that the		from the TCNID provided by the Registrar. Verify that the
	computed TCN Cheksum matches the TCN Checksum present in the		computed TCN Checksum matches the TCN Checksum present in the
	TCNID. For example, if the DN "xn--mgbachtv.xn--mgbh0fb" is		TCNID. For example, if the DN "xn--mgbachtv.xn--mgbh0fb" is
	being effectively allocated, the leftmost DNL would be "xn--		being effectively allocated, the leftmost DNL would be "xn--
	mgbachtv".		mgbachtv".
	These procedures apply to all DN registrations at the second level,		These procedures apply to all DN registrations at the second level,
	as well as to all other levels subordinate to the TLD that the		as well as to all other levels subordinate to the TLD that the
	Registry accepts registrations for.		Registry accepts registrations for.
	5.3.3. TMDB Trademark Claims Services for Registries		5.3.3. TMDB Trademark Claims Services for Registries
	skipping to change at line 1694 ¶		skipping to change at line 1694 ¶
	EK77-REP,example2.gtld,a7b786ed9223372036856775808,\		EK77-REP,example2.gtld,a7b786ed9223372036856775808,\
	9999,2012-08-15T11:20:00.0Z,2012-08-15T11:19:00.0Z		9999,2012-08-15T11:20:00.0Z,2012-08-15T11:19:00.0Z
	HB800-REP,example3.gtld,recent-dnl-insertion,\		HB800-REP,example3.gtld,recent-dnl-insertion,\
	9999,2012-08-15T13:20:00.0Z,recent-dnl-insertion		9999,2012-08-15T13:20:00.0Z,recent-dnl-insertion
	Figure 13: Example Trademark Claims LORDN File		Figure 13: Example Trademark Claims LORDN File
	6.3.1. LORDN Log File		6.3.1. LORDN Log File
	After reception of the LORDN file, the TMDB verifies its content for		After reception of the LORDN file, the TMDB verifies its content for
	syntactical and semantical correctness. The output of the LORDN file		syntactical and semantic correctness. The output of the LORDN file
	verification is retrieved using the yd interface (Section 4.3.7).		verification is retrieved using the yd interface (Section 4.3.7).
	The URIs of the yd interface (Section 4.3.7) used to retrieve the		The URIs of the yd interface (Section 4.3.7) used to retrieve the
	LORDN Log file are:		LORDN Log file are:
	* Sunrise LORDN Log file:		* Sunrise LORDN Log file:
	https://<tmdb-domain-name>/LORDN/<TLD>/sunrise/<lordn-transaction-		https://<tmdb-domain-name>/LORDN/<TLD>/sunrise/<lordn-transaction-
	identifier>/result		identifier>/result
End of changes. 3 change blocks.
	5 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.48.