RFC 9361 on ICANN Trademark Clearinghouse (TMCH) Functional Specifications

rfc-editor@rfc-editor.org Fri, 10 March 2023 05:34 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCDD5C1782C6 for <ietf-announce@ietfa.amsl.com>; Thu, 9 Mar 2023 21:34:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJAeT7yAs11g for <ietf-announce@ietfa.amsl.com>; Thu, 9 Mar 2023 21:34:21 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFB91C1782D0 for <ietf-announce@ietf.org>; Thu, 9 Mar 2023 21:34:21 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5BCEA4C26B; Thu, 9 Mar 2023 21:34:21 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9361 on ICANN Trademark Clearinghouse (TMCH) Functional Specifications
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230310053421.5BCEA4C26B@rfcpa.amsl.com>
Date: Thu, 09 Mar 2023 21:34:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/hgxZasgknfKE829M_VH1PF_roFQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Mar 2023 05:34:26 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9361

        Title:      ICANN Trademark Clearinghouse (TMCH) Functional 
                    Specifications 
        Author:     G. Lozano
        Status:     Informational
        Stream:     Independent
        Date:       March 2023
        Mailbox:    gustavo.lozano@icann.org
        Pages:      50
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-tmch-func-spec-15.txt

        URL:        https://www.rfc-editor.org/info/rfc9361

        DOI:        10.17487/RFC9361

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.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC