[lamps] Mohamed Boucadair's No Objection on draft-ietf-lamps-rfc5273bis-08: (with COMMENT)
Mohamed Boucadair via Datatracker <noreply@ietf.org> Wed, 10 September 2025 05:48 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@mail2.ietf.org
Received: from [10.244.8.59] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id A9E106039F8B; Tue, 9 Sep 2025 22:48:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mohamed Boucadair via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <175748328563.3519972.1174499574379480072@dt-datatracker-f7c8fdcb7-pjx77>
Date: Tue, 09 Sep 2025 22:48:05 -0700
Message-ID-Hash: 2LGEHMCYEPIEHO4SWNSPMWI5M55MLTGQ
X-Message-ID-Hash: 2LGEHMCYEPIEHO4SWNSPMWI5M55MLTGQ
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-lamps-rfc5273bis@ietf.org, lamps-chairs@ietf.org, spasm@ietf.org, housley@vigilsec.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Mohamed Boucadair <mohamed.boucadair@orange.com>
Subject: [lamps] Mohamed Boucadair's No Objection on draft-ietf-lamps-rfc5273bis-08: (with COMMENT)
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/7PaNuOk8VTT9c4K7iaOqLAZeeqE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Owner: <mailto:spasm-owner@ietf.org>
List-Post: <mailto:spasm@ietf.org>
List-Subscribe: <mailto:spasm-join@ietf.org>
List-Unsubscribe: <mailto:spasm-leave@ietf.org>
Mohamed Boucadair has entered the following ballot position for draft-ietf-lamps-rfc5273bis-08: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc5273bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi Joseph and Sean, Thank you for the effort put into this bis. I only reviewed the diff between this draft and RFC 5273. Please find some comments below: # On the TCP port number The draft says: CMC requires a registered port number to send and receive CMC messages over TCP. The Service Name is "pkix-cmc". The value of this TCP port is 5318. While RFC5273 says The ports in the range of 1-49151 SHOULD NOT be used. The port to be used is configured out of band. I appreciate that the new text is inherited from rfc6402#section-3, but I think some changes are needed here: (1) “requires” in the new text suggests that using other port number would break the protocol. Maybe s/requires/uses (2) I’m not sure how the SHOULD NOT in 5273 was handled by existing implementations (e.g., allow to configure a part in that range) or if this was left to operators. Can we please have an operational considerations section that discusses this? That section can also discuss whether support of alternative ports is still an option + how the selection among the various option is done in practice. Few sentences would suffice to clarify these. Thanks. # Use the correct registry name + add an action to update it to refer to this document: OLD: IANA has assigned a TCP port number in the Registered Port Number range for the use of CMC. NEW: IANA has assigned a TCP port number in the “Service Name and Transport Protocol Port Number” registry for the use of CMC. The registration should be update to: # Please move [erratum3593] to be listed as informative. Cheers Med
- [lamps] Mohamed Boucadair's No Objection on draft… Mohamed Boucadair via Datatracker