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

Dick Hardt <dick.hardt@gmail.com> Wed, 24 July 2019 22:06 UTC

Return-Path: <dick.hardt@gmail.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 4E8851202EC; Wed, 24 Jul 2019 15:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ON_758P_VtWR; Wed, 24 Jul 2019 15:06:20 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 C002B120112; Wed, 24 Jul 2019 15:06:19 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id c19so32996256lfm.10; Wed, 24 Jul 2019 15:06:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=n/fo//67nFEAMwuwVZRgR3yeindcIMdsKYl7st5JYHE=; b=tXkFWLj5orAAv6sruX2IVI5ksi1TmJINgYC8xGw5DqSok+cPrWh3L+IhWRf682UWqh 7tGQF/jRz4MGLWyVEdJjqKEBBP7pJdnQI2wn5G5qLapHS8U4CiXJJe5+XdDD4ROsBjFj hBjI5Iwiw9bPqIDm9+N8MPo92R0YjEAEFzJiIqacYyrjIIW/HqXZ8PqZvPQGWMBIUQPi cOD2NbqT0g6umXZpUiHLIVfQ4DOI3sKmBfBxbh+wunJslVWwuN3n1b123Ih3kWot+pXT gS8TO241DnRIpVScp0ZL+MJGja03i13tItj4i6E7jBlf0F8ydau9xmcxnI13t23GC9ZA a7Bg==
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=n/fo//67nFEAMwuwVZRgR3yeindcIMdsKYl7st5JYHE=; b=MbQPQN1R909PcwWvP87DgZf1TZ0a01SnwUm2rN2f/9WP4eiIXL7xjsi/JZ3bZ2Kr6v ewbp+57Kx9XLGW4BxRlpkM66IQhV3Pv9D0XETPAEiVO3+6RQfhFf1xeZwKCCd7xFb+B+ oAK6ZPcYbyLYONu1ByooYdk3VaJGsOlTrOfiKyw3jCnfi1BKqsyTZ6zxaYsACDBvGdHy D8mtbesu7juKNN5+7+LHwaIjGFHuB0MQYyb8eoPpiDlyWAo9Jv6NcMzeYjF4Zk+akupW BSwYA+QgwjKG6dLAbLFEH/zYjaKSCPkdpHW1vD1nBzXzzYLajDwDl0cBCtCLyUsYiro0 Pa+w==
X-Gm-Message-State: APjAAAWDnlEgPSvJYD/gY0fpMLTdJFaUrNZtghs5bOUU9FQL++wppQi4 zh3pG0vyL2K/WCbtyq3Ip41PAZvcmaBPvFvh6ZFZaDrd
X-Google-Smtp-Source: APXvYqzuzhyI9k7ZvrTcJ9nLmKU8qxFzfIm26J6/kUEAJhX8iitBKTpM03Tp6svg/CLuLRWlc3sP9SFjrbMfTN+rjtE=
X-Received: by 2002:a19:8c57:: with SMTP id i23mr38502121lfj.192.1564005977710; Wed, 24 Jul 2019 15:06:17 -0700 (PDT)
MIME-Version: 1.0
References: <156400473292.14631.1343409782640781856@ietfa.amsl.com> <E270751A-9735-426A-90DD-55C3F7B57FE8@amazon.com>
In-Reply-To: <E270751A-9735-426A-90DD-55C3F7B57FE8@amazon.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Wed, 24 Jul 2019 17:06:05 -0500
Message-ID: <CAD9ie-s=HdJa4QRYsvEz5-pBBhM-s5Z4xuxXq1ZtTf0vJw=TGg@mail.gmail.com>
To: "Richard Backman, Annabelle" <richanna=40amazon.com@dmarc.ietf.org>
Cc: "i-d-announce@ietf.org" <i-d-announce@ietf.org>, "id-event@ietf.org" <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ba652e058e74848a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/45uaixg4-x89AQTHHfvtZ4gBzUM>
Subject: Re: [Id-event] I-D Action: draft-ietf-secevent-subject-identifiers-05.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: Wed, 24 Jul 2019 22:06:22 -0000

What was the reason to have a dash in the type “phone-number” rather than
an underscore “phone_number”?

On Wed, Jul 24, 2019 at 4:54 PM Richard Backman, Annabelle <richanna=
40amazon.com@dmarc.ietf.org> wrote:

> This update to the Subject Identifiers for Security Event Tokens draft
> addresses comments raised at the secevents working group session this week.
> Specifically:
>
> * Renamed the "phone" type to "phone-number" and its "phone" claim
>
>       to "phone_number".
>
>
> —
> Annabelle Backman
> AWS Identity
>
> On Jul 24, 2019, at 5:46 PM, "internet-drafts@ietf.org" <
> 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-05.txt
>    Pages           : 15
>    Date            : 2019-07-24
>
> 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-05
>
> https://datatracker.ietf.org/doc/html/draft-ietf-secevent-subject-identifiers-05
>
> A diff from the previous version is available at:
>
> https://www.ietf.org/rfcdiff?url2=draft-ietf-secevent-subject-identifiers-05
>
>
> 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
>