Re: [regext] AD Review: draft-ietf-regext-rdap-object-tag

Adam Roach <adam@nostrum.com> Sat, 14 July 2018 18:37 UTC

Return-Path: <adam@nostrum.com>
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 593741310F2 for <regext@ietfa.amsl.com>; Sat, 14 Jul 2018 11:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 piEgVIozjwtL for <regext@ietfa.amsl.com>; Sat, 14 Jul 2018 11:37:22 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EED7D130FE5 for <regext@ietf.org>; Sat, 14 Jul 2018 11:37:21 -0700 (PDT)
Received: from dhcp-9259.meeting.ietf.org (dhcp-9259.meeting.ietf.org [31.133.146.89]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w6EIbJHs082362 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 14 Jul 2018 13:37:20 -0500 (CDT) (envelope-from adam@nostrum.com)
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "'shollenbeck=40verisign.com@dmarc.ietf.org'" <shollenbeck=40verisign.com@dmarc.ietf.org>, "'regext@ietf.org'" <regext@ietf.org>, "'draft-ietf-regext-rdap-object-tag@tools.ietf.org'" <draft-ietf-regext-rdap-object-tag@tools.ietf.org>
References: <7426e645-9de3-20ed-f4c4-7e1f46703233@nostrum.com> <831693C2CDA2E849A7D7A712B24E257F7FA73B18@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <02b19628-470c-124c-1fb1-8c622e3bd592@nostrum.com> <831693C2CDA2E849A7D7A712B24E257F7FA7533B@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <66aaa434-de52-f763-0a99-052f59306e8f@nostrum.com>
Date: Sat, 14 Jul 2018 14:37:17 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F7FA7533B@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/h0mtzkMtaBwK3PTzpB6yoboTHoM>
Subject: Re: [regext] AD Review: draft-ietf-regext-rdap-object-tag
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.27
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: Sat, 14 Jul 2018 18:37:25 -0000

On 6/6/18 06:56, Hollenbeck, Scott wrote:
>> -----Original Message-----
>> From: Adam Roach <adam@nostrum.com>;
...
>>>> I read the text as calling for implementors to concatenate "XXXX-YYYY"
>>>> to the
>>>> end of the IANA-registered base URL ("https://example.com/rdap/"),
>>>> resulting in "https://example.com/rdap/XXXX-YYYY". The example instead
>>>> shows "https://example.com/rdap/entity/XXXX-YYY". Is the inclusion of
>>>> "entity/" in this example an error?
>>> No, it's not an error. That’s the path segment that 7482 describes for
>> entity queries. I can see how my text above might be confusing, though, so
>> how about this wording instead?
>>> OLD:
>>> "The base RDAP URL is concatenated to the entity handle to create a
>> complete RDAP query path segment of "https://example.com/rdap/entity/XXXX-
>> YYYY""
>>> NEW:
>>> "The RDAP query URL is formed using the base RDAP URL and entity path
>> segment described in Section 3.1.5 of RFC 7482, using "XXXX-YYY" as the
>> value of the handle identifier. The complete RDAP query URL becomes
>> "https://example.com/rdap/entity/XXXX-YYYY"."
>>
>> That seems good.
>>
>> Thanks for the explanations. Based on what you've said, I think this is
>> ready for IETF last call -- you can treat my comment for clarification
>> of the example as an IETF last call comment, and address it along with
>> any other feedback you receive during last call.
> Will do - thanks!

IETF Last Call has concluded, and I didn't see any other comments that 
would necessitate changes in the document. Just to make sure we're on 
the same page, I'm waiting on a -04 version of the document reflecting 
the above change prior to asking for the IESG to ballot on the document. 
Let me know if that's not what you expect.

/a