IETF Logo Mail Archive

Re: [lamps] I-D Action: draft-ietf-lamps-im-keyusage-00.txt

Russ Housley <housley@vigilsec.com> Mon, 15 April 2024 21:21 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BADCEC151083 for <spasm@ietfa.amsl.com>; Mon, 15 Apr 2024 14:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dBXcv4gwqYMn for <spasm@ietfa.amsl.com>; Mon, 15 Apr 2024 14:21:46 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 569D1C14F701 for <spasm@ietf.org>; Mon, 15 Apr 2024 14:21:46 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 8F4D91012D7; Mon, 15 Apr 2024 17:21:45 -0400 (EDT)
Received: from smtpclient.apple (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 65D761028D1; Mon, 15 Apr 2024 17:21:45 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <2E8965D1-F0D8-4947-8A6B-19B822EEFA4C@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_ABA36529-67BD-40C2-9B7F-B1DB3BBDC84B"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.1\))
Date: Mon, 15 Apr 2024 17:21:35 -0400
In-Reply-To: <CAKoiRuYCSwdzwKwSXdyLCNm5Z3DzzzLZzSyDO7DGWHTSeUj-fA@mail.gmail.com>
Cc: LAMPS <spasm@ietf.org>
To: Rohan Mahy <rohan.ietf@gmail.com>
References: <171320513468.22285.6899802433610546466@ietfa.amsl.com> <B508131E-0554-471F-94FD-4AA2A0A95346@vigilsec.com> <CAKoiRuYCSwdzwKwSXdyLCNm5Z3DzzzLZzSyDO7DGWHTSeUj-fA@mail.gmail.com>
X-Mailer: Apple Mail (2.3731.700.6.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:message-id:content-type:mime-version:subject:date:in-reply-to:cc:to:references; s=pair-202402141609; bh=IVTak8c/gfqpDdzuxl3EJHZcKvBoWIDBI1fUB35JyN8=; b=aDGrOw/zbLZaI8zUOJrrlPw5ZFeXIR6dCQGAZ/fVlnYGuB/i6X0luUMfWt0Vf+KJUm2y7TcQVRUtLYGF7qRBjMjeFQ6BMpKdHJnvw8mthbY7dPfy7kvepHi1MWa9sf9XsmUe9uOgCKw2THcFdeFJI/i+GmwaQNWVLUDG/vURzv2iZrq0UF7+9dQBZrmtFsCWM6PxSr80cIF402wHTLvEeVPES4dfeXrJ+Z4bd8yPH4yomKgdWUv10KC35/xN7HvVAZRC9G8UJLgyDRyiE+Hgay5DTTx9HaNPO9MRVLYVSNjsI+1V0JXnVq+jh9YKUxq6lSE/fqAJ5KAhv11C7Z+vQg==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/lGmpI9FJjjuQdDThdzCnmSVC5_I>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-im-keyusage-00.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: This is the mail list for the LAMPS Working Group <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: Mon, 15 Apr 2024 21:21:50 -0000

I thought it was worth asking.  I think the xmpp: URI in the SAN would be a very reasonable solution.

Russ


> On Apr 15, 2024, at 4:49 PM, Rohan Mahy <rohan.mahy@gmail.com> wrote:
> 
> Hi Russ,
> I don't understand why an XmppAddr identifier type would have been strictly needed, since anyone could have put either an xmpp: URI or an im: URI into a SAN without any extensions (as a URI type).
> 
> I'm happy to go look at some old discussions, but I don't know the history.
> Thanks,
> -rohan
> 
> 
> 
> On Mon, Apr 15, 2024 at 11:28 AM Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
>> Rohan:
>> 
>> RFC 6120 defines the way to carry a client name (Jabber ID) in the subjectAltName extension.  Should this document be expanded to address subjectAltName as well as extended key usage?
>> 
>> Russ
>> 
>> 
>> > On Apr 15, 2024, at 2:18 PM, internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> wrote:
>> > 
>> > Internet-Draft draft-ietf-lamps-im-keyusage-00.txt is now available. It is a
>> > work item of the Limited Additional Mechanisms for PKIX and SMIME (LAMPS) WG
>> > of the IETF.
>> > 
>> >   Title:   X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs
>> >   Author:  Rohan Mahy
>> >   Name:    draft-ietf-lamps-im-keyusage-00.txt
>> >   Pages:   5
>> >   Dates:   2024-04-15
>> > 
>> > Abstract:
>> > 
>> >   RFC 5280 specifies several extended key purpose identifiers
>> >   (KeyPurposeIds) for X.509 certificates.  This document defines
>> >   Instant Messaging (IM) identity KeyPurposeId for inclusion in the
>> >   Extended Key Usage (EKU) extension of X.509 v3 public key
>> >   certificates
>> > 
>> > The IETF datatracker status page for this Internet-Draft is:
>> > https://datatracker.ietf.org/doc/draft-ietf-lamps-im-keyusage/
>> > 
>> > There is also an HTML version available at:
>> > https://www.ietf.org/archive/id/draft-ietf-lamps-im-keyusage-00.html
>> > 
>> > Internet-Drafts are also available by rsync at:
>> > rsync.ietf.org::internet-drafts
>> > 
>> > 
>> > _______________________________________________
>> > Spasm mailing list
>> > Spasm@ietf.org <mailto:Spasm@ietf.org>
>> > https://www.ietf.org/mailman/listinfo/spasm
>> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm

v2.23.0 | Report a Bug | By Email