--- 1/draft-ietf-regext-tmch-func-spec-04.txt	2019-10-31 10:13:09.820518427 -0700
+++ 2/draft-ietf-regext-tmch-func-spec-05.txt	2019-10-31 10:13:09.928521399 -0700
@@ -1,18 +1,18 @@
 
 Internet Engineering Task Force                                G. Lozano
 Internet-Draft                                                     ICANN
-Intended status: Informational                              Jun 13, 2018
-Expires: December 15, 2018
+Intended status: Informational                              Oct 31, 2019
+Expires: May 3, 2020
 
                   ICANN TMCH functional specifications
-                  draft-ietf-regext-tmch-func-spec-04
+                  draft-ietf-regext-tmch-func-spec-05
 
 Abstract
 
    This document describes the requirements, the architecture and the
    interfaces between the ICANN Trademark Clearinghouse (TMCH) and
    Domain Name Registries as well as between the ICANN TMCH and Domain
    Name Registrars for the provisioning and management of domain names
    during Sunrise and Trademark Claims Periods.
 
 Status of This Memo
@@ -23,25 +23,25 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on December 15, 2018.
+   This Internet-Draft will expire on May 3, 2020.
 
 Copyright Notice
 
-   Copyright (c) 2018 IETF Trust and the persons identified as the
+   Copyright (c) 2019 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
    carefully, as they describe your rights and restrictions with respect
    to this document.  Code Components extracted from this document must
    include Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
@@ -114,20 +114,21 @@
        6.3.1.  LORDN Log file  . . . . . . . . . . . . . . . . . . .  40
          6.3.1.1.  LORDN Log Result Codes  . . . . . . . . . . . . .  42
      6.4.  Signed Mark Data (SMD) File . . . . . . . . . . . . . . .  46
      6.5.  Trademark Claims Notice (TCN) . . . . . . . . . . . . . .  47
      6.6.  Sunrise List (SURL) . . . . . . . . . . . . . . . . . . .  54
    7.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . .  55
      7.1.  Trademark Claims Notice (TCN) . . . . . . . . . . . . . .  55
    8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  58
    9.  Change History  . . . . . . . . . . . . . . . . . . . . . . .  58
      9.1.  Version 04  . . . . . . . . . . . . . . . . . . . . . . .  58
+     9.2.  Version 05  . . . . . . . . . . . . . . . . . . . . . . .  58
    10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  58
    11. Security Considerations . . . . . . . . . . . . . . . . . . .  59
    12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  59
      12.1.  Normative References . . . . . . . . . . . . . . . . . .  59
      12.2.  Informative References . . . . . . . . . . . . . . . . .  60
    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  62
 
 1.  Introduction
 
    Domain Name Registries (DNRs) may operate in special modes for
@@ -2554,30 +2555,33 @@
    Paul Hoffman.
 
 9.  Change History
 
    [[RFC Editor: Please remove this section.]]
 
 9.1.  Version 04
 
    1.  Ping update.
 
+9.2.  Version 05
+
+   1.  Ping update.
+
 10.  IANA Considerations
 
    This document uses URNs to describe XML namespaces and XML schemas
    conforming to a registry mechanism described in [RFC3688].  One URI
    assignment have been registered by the IANA.
 
    Registration request for the Trademark Claims Notice namespace:
 
       URI: urn:ietf:params:xml:ns:tmNotice-1.0
-
       Registrant Contact: See the "Author's Address" section of this
       document.
 
       XML: None.  Namespace URIs do not represent an XML specification.
 
    Registration request for the Trademark Claims Notice XML schema:
 
       URI: urn:ietf:params:xml:ns:tmNotice-1.0
 
       Registrant Contact: See the "Author's Address" section of this
@@ -2614,22 +2618,22 @@
               clearinghouse/previously-abused-16jul13-en.pdf>.
 
    [MatchingRules]
               ICANN, "Memorandum on Implementing Matching Rules",
               September 2012, <https://newgtlds.icann.org/en/about/
               trademark-clearinghouse/matching-rules-24sep12-en.pdf>.
 
    [QLP-Addendum]
               ICANN, "Qualified Launch Program Addendum", April 2014,
               <https://newgtlds.icann.org/en/about/trademark-
-              clearinghouse/
-              rpm-requirements-qlp-addendum-10apr14-en.pdf>.
+              clearinghouse/rpm-requirements-qlp-addendum-
+              10apr14-en.pdf>.
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
               <https://www.rfc-editor.org/info/rfc2119>.
 
    [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
               DOI 10.17487/RFC3688, January 2004,
               <https://www.rfc-editor.org/info/rfc3688>.