[rpp] [IANA #1446149] Early review: draft-wullink-rpp-core-04 (IETF 125)

Amanda Baber via RT <iana-issues@iana.org> Thu, 12 March 2026 04:52 UTC

Return-Path: <iana-shared@iana.org>
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 B1C67C8B00B8; Wed, 11 Mar 2026 21:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.375
X-Spam-Level:
X-Spam-Status: No, score=-3.375 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=iana.org
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 onMv7dBdYDVv; Wed, 11 Mar 2026 21:52:03 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (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 D98A2C8B00B3; Wed, 11 Mar 2026 21:52:03 -0700 (PDT)
Received: from request7.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 32134E1FC5; Thu, 12 Mar 2026 04:52:03 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.lax.icann.org 32134E1FC5
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iana.org; s=202509s; t=1773291123; bh=hdwiSVJwDuhVscynoHKrGfa3UQc63JPiTNRb9xw55nM=; h=Subject:From:Reply-To:In-Reply-To:References:CC:Date:From; b=DdJSZDhSeK3B6XVuvB0dmiQUIHpnYtq3lidhmeb+ZzRz3QL1hkrD/4cRpovIxwQij KkquBE1XYMEWJXf7pT1o7ZkV0LQ3o8d3x/dTi5j6MOReM8f/F1maT7+Nl+us2ylTX3 mI0QxSLdFiIIHGu11Gwxt6O4646RoHGjJ3iNZCYA=
Received: by request7.lax.icann.org (Postfix, from userid 48) id 1F2AEC08F726; Thu, 12 Mar 2026 04:52:03 +0000 (UTC)
RT-Owner: Nobody
From: Amanda Baber via RT <iana-issues@iana.org>
In-Reply-To: <rt-5.0.3-563628-1773290677-1656.1446149-37-0@icann.org>
References: <RT-Ticket-1446149@icann.org> <rt-5.0.3-563628-1773290677-1656.1446149-37-0@icann.org>
Message-ID: <rt-5.0.3-563628-1773291123-887.1446149-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1446149
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Thu, 12 Mar 2026 04:52:03 +0000
MIME-Version: 1.0
Message-ID-Hash: 7A4JDWSGQIX6ZYDULARML2ORC55YRFEP
X-Message-ID-Hash: 7A4JDWSGQIX6ZYDULARML2ORC55YRFEP
X-MailFrom: iana-shared@iana.org
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: draft-wullink-rpp-core.all@ietf.org, rpp@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: iana-issues@iana.org
Subject: [rpp] [IANA #1446149] Early review: draft-wullink-rpp-core-04 (IETF 125)
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/A6jsoX-BhCLC4a-xYKFKaUK3EKw>
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>

Dear Authors,

Before the IETF meeting, we check working group agendas for documents with IANA-related issues. We have notes about this document:

https://datatracker.ietf.org/doc/html/draft-wullink-rpp-core-04

1) Please add guidance to future designated experts for the registries. This could be presented in a single subsection, if appropriate. For more information, see RFC 8126, Section 5.3.

2) For media types registered by IETF stream RFCs, the change controller is typically the IETF. The contact field often refers to the "Authors' Addresses" section or the WG. 

If you have any questions, just let us know. If you'd like to talk in person, you can find us next to the RFC Editor's table from Monday through Thursday. You can also request another review at any time by contacting us at iana@iana.org.

For more information about IANA Considerations section requirements, please see

https://www.iana.org/help/protocol-registration

Best regards,

Amanda Baber
IANA