IETF Logo Mail Archive

[rpp] Re: RPP -05 feedback

Stéphane Bortzmeyer <bortzmeyer+ietf@nic.fr> Thu, 19 March 2026 07:36 UTC

Return-Path: <bortzmeyer@ietf.bortzmeyer.fr>
X-Original-To: rpp@mail2.ietf.org
Delivered-To: rpp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 36C6CCDBE6C3 for <rpp@mail2.ietf.org>; Thu, 19 Mar 2026 00:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGo7s7GpuQWi for <rpp@mail2.ietf.org>; Thu, 19 Mar 2026 00:36:55 -0700 (PDT)
Received: from ayla.bortzmeyer.org (ayla.bortzmeyer.org [92.243.4.211]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C6533CDBE6B6 for <rpp@ietf.org>; Thu, 19 Mar 2026 00:36:55 -0700 (PDT)
Received: by ayla.bortzmeyer.org (Postfix, from userid 10) id 03B39A00FD; Thu, 19 Mar 2026 08:36:53 +0100 (CET)
Received: by sbo-Latitude-7480 (Postfix, from userid 1002) id A162D19600FD; Thu, 19 Mar 2026 15:28:27 +0800 (HKT)
Date: Thu, 19 Mar 2026 15:28:27 +0800
From: Stéphane Bortzmeyer <bortzmeyer+ietf@nic.fr>
To: Pawel Kowalik <kowalik=40denic.de@dmarc.ietf.org>
Message-ID: <abulmy31k0A43Vmn@ietf.bortzmeyer.fr>
References: <PH7PR15MB6084DB24C0D4AC84D9B899EEC941A@PH7PR15MB6084.namprd15.prod.outlook.com> <abqwx-eq-_fEB4L2@ietf.bortzmeyer.fr> <9433d3f3-bdd3-4e98-b0b1-9ce4a3e2a0ea@denic.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9433d3f3-bdd3-4e98-b0b1-9ce4a3e2a0ea@denic.de>
Message-ID-Hash: A3OBJ6VPI6MJHUCWVPJPS47BLANHZFAE
X-Message-ID-Hash: A3OBJ6VPI6MJHUCWVPJPS47BLANHZFAE
X-MailFrom: bortzmeyer@ietf.bortzmeyer.fr
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rpp@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [rpp] Re: RPP -05 feedback
List-Id: "This list discusses a provisioning protocol based on RESTful principles and corresponding data representations using JSON." <rpp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rpp/yClXd0jTe06_Jp0kJRg3d4FICjM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rpp>
List-Help: <mailto:rpp-request@ietf.org?subject=help>
List-Owner: <mailto:rpp-owner@ietf.org>
List-Post: <mailto:rpp@ietf.org>
List-Subscribe: <mailto:rpp-join@ietf.org>
List-Unsubscribe: <mailto:rpp-leave@ietf.org>

On Wed, Mar 18, 2026 at 03:30:08PM +0100, Pawel Kowalik wrote:

> 1) Bootstrapping = finding where is the server for .xx TLD. I agree this is
> likely of limited value today.

Just a small warning: RPP is not limited to TLD. There are many public
(accepting domain name registrations from a wide public) registries
which are not TLD.

RDAP bootstrap is not limited to TLD (RFC 9224 "If a domain RDAP query
for a.b.example.com matches both com and example.com entries in the
registry, then the longest match applies and the example.com entry is
used by the client.")

Also, RDAP relies on HTTP redirection and, currently,
draft-wullink-rpp-core-05 seems silent about redirection (should a RPP
client follow it?)

v2.46.0 | Report a Bug | By Email | System Status