IETF Logo Mail Archive

[Id-event] New revision: draft-ietf-secevent-subject-identifiers-07

"Richard Backman, Annabelle" <richanna@amazon.com> Tue, 09 March 2021 01:46 UTC

Return-Path: <prvs=695a2e310=richanna@amazon.com>
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 0E8F53A1C0A for <id-event@ietfa.amsl.com>; Mon, 8 Mar 2021 17:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.167
X-Spam-Level:
X-Spam-Status: No, score=-12.167 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.248, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.com
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 GNFFH4zet-im for <id-event@ietfa.amsl.com>; Mon, 8 Mar 2021 17:46:40 -0800 (PST)
Received: from smtp-fw-6001.amazon.com (smtp-fw-6001.amazon.com [52.95.48.154]) (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 358193A1C09 for <id-event@ietf.org>; Mon, 8 Mar 2021 17:46:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1615254400; x=1646790400; h=from:to:subject:date:message-id:mime-version; bh=HpmZfcBcFUHO1kuwyFz/n0bWD1iacz1s4tcR7jeczaQ=; b=P1QzIZFbxxUGGURxjYxQTy9AhqgXFFRD92JrLE3sZKM07h0v2QpgvpcA C08Uo8NadZtmGD5J+pGwMAITcsuQuNRZfEks05x2T695wTzX9v1O033Mk 7n2Nrkn6n4qK+SnnE/1ndj6Q6Vd/M2i8LCJ+iuNz6dTwsg+Mz3sKeXu7u Q=;
X-IronPort-AV: E=Sophos; i="5.81,233,1610409600"; d="scan'208,217"; a="96935501"
Received: from iad12-co-svc-p1-lb1-vlan2.amazon.com (HELO email-inbound-relay-1e-57e1d233.us-east-1.amazon.com) ([10.43.8.2]) by smtp-border-fw-out-6001.iad6.amazon.com with ESMTP; 09 Mar 2021 01:46:31 +0000
Received: from EX13MTAUWB001.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan3.iad.amazon.com [10.40.163.38]) by email-inbound-relay-1e-57e1d233.us-east-1.amazon.com (Postfix) with ESMTPS id E29C71417D1 for <id-event@ietf.org>; Tue, 9 Mar 2021 01:46:30 +0000 (UTC)
Received: from EX13D11UWC004.ant.amazon.com (10.43.162.101) by EX13MTAUWB001.ant.amazon.com (10.43.161.249) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 9 Mar 2021 01:46:30 +0000
Received: from EX13D11UWC004.ant.amazon.com (10.43.162.101) by EX13D11UWC004.ant.amazon.com (10.43.162.101) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 9 Mar 2021 01:46:30 +0000
Received: from EX13D11UWC004.ant.amazon.com ([10.43.162.101]) by EX13D11UWC004.ant.amazon.com ([10.43.162.101]) with mapi id 15.00.1497.012; Tue, 9 Mar 2021 01:46:30 +0000
From: "Richard Backman, Annabelle" <richanna@amazon.com>
To: "id-event@ietf.org" <id-event@ietf.org>
Thread-Topic: New revision: draft-ietf-secevent-subject-identifiers-07
Thread-Index: AQHXFIYG17lwGy79bU+yTnxc2JnJwA==
Date: Tue, 09 Mar 2021 01:46:29 +0000
Message-ID: <53698407-2007-4BD5-AF33-4B9F68B78534@amazon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3608.120.23.2.4)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.162.131]
Content-Type: multipart/alternative; boundary="_000_5369840720074BD5AF334B9F68B78534amazoncom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/D0F-o_RSA_X2wOeWi1upAqMnHY8>
Subject: [Id-event] New revision: draft-ietf-secevent-subject-identifiers-07
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 09 Mar 2021 01:46:42 -0000

Hello Security Events Working Group,

I have just published an update to the Subject Identifiers draft, making the following notable changes:


  1.  The term "Subject Identifier Type" has been replaced with "Identifier Format", and the `subject_type` member has been changed to `format`. This is part of an attempt to further emphasize the difference the fact that Subject Identifiers and Identifier Formats relate to identifiers themselves, not the subjects they identify.

     *   Note that this change applies to the IANA registry as well.

  2.  Added a section for considerations for specifications that define Identifier Formats, prohibiting them from defining rules that make assertions or declarations about the subject, rather than about the identifier.

  3.  A new format, `opaque` has been added. This is intended for scenarios where an opaque string is used as the identifier, and no additional semantics are asserted about it. (e.g., it is not to be parsed or interpreted as anything other than an identifier)

  4.  Clarified that "subject" is used in a generic sense, i.e., not specifically referring to subjects of JWTs. Also defined the term "JWT Subject" for the specific case, and updated the draft to use that when referring specifically to a subject of a JWT.

URL:            https://www.ietf.org/archive/id/draft-ietf-secevent-subject-identifiers-07.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-secevent-subject-identifiers
Htmlized:       https://tools.ietf.org/html/draft-ietf-secevent-subject-identifiers-07
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-secevent-subject-identifiers-07

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.

–
Annabelle Backman (she/her)
richanna@amazon.com<mailto:richanna@amazon.com>

v2.23.0 | Report a Bug | By Email