IETF Logo Mail Archive

Re: [Anima] [netmod] [anima-wg/anima-brski-async-enroll] Definition of new assertion type (agent-proximity) for the voucher (#18)

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 18 June 2021 20:09 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DEB3A09F9; Fri, 18 Jun 2021 13:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 c0ig5Wb5FXCz; Fri, 18 Jun 2021 13:09:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 659D93A09F6; Fri, 18 Jun 2021 13:09:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2A44A38E0B; Fri, 18 Jun 2021 16:11:14 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ib46nNH40nyF; Fri, 18 Jun 2021 16:11:11 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 80C1738E09; Fri, 18 Jun 2021 16:11:11 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 399A252; Fri, 18 Jun 2021 16:09:49 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andy Bierman <andy@yumaworks.com>, "Fries, Steffen" <steffen.fries@siemens.com>, Kent Watsen <kent+ietf@watsen.net>, "netmod@ietf.org" <netmod@ietf.org>, "anima@ietf.org" <anima@ietf.org>, "Werner, Thomas" <thomas-werner@siemens.com>
In-Reply-To: <CABCOCHRGYM3nkUaX4_quu3JpznYXDdwejD11ppWni3wU8tEbkA@mail.gmail.com>
References: <anima-wg/anima-brski-async-enroll/issues/18@github.com> <19872.1623779796@localhost> <0100017a16ff590b-6803346f-2ef6-4b19-88bf-3c670e32d5a0-000000@email.amazonses.com> <CABCOCHQRJB3nca36bz+gVykw5fxym7ji3GJrVMcrsW+6uUopYg@mail.gmail.com> <c8c4ea615bb2450c9a1a9fccb956909f@siemens.com> <CABCOCHRs7npz4nv3KnfHSGaDEuskPbdOSn-bjXt83r+46VEaRg@mail.gmail.com> <06674cb9709f4bd6bc2af297b929163f@siemens.com> <CABCOCHRGYM3nkUaX4_quu3JpznYXDdwejD11ppWni3wU8tEbkA@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512"; protocol="application/pgp-signature"
Date: Fri, 18 Jun 2021 16:09:49 -0400
Message-ID: <32390.1624046989@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/c95McG13uAF4weAJD1VkYXVNqww>
Subject: Re: [Anima] [netmod] [anima-wg/anima-brski-async-enroll] Definition of new assertion type (agent-proximity) for the voucher (#18)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2021 20:10:00 -0000

Kent, my appologies for not putting enough context with my email.
Andy, thanks for the clarification.

As I understand, in order to add a new assertion to RFC8366's leaf
"assertion", we have to revise RFC8366.

Question: was it a mistake to make this an assertion, if we wanted to
be able extend it?
Can we do this via IANA registry in some way instead?

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email