Return-Path: 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 D0396E328688 for ; Sat, 25 Apr 2026 17:19:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777162747; bh=YjzWbLfFQkT30BlkxxnU27dVaa8JhRCa2dweNVrmRbI=; h=Date:Subject:To:References:From:In-Reply-To; b=xOmfGy1uy8vjKCYNW7rcqPQ/wejfIVbbrUH0Cb59ZMAVjzNzTvx9lIR6fLT1+4Ld2 4hywebINYqzMbiq2TRwjDkYVDMi9nDvCgd7VLjc5dUEsXIL6I9rs385yyiaIubMX9g YhfkHa6f0nxwkJYVI/dgg+JRDE8hz1j70eDvCABA= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 eyiAcZl1wcYa for ; Sat, 25 Apr 2026 17:19:07 -0700 (PDT) Received: from smtp-190f.mail.infomaniak.ch (smtp-190f.mail.infomaniak.ch [IPv6:2001:1600:19:fff0::190f]) (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 27635E328681 for ; Sat, 25 Apr 2026 17:19:06 -0700 (PDT) Received: from smtp-4-0001.mail.infomaniak.ch (smtp-4-0001.mail.infomaniak.ch [10.7.10.108]) by smtp-4-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4g36kW0QlnzdL8 for ; Sun, 26 Apr 2026 02:18:59 +0200 (CEST) Received: from unknown by smtp-4-0001.mail.infomaniak.ch (Postfix) with ESMTPA id 4g36kV4sKhzjT1 for ; Sun, 26 Apr 2026 02:18:58 +0200 (CEST) Content-Type: multipart/alternative; boundary="------------3MRafQivQrGLGOM0wDP8lZYg" Message-ID: Date: Sun, 26 Apr 2026 02:18:58 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: rpp@ietf.org References: <7aecece5-7098-4132-869c-56664d42a34e@nothos.net> <71C79B1D-EACE-4D23-B053-2859903A7A47@sidn.nl> <85cd2c3e-ae4d-4976-bf86-9fb7708c391f@nothos.net> <8DD95A12-E7C8-4D48-B17B-C18F71B5BA67@sidn.nl> Content-Language: en-US From: Pierre Thierry In-Reply-To: <8DD95A12-E7C8-4D48-B17B-C18F71B5BA67@sidn.nl> X-Infomaniak-Routing: alpha Message-ID-Hash: JXYZFYPBNJSDQ5KKBBGPJBF6TD7UKMTQ X-Message-ID-Hash: JXYZFYPBNJSDQ5KKBBGPJBF6TD7UKMTQ X-MailFrom: pierre@nothos.net 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 X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Brpp=5D_Re=3A_RPP_-05_feedback?= List-Id: "This list discusses a provisioning protocol based on RESTful principles and corresponding data representations using JSON." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This is a multi-part message in MIME format. --------------3MRafQivQrGLGOM0wDP8lZYg Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Le 24/04/2026 à 08:35, Maarten Wullink a écrit : >  what about if we add a special zone (e.g. _rpp) for rpp server > bootstrap only and put the HTTP RR there. something like: > _rpp.example. 3600 IN HTTPS 1 rpp.example. alpn=h2,h3 port=8443 IIUC, a _rpp.example SVCB record is supposed to be used for rpp://example. I didn't see the use you suggest in RFC 9460 (a special zone for a HTTPS RR). SRV is more flexible there. Doubtfully, Pierre Thierry -- pierre@nothos.net 0xD9D50D8A --------------3MRafQivQrGLGOM0wDP8lZYg Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Le 24/04/2026 à 08:35, Maarten Wullink a écrit :
 what about if we add a special zone (e.g. _rpp) for rpp server bootstrap only and put the HTTP RR there. something like:
_rpp.example. 3600 IN HTTPS 1 rpp.example. alpn=h2,h3 port=8443

IIUC, a _rpp.example SVCB record is supposed to be used for rpp://example. I didn't see the use you suggest in RFC 9460 (a special zone for a HTTPS RR). SRV is more flexible there.

Doubtfully,
Pierre Thierry
-- 
pierre@nothos.net
0xD9D50D8A
--------------3MRafQivQrGLGOM0wDP8lZYg--