[netmod] Murray Kucherawy's No Objection on draft-ietf-netmod-rfc6991-bis-17: (with COMMENT)
Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 19 December 2024 06:31 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: netmod@ietf.org
Delivered-To: netmod@ietfa.amsl.com
Received: from [10.244.8.156] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 39BFCC18870B; Wed, 18 Dec 2024 22:31:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.31.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <173458986989.44109.994042303935837069@dt-datatracker-65f549669d-lhv7k>
Date: Wed, 18 Dec 2024 22:31:09 -0800
Message-ID-Hash: T5VO65CHQELHKV4IXL2PEUPHBWY2DBGM
X-Message-ID-Hash: T5VO65CHQELHKV4IXL2PEUPHBWY2DBGM
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netmod.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-netmod-rfc6991-bis@ietf.org, netmod-chairs@ietf.org, netmod@ietf.org, kent+ietf@watsen.net
X-Mailman-Version: 3.3.9rc6
Reply-To: Murray Kucherawy <superuser@gmail.com>
Subject: [netmod] Murray Kucherawy's No Objection on draft-ietf-netmod-rfc6991-bis-17: (with COMMENT)
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/mfVqUbChP9PDFH4XuyVDigTdCkA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Owner: <mailto:netmod-owner@ietf.org>
List-Post: <mailto:netmod@ietf.org>
List-Subscribe: <mailto:netmod-join@ietf.org>
List-Unsubscribe: <mailto:netmod-leave@ietf.org>
Murray Kucherawy has entered the following ballot position for draft-ietf-netmod-rfc6991-bis-17: 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-netmod-rfc6991-bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I support Orie's DISCUSS position. His point about Security Considerations might draw an additional DISCUSS from the SEC ADs. The shepherd writeup doesn't explain why Proposed Standard is being requested. (It's fairly obvious, but I'd prefer a bit more completeness.) I think the SHOULD [NOT]s in the "object-identifier" section could use some guidance about why they're only SHOULD [NOT]. Is there a reason one might deviate from this advice? What's the interoperability impact of doing so? Same question about the SHOULD under "domain-name".
- [netmod] Murray Kucherawy's No Objection on draft… Murray Kucherawy via Datatracker