Re: [Id-event] I-D Action: draft-ietf-secevent-delivery-00.txt (and Verify Event)

Phil Hunt <phil.hunt@oracle.com> Mon, 31 July 2017 16:20 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 53B7713265A for <id-event@ietfa.amsl.com>; Mon, 31 Jul 2017 09:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 blZiA0t_rzgJ for <id-event@ietfa.amsl.com>; Mon, 31 Jul 2017 09:20:44 -0700 (PDT)
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 8AEAA132659 for <id-event@ietf.org>; Mon, 31 Jul 2017 09:20:41 -0700 (PDT)
Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v6VGKc8R013301 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 31 Jul 2017 16:20:38 GMT
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0021.oracle.com (8.14.4/8.14.4) with ESMTP id v6VGKcl4017246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 31 Jul 2017 16:20:38 GMT
Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id v6VGKccp022671; Mon, 31 Jul 2017 16:20:38 GMT
Received: from [192.168.1.46] (/70.70.142.148) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 31 Jul 2017 09:20:38 -0700
From: Phil Hunt <phil.hunt@oracle.com>
Message-Id: <FE9A1FB8-0DC5-48F6-853F-6E1733DA5A5B@oracle.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B88C4C63-65DA-4AD8-8E66-B3CF79D7ADA6"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 31 Jul 2017 09:20:35 -0700
In-Reply-To: <150130555312.20751.6664832712498006194@ietfa.amsl.com>
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, Marius Scurtescu <mscurtescu@google.com>
To: ID Events Mailing List <id-event@ietf.org>
References: <150130555312.20751.6664832712498006194@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3273)
X-Source-IP: aserv0021.oracle.com [141.146.126.233]
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/nxh0KZb6GK7Y8UsRCxkWFIWD3ek>
Subject: Re: [Id-event] I-D Action: draft-ietf-secevent-delivery-00.txt (and Verify Event)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.22
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, 31 Jul 2017 16:20:47 -0000

As requested by Yaron, I have posted the delivery draft unchanged as the WG draft.

Marius made a suggestion that as per discussion in Prague that the Verify Event be removed from the Delivery draft and potentially placed in an upcoming control plane draft (to be proposed).

After some thinking, I propose the Verify Event be placed into the SET Token draft. It would actually be a good thing to have at least one “normative” event defined in SET Token. 

If the group is agreeable, I am happy to propose some modified Verify Event definition text to move into the SET Token spec.  Note: SET Token is or is about to be WGLC.  Chairs: Can we consider this?

I would suggest we only move Verify to Control Plane if there is a specific reason (eg. distinct or separate use cases that may be specific to some profiles) why it is better suited there.

If there is no objection, I will:
* Remove the Verify Event from the Delivery Spec on its next regular update
* Update SET Token Spec with Verify Event, subject to guidance in regards to WGLC.

Phil

Oracle Corporation, Identity Cloud Services Architect & Standards
@independentid
www.independentid.com <http://www.independentid.com/>phil.hunt@oracle.com <mailto:phil.hunt@oracle.com>
> On Jul 28, 2017, at 10:19 PM, 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           : SET Token Delivery Using HTTP
>        Authors         : Phil Hunt
>                          Marius Scurtescu
>                          Morteza Ansari
>                          Anthony Nadalin
>                          Annabelle Richard Backman
> 	Filename        : draft-ietf-secevent-delivery-00.txt
> 	Pages           : 28
> 	Date            : 2017-07-28
> 
> Abstract:
>   This specification defines how a series of security event tokens
>   (SETs) may be delivered to a previously registered receiver using
>   HTTP POST over TLS initiated as a push to the receiver, or as a poll
>   by the receiver.  The specification also defines how delivery can be
>   assured subject to the SET Token Receiver's need for assurance.
> 
> 
> The IETF datatracker status page for this draft is:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dsecevent-2Ddelivery_&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=-776NP5LxWSJp_f1PMNn10AECHMGYqhgPsPTqXr4srE&s=pc0m7nhCLHj3Mab6Ppgz8m3HF_kwzH4EKFO6jtzNYfE&e= 
> 
> There are also htmlized versions available at:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dsecevent-2Ddelivery-2D00&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=-776NP5LxWSJp_f1PMNn10AECHMGYqhgPsPTqXr4srE&s=6jsUPOsyCumT0ZD-nr6TrlbMzPGgPWZ4OVQjSEr1aOo&e= 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dietf-2Dsecevent-2Ddelivery-2D00&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=-776NP5LxWSJp_f1PMNn10AECHMGYqhgPsPTqXr4srE&s=IX4vI17s3YIk7uq1W2aVRxUHH8ybXQZxgyNJLr1H_Ug&e= 
> 
> 
> 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:
> https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_internet-2Ddrafts_&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=-776NP5LxWSJp_f1PMNn10AECHMGYqhgPsPTqXr4srE&s=M-c_zQSJ7nJg1SbvMQqc2f2yJFUnTDPT9IMX_-h9Fyw&e= 
> 
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_id-2Devent&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=-776NP5LxWSJp_f1PMNn10AECHMGYqhgPsPTqXr4srE&s=aTnebfvP2aZrcA1xIr41D3o8_5Qpyx_NGC7S1km7uKE&e=