[Id-event] Fwd: New Version Notification for draft-ietf-secevent-token-01.txt

Phil Hunt <phil.hunt@oracle.com> Fri, 10 March 2017 05:21 UTC

Return-Path: <phil.hunt@oracle.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 4192F12941C for <id-event@ietfa.amsl.com>; Thu, 9 Mar 2017 21:21:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 7ASsOPi4ncUl for <id-event@ietfa.amsl.com>; Thu, 9 Mar 2017 21:21:08 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (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 D43581288B8 for <id-event@ietf.org>; Thu, 9 Mar 2017 21:21:07 -0800 (PST)
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v2A5L6Ms029418 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <id-event@ietf.org>; Fri, 10 Mar 2017 05:21:07 GMT
Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id v2A5L6vn025002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <id-event@ietf.org>; Fri, 10 Mar 2017 05:21:06 GMT
Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id v2A5L6eH009605 for <id-event@ietf.org>; Fri, 10 Mar 2017 05:21:06 GMT
Received: from [10.0.1.7] (/24.86.190.97) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 09 Mar 2017 21:21:06 -0800
From: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_03459693-8733-497F-BCAD-AD8F143D20FB"
Date: Thu, 09 Mar 2017 21:21:00 -0800
References: <148912292506.5730.1061332191325437031.idtracker@ietfa.amsl.com>
To: ID Events Mailing List <id-event@ietf.org>
Message-Id: <F9DE47C5-638F-466F-9A2D-45A2F1AC3E72@oracle.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-Source-IP: userv0021.oracle.com [156.151.31.71]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/cupl7sOSMa-nvay8QjeDZz_R6yE>
Subject: [Id-event] Fwd: New Version Notification for draft-ietf-secevent-token-01.txt
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Mar 2017 05:21:09 -0000

This update includes the terminology refinements discussed last week plus the editorial feedback from Yaron.

The draft does not include the recent discussion on sub/iss handling, nor does it include AT/IDToken/SET differentiation. As proposed by Yaron, we should keep discussing and work on it during the Chicago meeting.

As far as I remember this revision includes only editorial changes.

Phil

Oracle Corporation, Identity Cloud Architect & Standards
@independentid
www.independentid.com <http://www.independentid.com/>phil.hunt@oracle.com <mailto:phil.hunt@oracle.com>



> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-ietf-secevent-token-01.txt
> Date: March 9, 2017 at 9:15:25 PM PST
> To: "Phil Hunt" <phil.hunt@yahoo.com>, "Morteza Ansari" <morteza.ansari@cisco.com>, "Michael B. Jones" <mbj@microsoft.com>, "Michael Jones" <mbj@microsoft.com>, <secevent-chairs@ietf.org>, "William Denniss" <wdenniss@google.com>
> 
> 
> A new version of I-D, draft-ietf-secevent-token-01.txt
> has been successfully submitted by Phil Hunt and posted to the
> IETF repository.
> 
> Name:		draft-ietf-secevent-token
> Revision:	01
> Title:		Security Event Token (SET)
> Document date:	2017-03-09
> Group:		secevent
> Pages:		18
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-secevent-token-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-secevent-token/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-secevent-token-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-secevent-token-01
> 
> Abstract:
>   This specification defines the Security Event Token, which may be
>   distributed via a protocol such as HTTP.  The Security Event Token
>   (SET) specification profiles the JSON Web Token (JWT), which can be
>   optionally signed and/or encrypted.  A SET describes a statement of
>   fact from the perspective of an issuer that it intends to share with
>   one or more receivers.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
>