Re: [Last-Call] Last Call: Advancing the Registration Data Access Protocol (RDAP) to Internet Standard

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 15 February 2021 14:44 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2693A0BB1 for <last-call@ietfa.amsl.com>; Mon, 15 Feb 2021 06:44:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
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 srdqSwtwUuex for <last-call@ietfa.amsl.com>; Mon, 15 Feb 2021 06:44:24 -0800 (PST)
Received: from mail1.verisign.com (mail1.verisign.com [72.13.63.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F6AE3A0BB8 for <last-call@ietf.org>; Mon, 15 Feb 2021 06:44:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=5880; q=dns/txt; s=VRSN; t=1613400266; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=ecfsU0NtVdPrsP6Nwk7rcjgesNT4Tb+LDAavr1XX4sk=; b=h3OgYPxnX9oCfH3Sy07VpEPbPOKPiwxtcbTe9mG/P/7w7Hy6tSPpWtz/ xukFolaH/S5aT9D1XiMEXUXRc6EXIQwqQR7YC6qAYrzIL26TIY5rbgS/3 ZCd8EldlyMjEIoHWZqVG2kUwLKNt4uBRteBEUclVefOhYqd02n24Y8N5u RMZLYXVIW3Zjzqfyr2edUomse1tJOaAMMBvCoZPC7BaDsYj5UvSZwTyyb U1YqZxUXCJc7DGrVE2ZUwujEzNTzkevWqtrNO7MlXj7YXsZo2u1I3u4dF syaLU/r2cXApT074rIwpQjGoMhR3mF2J6sz4p/8gfTgaqNTZKLB4BGNTz g==;
IronPort-SDR: X2BWWc2DvuS3Z9c+YTS/5gAY6UK+3S/iKzJMGHYuLjftpAynRU1eCNKjCHINXI9r3SgkdNnBmt BWTMQrtF/pIws8aIq5E8rkBUA+j1wI5X2UuXVijvsh74l/dIKX4/fCRymzXu2vCEdlPhxpKl1N SR6JL7i0lsP/LOneZFsDluHPvvmqK8Ytluq+05nJWMUoGryZ7i5GfVy4ky4w+BpjRnV3/4Lo97 czG5HUhZyGaVOJ0Vmx+0xkPszDu4eMShnpkhJg+gU0FETG2fe5r51veEZrjpr+P4U/yS/VGHrB iEI=
X-IronPort-AV: E=Sophos;i="5.81,180,1610409600"; d="scan'208";a="5735712"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Mon, 15 Feb 2021 09:44:23 -0500
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde]) by BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde%4]) with mapi id 15.01.2176.002; Mon, 15 Feb 2021 09:44:23 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "john-ietf@jck.com" <john-ietf@jck.com>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: [EXTERNAL] Re: [Last-Call] Last Call: Advancing the Registration Data Access Protocol (RDAP) to Internet Standard
Thread-Index: AQHW//JeCFiu9rRwmUWw/osy319k8apZTyJw
Date: Mon, 15 Feb 2021 14:44:22 +0000
Message-ID: <0a777da707614510b062b7435f63bcb0@verisign.com>
References: <161298637422.6661.9458865452594710338@ietfa.amsl.com> <4CB6A24AB8CEFE61CBA4B082@PSB>
In-Reply-To: <4CB6A24AB8CEFE61CBA4B082@PSB>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/erj9rSJPel4hN6dhGXH3vcOi6Mc>
Subject: Re: [Last-Call] Last Call: Advancing the Registration Data Access Protocol (RDAP) to Internet Standard
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 14:44:26 -0000

> -----Original Message-----
> From: last-call <last-call-bounces@ietf.org> On Behalf Of John C Klensin
> Sent: Wednesday, February 10, 2021 4:18 PM
> To: last-call@ietf.org
> Subject: [EXTERNAL] Re: [Last-Call] Last Call: Advancing the Registration Data
> Access Protocol (RDAP) to Internet Standard
> 
> Caution: This email originated from outside the organization. Do not click links
> or open attachments unless you recognize the sender and know the content
> is safe.
> 
> Hi.
> 
> Questions about this that may bear some discussion (I'm not necessarily
> opposed, just think we should be clear)...
> 
> The description in the supporting document indicates, as required,
> "widespread deployment and successful operational
> experience".   While I understand that this has been implemented
> for many TLD and address registries and is in use by at least some of those
> registries and their customers, RFC 7480, which appears to be the core
> document of the collection, says:
> 
> "RDAP is a successor protocol to the very old WHOIS protocol."
> in the abstract and proceeds to justify the specification of RDAP in the
> Introduction and elsewhere in the document.  It is now nearly seven years
> since RFC 7480 was published; WHOIS is almost certainly more in use than
> ever (just because the Internet and number of TLDs has grown); and there
> are continuing efforts outside the IETF (e.g., in a seemingly-never-ending
> sequence of ICANN committees and working groups) to define a
> replacement for WHOIS and requirements for its use (at least for DNS
> purposes).
> 
> So, three questions and a comment, with the understanding that they may
> partially apply to 7482bis and 7483bis as well:
> 
> (1) While the requirements for Internet Standard do not require acceptance
> in the marketplace, I believe the IETF has sometimes interpreted evidence of
> the lack of such acceptance --which, at least in terms of replacing WHOIS for
> DMS use, appears clear
> here-- as an indication that we should not proceed with advancing the
> document.  There may be reasons for advancing these specifications anyway,
> but would it then be useful to modify at least 7480 to make the relationships
> more clear?

WHOIS and RDAP are completely independent, but Section 1 of 7480 already describes some of the issues with WHOIS that prompted the development of RDAP. What else is needed?

> (2) More basically, is there consensus in the IETF community (not just in the
> regional and TLD registry communities) that this is the way to go, doing so
> without any supporting or explanatory documentation in the RFC Series,
> noting in particular that RFC 3912 (the current Whois spec) is already at Draft
> Standard and evidently much more widely deployed and used and that these
> documents do nothing to deprecate it (the comments in assorted SSAC
> reports referenced from RFC 7480 and many subsequent ICANN reports
> about its deficiencies notwithstanding).
> 
> (3) If there is actually IETF consensus to advance these two documents
> without either updates or supplemental explanations, could the supporting
> document in the datatracker, be updated to reflect discussion and decisions
> related to the above issues rather than simply asserting that "the RFC 6410
> requirements...
> have been met" which, given at least the Whois question, may be a bit
> misleading even if that was not intended?
> 
> (4) Finally, if the intention of moving these documents to Internet Standard
> at this time is, even partially, to act as a forcing function for getting rid of
> WHOIS, can that please be explicit rather than having people asking "why
> now" questions.
> >From my perspective, if it is just a matter of an outgoing AD
> trying to clean up as many loose end as possible, I have no problem with that,
> but it would be good to be clear.

I'll leave the consensus questions for the IESG, but the intention of the request to advance the RDAP RFCs to Standard status is NOT to force deprecation of WHOIS. It's about recognizing the implementation and deployment success of RDAP. I imagine that there will need to be a "move WHOIS to Historic status" request at some point in the future if it ever falls into disuse.

Scott