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

"Richard Backman, Annabelle" <richanna@amazon.com> Mon, 11 March 2019 20:04 UTC

Return-Path: <prvs=9667c2ea0=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 741871310F1; Mon, 11 Mar 2019 13:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 oyFFO3juhwvv; Mon, 11 Mar 2019 13:04:25 -0700 (PDT)
Received: from smtp-fw-9101.amazon.com (smtp-fw-9101.amazon.com [207.171.184.25]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D37FA1311AB; Mon, 11 Mar 2019 13:04:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1552334663; x=1583870663; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=192CUbLaC8r21zLffZ0wXzOtfo43aj/Oo+foxQv5TF0=; b=qK5WI5X5+5gRFzRikLL6fBSuD9CFflv3fL6kxbmoh9sGWO+pwTtBFrus 71No7q7H14B/9L2MNJKWdX+cro4Q6Dv5grPS/vgDJoJIe7Q8Pn74nkDEv YEn7JkLRn5M1rDWZ/scYBRmhHQjkHFGVkn94boee6VEfPFOxnkLZtVadG Y=;
X-IronPort-AV: E=Sophos;i="5.58,468,1544486400"; d="scan'208";a="792744658"
Received: from sea3-co-svc-lb6-vlan3.sea.amazon.com (HELO email-inbound-relay-1d-474bcd9f.us-east-1.amazon.com) ([10.47.22.38]) by smtp-border-fw-out-9101.sea19.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Mar 2019 20:04:21 +0000
Received: from EX13MTAUWC001.ant.amazon.com (iad55-ws-svc-p15-lb9-vlan3.iad.amazon.com [10.40.159.166]) by email-inbound-relay-1d-474bcd9f.us-east-1.amazon.com (8.14.7/8.14.7) with ESMTP id x2BK4GL8075274 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 11 Mar 2019 20:04:20 GMT
Received: from EX13D11UWC002.ant.amazon.com (10.43.162.174) by EX13MTAUWC001.ant.amazon.com (10.43.162.135) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 11 Mar 2019 20:04:19 +0000
Received: from EX13D11UWC004.ant.amazon.com (10.43.162.101) by EX13D11UWC002.ant.amazon.com (10.43.162.174) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 11 Mar 2019 20:04:19 +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.1367.000; Mon, 11 Mar 2019 20:04:19 +0000
From: "Richard Backman, Annabelle" <richanna@amazon.com>
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-03.txt
Thread-Index: AQHU2ETVglDzm7wOT0uF8/wFbXJIkaYGZVaA
Date: Mon, 11 Mar 2019 20:04:19 +0000
Message-ID: <7BE600FD-F838-45E2-A8C1-0BB13D96BB9C@amazon.com>
References: <155233425224.23102.17382771448465382026@ietfa.amsl.com>
In-Reply-To: <155233425224.23102.17382771448465382026@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.0.180812
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.161.253]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6A2F5BEBBEDEE6419AC8225FBA212700@amazon.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Precedence: Bulk
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/auX-zB0GKBWA6zws7rDLviskOk0>
Subject: Re: [Id-event] I-D Action: draft-ietf-secevent-subject-identifiers-03.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Mar 2019 20:04:34 -0000

Hello all,

This update includes changes discussed at IETF 103, and on list since then.  The change log for -02 to -03 is:

   Draft 03 - AB:

   o  Added "account" type for "acct" URIs.

   o  Replaced "id-token-claims" type with "aliases" type.

   o  Added email canonicalization guidance.

   o  Updated semantics for "email", "phone", and "iss-sub" types.

-- 
Annabelle Richard Backman
AWS Identity
 

On 3/11/19, 12:58 PM, "Id-event on behalf of internet-drafts@ietf.org" <id-event-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:

    
    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
    	Filename        : draft-ietf-secevent-subject-identifiers-03.txt
    	Pages           : 11
    	Date            : 2019-03-11
    
    Abstract:
       Security events communicated within Security Event Tokens may support
       a variety of identifiers to identify the subject and/or other
       principals related to the event.  This specification formalizes the
       notion of subject identifiers as named sets of well-defined claims
       describing the subject, a mechanism for representing subject
       identifiers within a [JSON] object such as a JSON Web Token [JWT] or
       Security Event Token [SET], and a registry for defining and
       allocating names for these claim sets.
    
    
    The IETF datatracker status page for this draft is:
    https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/
    
    There are also htmlized versions available at:
    https://tools.ietf.org/html/draft-ietf-secevent-subject-identifiers-03
    https://datatracker.ietf.org/doc/html/draft-ietf-secevent-subject-identifiers-03
    
    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-secevent-subject-identifiers-03
    
    
    Please note that it may take a couple of minutes from the time of submission
    until the htmlized version and diff are available at tools.ietf.org.
    
    Internet-Drafts are also available by anonymous FTP at:
    ftp://ftp.ietf.org/internet-drafts/
    
    _______________________________________________
    Id-event mailing list
    Id-event@ietf.org
    https://www.ietf.org/mailman/listinfo/id-event