Re: [Secdispatch] Request for discussion of Concise IDs in Prague

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 17 March 2019 20:41 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF29131038 for <secdispatch@ietfa.amsl.com>; Sun, 17 Mar 2019 13:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d7M1gsKjFSvH for <secdispatch@ietfa.amsl.com>; Sun, 17 Mar 2019 13:41:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29FD71279AD for <secdispatch@ietf.org>; Sun, 17 Mar 2019 13:41:46 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 0CB0E3826B; Sun, 17 Mar 2019 16:41:21 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id AB84AA91; Sun, 17 Mar 2019 16:41:44 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A91E65D0; Sun, 17 Mar 2019 16:41:44 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: secdispatch@ietf.org
In-Reply-To: <B55C574A-8C20-45AD-9213-C00F942F4518@tzi.org>
References: <B55C574A-8C20-45AD-9213-C00F942F4518@tzi.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Sun, 17 Mar 2019 16:41:44 -0400
Message-ID: <16027.1552855304@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/xq7C1JTQIGrMDFeuxyFj27TfosU>
Subject: Re: [Secdispatch] Request for discussion of Concise IDs in Prague
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Mar 2019 20:41:49 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > A side discussion and meeting(*) was held a while ago to determine a
    > good solution; this side meeting came up with ACE and CORE as two
    > leading candidates: ACE because it already did CWT (which, however,
    > already was a bit of an odd addition to its charter), and CORE,
    > because it is interested in having such a profile available and has
    > the requirements (but is not itself a security area WG).

I had asked why not CBOR WG, and it might be useful to share your answer.

    > The side meeting also recommended to ask secdispatch to dispatch this
    > document.  Because a family tragedy kept one of the main authors away
    > from this, this did not happen right away; however, I would like to
    > make this request now, hopefully in time for a discussion in Prague.

+1

I am also aware of a few other groups that would be interested in
ConciseIDs, but I don't speak for them, so I've asked them to speak up
themselves.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-