[lamps] Martin Duke's No Objection on draft-ietf-lamps-5g-nftypes-08: (with COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Wed, 30 November 2022 21:58 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CD399C159484; Wed, 30 Nov 2022 13:58:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lamps-5g-nftypes@ietf.org, lamps-chairs@ietf.org, spasm@ietf.org, tim.hollebeek@digicert.com, tim.hollebeek@digicert.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <166984550883.50686.943643638647266078@ietfa.amsl.com>
Date: Wed, 30 Nov 2022 13:58:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/frW76cy4BYVOjstFq-VPok6zyuk>
Subject: [lamps] Martin Duke's No Objection on draft-ietf-lamps-5g-nftypes-08: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2022 21:58:28 -0000

Martin Duke has entered the following ballot position for
draft-ietf-lamps-5g-nftypes-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-5g-nftypes/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

# Martin Duke, TSV AD

## Comments

I don't love that there isn't any sort of FCFS registry to avoid collisions in
NF type. I don't understand the division between 3GPP, IETF, and IANA here, but
it would be nice to straighten this out. It would otherwise be a matter of time
before there was some sort of collision between similarly named proprietary
functions.