Re: [Id-event] Use case document
Yaron Sheffer <yaronf.ietf@gmail.com> Thu, 04 May 2017 10:36 UTC
Return-Path: <yaronf.ietf@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 0D34F12E85E for <id-event@ietfa.amsl.com>; Thu, 4 May 2017 03:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.99
X-Spam-Level:
X-Spam-Status: No, score=0.99 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 P9JX5uwFJkVE for <id-event@ietfa.amsl.com>; Thu, 4 May 2017 03:36:20 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (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 13045129ACC for <id-event@ietf.org>; Thu, 4 May 2017 03:36:20 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id z52so5378991wrc.2 for <id-event@ietf.org>; Thu, 04 May 2017 03:36:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=h8Rs3LSZRl1dswtfAw+U0OQAmv98W1InfLMRUQUuR6w=; b=ffFsGF/vfq41msirBThMmdB3iKlFOw3MEZfKJbu3ZnKR4DnzRBNNceYnTR93byaKdU eCKzpPsg6zeAEPDM4jfv6X4VCwatzo5LEhoXPwrC+MCFZ/YYE8IheqtmRYOhRBohG0Hx uaShxuzw8ei50QofBZH3oP2wrYO2QaqdBbhFYy+Rvpwc/9GWoXVgtCJx9D9yRkV2mozO KDxnuqJEBdYDbevOtz+vLJv37YElnE6yvU6v0/GmC8jWtPEi6h75CLDRCRHY96A/MMmI 0gB8Fgmw/46d7+bLrtc+A1wCbz29roN91W8Da0YmUkoovSu/FhsxqI6gQsvNxsnKhopu fpwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=h8Rs3LSZRl1dswtfAw+U0OQAmv98W1InfLMRUQUuR6w=; b=Vvblpu2J1aF6YaqoKVz7ojFa1ARKAqhQSsRRNWu3FSYq3rkYp21iENtu/tBWeX5wb9 78ckjuEfx5fTvM0MP2rc54zAYLZyrkGOHkMTa32xUBBJjRV6RfKrIFaKOkGPRS1kPR7a iM3hOUKg4Ygz9nzs2DCdSEqZcYbMw+NjQIPNVC/r3JH64/hH1OQ6Og29Xpxxis73+G5O 58u0imTvvsiMKlpi6zhiVwXARdCGYz6qY0HOvOwInqPgi6sHl9pwyG6LQDFVDfgPtKdZ lENWD8XbjUgwbOaZDYRhE4Ldt/Ww6wPI56oDYOJHf4aK0C0Mhn5UmOuwtuPNMGzSjdq7 iFcA==
X-Gm-Message-State: AN3rC/7KJC6ZOe8VYxihKsmHwe1o94lEbAJS3qxr6rZUiJPN7eRor9i/ W8jzNt4ZfCUw0w==
X-Received: by 10.223.169.230 with SMTP id b93mr28375782wrd.196.1493894178551; Thu, 04 May 2017 03:36:18 -0700 (PDT)
Received: from [172.18.133.122] (cowboy3.intuit.com. [65.204.229.13]) by smtp.gmail.com with ESMTPSA id c184sm932858wmd.2.2017.05.04.03.36.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 May 2017 03:36:17 -0700 (PDT)
To: Justin Richer <jricher@mit.edu>, Dick Hardt <dick.hardt@gmail.com>
References: <CAD9ie-tS8FcrggbNH3rmN17JNv6m+KKcTpVvNTsfBqH=-Okadg@mail.gmail.com> <2104A459-8402-4498-9F7F-3EED264DB4E8@oracle.com> <CAD9ie-tSZfcLvL4m4wctgdb86aFDSbbpY49Q0VboB0UYTwAyww@mail.gmail.com> <EC9C6ED5-0915-4C82-9ED5-DCFAB1A392BB@oracle.com> <CAD9ie-t5LPbF-saJuzSR=y=07n_sZ2ZHMH3fjJhwyAnEmrbHNA@mail.gmail.com> <2F79A80F-AE98-4372-B096-C26ED77F4C3B@mit.edu>
Cc: Phil Hunt <phil.hunt@oracle.com>, SecEvent <id-event@ietf.org>, Marius Scurtescu <mscurtescu@google.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <c0addac5-fdad-8b22-6e44-3f1d0d139f26@gmail.com>
Date: Thu, 04 May 2017 13:36:10 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <2F79A80F-AE98-4372-B096-C26ED77F4C3B@mit.edu>
Content-Type: multipart/alternative; boundary="------------36E8FD8C8CBC2065E1EC65FF"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/ZHTx9sYMJPzbPXHR4wTSvxWoLgg>
Subject: Re: [Id-event] Use case document
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: Thu, 04 May 2017 10:36:23 -0000
My strong preference would be an individual I-D that (as Justin says) will NOT be pushed to RFC. Why an I-D at all? Because this is what IETF folks are used to, and it is referenced from the WG agenda and minutes. Thanks, Yaron On 04/05/17 07:57, Justin Richer wrote: > In fact, I’m going to ask that we *not* push a use cases document > toward RFC. Use case documents are wonderful tools for guiding > development, but should be discarded as artifacts of that process once > said process is completed (or even well on its way). > > As such, RFC, wiki, blog post, or anything referenced from the list > and easily findable works. > > — Justin > >> On May 3, 2017, at 4:45 PM, Dick Hardt <dick.hardt@gmail.com >> <mailto:dick.hardt@gmail.com>> wrote: >> >> As the more experienced chair, I will defer to Yaron for guidance. >> >> So far no one has expected it to be adopted as an RFC >> >> On Wed, May 3, 2017 at 4:39 PM, Phil Hunt<phil.hunt@oracle.com >> <mailto:phil.hunt@oracle.com>>wrote: >> >> Depends on what the WG wants. >> >> Email cases, >> Github posted document, >> Individual IDs posted to the working group, or >> an ID that gets adopted as a WG draft to end up as RFC (e.g. JOSE >> has RFC7165, and SCIM itself had RFC7642, Oauth had a WG >> drafthttps://tools.ietf.org/html/draft-ietf-oauth-use-cases-03 >> <https://tools.ietf.org/html/draft-ietf-oauth-use-cases-03>). >> >> Let us know what form and what format. >> >> We can also use one for OpenID Backchannel Logout. This is >> particularly important because it will be triggered by (or is >> related to) SCIM and by RISC events such as account resets, >> authentication factor changes etc. >> >> 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 May 3, 2017, at 4:31 PM, Dick Hardt <dick.hardt@gmail.com >>> <mailto:dick.hardt@gmail.com>> wrote: >>> >>> Hi Phil >>> >>> per >>> >>> https://mailarchive.ietf.org/arch/msg/id-event/FGuz9IsUMKqKeq2OjEBjCZ9cBcI >>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_id-2Devent_FGuz9IsUMKqKeq2OjEBjCZ9cBcI&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=bAI2H661a1QkItfplrd3RIM36dgAhF4WdbWxW8BOy4Q&s=ebhqgdwBfmclFpVn-cScD6uoiYqkmZVlRpC3XXk91Es&e=> >>> >>> you offered to put them in a WG doc (see quate below). Would >>> that not be an ID. Also, as I read over the document, it is hard >>> to follow what the use cases are as it is very verbose. >>> >>> On Tue, Apr 18, 2017 at 11:27 AM, Phil Hunt <phil.hunt@oracle.com> <mailto:phil.hunt@oracle.com>>; wrote: >>> >>> > All, >>> > >>> > Dick asked me if I would enumerate the SCIM use cases. Here is the SCIM >>> > case. Happy to put these somewhere in a working group document. >>> >>> On Wed, May 3, 2017 at 4:16 PM, Phil Hunt<phil.hunt@oracle.com >>> <mailto:phil.hunt@oracle.com>>wrote: >>> >>> My understanding was you wanted informal cases not IDs. The >>> SCIM cases have been posted to the mailing list. I believe >>> Marius is close on the RISC cases. >>> >>> Phil >>> >>> Oracle Corporation, Identity Cloud Services Architect & >>> Standards >>> @independentid >>> www.independentid.com >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.independentid.com&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=bAI2H661a1QkItfplrd3RIM36dgAhF4WdbWxW8BOy4Q&s=nBNO3_d_Mw4enpU54VxuTcoqCJSXkSSzg8LnXIkI5bg&e=> >>> phil.hunt@oracle.com <mailto:phil.hunt@oracle.com> >>> >>>> On May 3, 2017, at 3:56 PM, Dick Hardt >>>> <dick.hardt@gmail.com <mailto:dick.hardt@gmail.com>> wrote: >>>> >>>> Phil / Marius >>>> >>>> At the Chicago meeting, the two of you agreed to work on a >>>> document containing use cases you considered to be relevant >>>> for secevent so that the WG could decide which ones were in >>>> scope and which ones were out of scope. >>>> >>>> Checking in on the status of the use case document. Would >>>> you provide an update when you have a chance? >>>> >>>> /Dick >>>> >>>> _______________________________________________ >>>> Id-event mailing list >>>> Id-event@ietf.org <mailto: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=HWdy4Q9fHAYB3f-DZ2GWUJnaZDGcZQRaMexC2oHuR7g&s=JTwCxbXPzY_A62IiywTMIjRB-XsMY8UPafBs4oPwOTc&e= >>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_id-2Devent&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=HWdy4Q9fHAYB3f-DZ2GWUJnaZDGcZQRaMexC2oHuR7g&s=JTwCxbXPzY_A62IiywTMIjRB-XsMY8UPafBs4oPwOTc&e=> >>> >>> >>> >>> >>> -- >>> Subscribe to theHARDTWARE >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__hardtware.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=bAI2H661a1QkItfplrd3RIM36dgAhF4WdbWxW8BOy4Q&s=uVstd9R0_1UCdJ6s_rcX7xhYo6fyGuk22APkiwL0vpI&e=>mail >>> list to learn about projects I am working on! >>> _______________________________________________ >>> Id-event mailing list >>> Id-event@ietf.org <mailto: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=bAI2H661a1QkItfplrd3RIM36dgAhF4WdbWxW8BOy4Q&s=fzkXYKa7l9vPc2VrpDeaBZo7bH9cDrk9wUethVbuCS8&e= >>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_id-2Devent&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=JBm5biRrKugCH0FkITSeGJxPEivzjWwlNKe4C_lLIGk&m=bAI2H661a1QkItfplrd3RIM36dgAhF4WdbWxW8BOy4Q&s=fzkXYKa7l9vPc2VrpDeaBZo7bH9cDrk9wUethVbuCS8&e=> >> >> >> >> >> -- >> Subscribe to theHARDTWARE <http://hardtware.com/>mail list to learn >> about projects I am working on! >> _______________________________________________ >> Id-event mailing list >> Id-event@ietf.org <mailto:Id-event@ietf.org> >> https://www.ietf.org/mailman/listinfo/id-event >
- [Id-event] Use case document Dick Hardt
- Re: [Id-event] Use case document Phil Hunt
- Re: [Id-event] Use case document Dick Hardt
- Re: [Id-event] Use case document Phil Hunt
- Re: [Id-event] Use case document Dick Hardt
- Re: [Id-event] Use case document Justin Richer
- Re: [Id-event] Use case document Yaron Sheffer
- Re: [Id-event] Use case document Marius Scurtescu
- Re: [Id-event] Use case document Yaron Sheffer
- Re: [Id-event] Use case document Marius Scurtescu
- Re: [Id-event] Use case document Phil Hunt (IDM)
- Re: [Id-event] Use case document Dick Hardt
- Re: [Id-event] Use case document Marius Scurtescu
- Re: [Id-event] Use case document Mike Jones
- Re: [Id-event] Use case document Phil Hunt (IDM)
- Re: [Id-event] Use case document Dick Hardt
- Re: [Id-event] Use case document Dick Hardt
- Re: [Id-event] Use case document Yaron Sheffer