[regext] RFC 9022 on Domain Name Registration Data (DNRD) Objects Mapping

rfc-editor@rfc-editor.org Fri, 28 May 2021 16:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDA593A2DDE; Fri, 28 May 2021 09:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z02IN9WRocp2; Fri, 28 May 2021 09:36:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CB053A2DDA; Fri, 28 May 2021 09:36:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A993AF407D8; Fri, 28 May 2021 09:36:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, regext@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210528163600.A993AF407D8@rfc-editor.org>
Date: Fri, 28 May 2021 09:36:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/2xRIBwyDluWM6To2InBhm_RggOg>
Subject: [regext] RFC 9022 on Domain Name Registration Data (DNRD) Objects Mapping
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2021 16:36:21 -0000

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

        
        RFC 9022

        Title:      Domain Name Registration Data (DNRD) 
                    Objects Mapping 
        Author:     G. Lozano,
                    J. Gould,
                    C. Thippeswamy
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2021
        Mailbox:    gustavo.lozano@icann.org,
                    jgould@verisign.com,
                    cthippeswamy@verisign.com
        Pages:      169
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-dnrd-objects-mapping-11.txt

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

        DOI:        10.17487/RFC9022

This document specifies the format, contents, and semantics of Domain
Name Registration Data (DNRD) escrow deposits for a domain name
registry.

This document is a product of the Registration Protocols Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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