[art] Artart last call review of draft-ietf-lamps-im-keyusage-02

Cullen Jennings via Datatracker <noreply@ietf.org> Mon, 28 October 2024 02:48 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from [10.244.8.143] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 98488C14F6A6; Sun, 27 Oct 2024 19:48:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Cullen Jennings via Datatracker <noreply@ietf.org>
To: art@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.26.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <173008371824.314572.18330630715795320344@dt-datatracker-6cdf944fd9-dld6h>
Date: Sun, 27 Oct 2024 19:48:38 -0700
Message-ID-Hash: W3ZROT6AEO3MJKKA7QZ7LVPNWYTSQFRL
X-Message-ID-Hash: W3ZROT6AEO3MJKKA7QZ7LVPNWYTSQFRL
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-art.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-lamps-im-keyusage.all@ietf.org, last-call@ietf.org, spasm@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Cullen Jennings <fluffy@iii.ca>
Subject: [art] Artart last call review of draft-ietf-lamps-im-keyusage-02
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/2LoUIIBCLfFOBAqY-FSPXNgHLi8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Owner: <mailto:art-owner@ietf.org>
List-Post: <mailto:art@ietf.org>
List-Subscribe: <mailto:art-join@ietf.org>
List-Unsubscribe: <mailto:art-leave@ietf.org>

Reviewer: Cullen Jennings
Review result: Ready

This is a very simple draft but it needs to get the details correct it how it
adds this key usage. I do not see any problems with the draft and think it is
ready to publish.

I find it slightly odd that it included the XMPP URL when the use cases seem
like they fit better with IM URL but I do not see any issues in having both.