Re: [regext] [Ext] Erik Kline's No Objection on draft-ietf-regext-dnrd-objects-mapping-09: (with COMMENT)

Gustavo Lozano <> Thu, 08 October 2020 22:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32AA83A0ED1; Thu, 8 Oct 2020 15:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qMYZA4Et0oLI; Thu, 8 Oct 2020 15:08:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AA96B3A0D0B; Thu, 8 Oct 2020 15:08:26 -0700 (PDT)
Received: from ( []) by ( with ESMTPS id 098M8PL9028203 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 8 Oct 2020 22:08:25 GMT
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.659.4; Thu, 8 Oct 2020 14:52:21 -0700
Received: from ([]) by ([]) with mapi id 15.02.0659.006; Thu, 8 Oct 2020 14:52:21 -0700
From: Gustavo Lozano <>
To: Erik Kline <>, The IESG <>
CC: "" <>, "" <>, "" <>, "Scott Hollenbeck" <>
Thread-Topic: [Ext] Erik Kline's No Objection on draft-ietf-regext-dnrd-objects-mapping-09: (with COMMENT)
Thread-Index: AQHWe0KLPcFvoupfN0ekhbP/YFxpzqmOhBIA
Date: Thu, 8 Oct 2020 21:52:21 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/16.38.20061401
x-originating-ip: []
x-source-routing-agent: Processed
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-10-08_15:2020-10-08, 2020-10-08 signatures=0
Archived-At: <>
Subject: Re: [regext] [Ext] Erik Kline's No Objection on draft-ietf-regext-dnrd-objects-mapping-09: (with COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 08 Oct 2020 22:08:28 -0000

Thank you Erik,

Comments below are prefixed with Authors-.

A new version has been published here:


On 8/25/20, 17:47, "Erik Kline via Datatracker" <> wrote:

    Erik Kline has entered the following ballot position for
    draft-ietf-regext-dnrd-objects-mapping-09: No Objection

    When responding, please keep the subject line intact and reply to all
    email addresses included in the To and CC lines. (Feel free to cut this
    introductory paragraph, however.)

    Please refer to;!!PtGJab4!oublqDZDSArqbWBQnbFor1rxwDgavlq-WBXYt_Cr9S7UqhIyOUn0WdGP8hxc-QTzTjHzr-r7-Q0$ 
    for more information about IESG DISCUSS and COMMENT positions.

    The document, along with other ballot positions, can be found here:;!!PtGJab4!oublqDZDSArqbWBQnbFor1rxwDgavlq-WBXYt_Cr9S7UqhIyOUn0WdGP8hxc-QTzTjHzztI-XAo$ 


    [ section 4.5 ]

    * For text representations you want RFC 5952 rather than 4291.

Authors- fixed in the next version of the I-D.

    [ section, ]

    * It's not clear that ",v4" or ",v6" are adding anything. The IP address
      family should be unambiguous without the hint.

      No change necessary, it just seems like this isn't really needed.  (For
      example, if there's even a remote possibility someone might try to list
      IPv4-mapped IPv6 addresses -- or even worse, compat addresses -- then
      there are going some other, much bigger problems ahead.)

Authors- it's a hint for verification to the party restoring the deposit

    [ section ]

    * Is it recommended at all that rdeRegistrar:url be https whenever possible?

Authors- text added in the next version of the I-D.

    * In addition to whois name/url should there RDAP information?  Or is the
      http/https whois URL expected to handle RDAP?

Authors- the industry is moving away for storing the base URL for the RDAP services in the SRS. See RFC7484, and There have been conversations of having a generic bootstrap-like for Registrars to accommodate non-gTLDs. If there is a specific need to store this information in the deposit, an extension can be created.