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

Brian Campbell <bcampbell@pingidentity.com> Mon, 25 March 2019 12:59 UTC

Return-Path: <bcampbell@pingidentity.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 3539512047C for <id-event@ietfa.amsl.com>; Mon, 25 Mar 2019 05:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.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 PgPXfhiiTa2Z for <id-event@ietfa.amsl.com>; Mon, 25 Mar 2019 05:59:17 -0700 (PDT)
Received: from mail-it1-x12b.google.com (mail-it1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3AE2120452 for <id-event@ietf.org>; Mon, 25 Mar 2019 05:59:17 -0700 (PDT)
Received: by mail-it1-x12b.google.com with SMTP id y63so2018933itb.5 for <id-event@ietf.org>; Mon, 25 Mar 2019 05:59:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bWx6Dcw2fVs7NFgfvVRPNsO4CvCGrfzAy5T9NqHow9Q=; b=m2+rZZ8ra1xJW0fJHNFnsA8UsB2Pe7WGhpagR+JUl2SZ8f8WE/CXyWIIsCUPa0++bd XPQaj7b3sOCiHi3CbbRM/H9dCN8dxGfY7ryHFeTgyUYGiXKJs+pBWOnSgXoOekaDOI4l 90ryq8G6p0iItVq5PLfK1OVJ+UBlNmXIlgmMk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bWx6Dcw2fVs7NFgfvVRPNsO4CvCGrfzAy5T9NqHow9Q=; b=k0Cp+O8hT4E7zCUYMxHzT9cJbQvfYp9/k3QcblTh5WsvEtT8K+0sHU9TaBUHNQdZWQ sikqnOFZJWYKvFP8cZRXaA0P6n2axCfvLjb7B3XMvm/4Ir2dzvx2WoMVk2/wy1UVRzVE 4zFdouR3m0wfbxC7xyQrnDwwhuWtKGG9SsYKkdSyzkrnzd3fZtTXghNeKIg8fcrGtCtu uWUsaVD3PAwEZbJ/gmeVFoYmzSrtFaxY6NSclAs4HGr3JJaKQyxcOfuo5qN0rBnQ4BQW YMKzqWFuZyykJt4Fdc8CtPxdlDam7uKKA0IBWioPU1KDYeT7OSRhFuUTIfHF/q8WOE3o 4LHQ==
X-Gm-Message-State: APjAAAVgI/3mb1SiH3kVM3Gxtep3Jb/p1X2uKvcCA53BnUM8pcU7d0Eb Ct7u1MieWqBf/C25w0FcdXPqL6HobqFEsCK5CYxulcqjoFu2iz4kFpVvl0d9GMp/GgDtbxaBgIE 0otZ4mfsr7G8FOfpWug==
X-Google-Smtp-Source: APXvYqw1g3naq1/8Z7hCg07a9eHN33+KJ9VNCER77tcXr2/IriDhzclP7ncUCZKZvmiaxbcS2RchPrf7ou44f8CqQy4=
X-Received: by 2002:a24:c906:: with SMTP id h6mr7865060itg.45.1553518756841; Mon, 25 Mar 2019 05:59:16 -0700 (PDT)
MIME-Version: 1.0
References: <155233425224.23102.17382771448465382026@ietfa.amsl.com> <7BE600FD-F838-45E2-A8C1-0BB13D96BB9C@amazon.com>
In-Reply-To: <7BE600FD-F838-45E2-A8C1-0BB13D96BB9C@amazon.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 25 Mar 2019 06:58:51 -0600
Message-ID: <CA+k3eCSWzx6qK2hj+YAVgMvz5dwvzxB_LMuYWKDqYBoiK77mGg@mail.gmail.com>
To: "Richard Backman, Annabelle" <richanna=40amazon.com@dmarc.ietf.org>
Cc: "id-event@ietf.org" <id-event@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a76e470584eac5fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/fWMcPOytBhDUoMpTk-6sXtZ0b6g>
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
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: Mon, 25 Mar 2019 12:59:23 -0000

https://mailarchive.ietf.org/arch/msg/id-event/Xipj4J3umYa2EnGBU2Q0dUM-Xy8
was a question about the JWT claim name or lack thereof in
draft-ietf-secevent-subject-identifiers -02 that didn't garner any response
but I still think warrants some treatment in the document.

On Mon, Mar 11, 2019 at 2:04 PM Richard Backman, Annabelle <richanna=
40amazon.com@dmarc.ietf.org> wrote:

> 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
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._