Re: [Id-event] I-D Action: draft-ietf-secevent-subject-identifiers-11.txt

Justin Richer <jricher@mit.edu> Wed, 27 April 2022 00:36 UTC

Return-Path: <jricher@mit.edu>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D58DC1D3876; Tue, 26 Apr 2022 17:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 EEAD8DhhwTR1; Tue, 26 Apr 2022 17:36:31 -0700 (PDT)
Received: from outgoing-exchange-1.mit.edu (outgoing-exchange-1.mit.edu [18.9.28.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66F87C1D191F; Tue, 26 Apr 2022 17:36:27 -0700 (PDT)
Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 23R0aP2F024510; Tue, 26 Apr 2022 20:36:25 -0400
Received: from w92expo18.exchange.mit.edu (18.7.74.72) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Tue, 26 Apr 2022 20:35:42 -0400
Received: from oc11expo18.exchange.mit.edu (18.9.4.49) by w92expo18.exchange.mit.edu (18.7.74.72) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Tue, 26 Apr 2022 20:36:24 -0400
Received: from oc11expo18.exchange.mit.edu ([18.9.4.49]) by oc11expo18.exchange.mit.edu ([18.9.4.49]) with mapi id 15.00.1497.023; Tue, 26 Apr 2022 20:36:24 -0400
From: Justin Richer <jricher@mit.edu>
To: "id-event@ietf.org" <id-event@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Thread-Topic: [Id-event] I-D Action: draft-ietf-secevent-subject-identifiers-11.txt
Thread-Index: AQHYVbnqV6/yskMWAUubzgO2iAUFI60C8ZBK
Date: Wed, 27 Apr 2022 00:36:24 +0000
Message-ID: <0c05d86964e544818799c817287ebe2e@oc11expo18.exchange.mit.edu>
References: <165057098708.9791.15663968524996247808@ietfa.amsl.com>
In-Reply-To: <165057098708.9791.15663968524996247808@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.58.38.206]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/qZwbQCQIJjE-z0gpu7JVXIWEjQE>
Subject: Re: [Id-event] I-D Action: draft-ietf-secevent-subject-identifiers-11.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2022 00:36:33 -0000

I strongly disagree with the editor's removal of "did" from the spec and the reasons for doing so.pushing the semantic information off into a lower layer is not helpful in terms of complexity nor application. Now an application will need to parse the various url's to know what they are instead of being told in the data structure what's in there. 

-Justin
________________________________________
From: Id-event [id-event-bounces@ietf.org] on behalf of internet-drafts@ietf.org [internet-drafts@ietf.org]
Sent: Thursday, April 21, 2022 3:56 PM
To: i-d-announce@ietf.org
Cc: id-event@ietf.org
Subject: [Id-event] I-D Action: draft-ietf-secevent-subject-identifiers-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Security Events WG of the IETF.

        Title           : Subject Identifiers for Security Event Tokens
        Authors         : Annabelle Backman
                          Marius Scurtescu
                          Prachi Jain
        Filename        : draft-ietf-secevent-subject-identifiers-11.txt
        Pages           : 22
        Date            : 2022-04-21

Abstract:
   Security events communicated within Security Event Tokens may support
   a variety of identifiers to identify subjects related to the event.
   This specification formalizes the notion of subject identifiers as
   structured information that describe a subject, and named formats
   that define the syntax and semantics for encoding subject identifiers
   as JSON objects.  It also defines a registry for defining and
   allocating names for such formats, as well as the sub_id JSON Web
   Token (JWT) claim.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-secevent-subject-identifiers-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-secevent-subject-identifiers-11


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
Id-event mailing list
Id-event@ietf.org
https://www.ietf.org/mailman/listinfo/id-event