Re: [Id-event] Use case document

Whatever works for you - and that's the whole point of *individual* I-Ds.

Thanks,

     Yaron

On 04/05/17 18:25, Marius Scurtescu wrote:
> Do we need one document for all use cases (all profiles) or one for 
> each profiles?
>
> I am happy to create the one document or the one for RISC (if one per 
> profile).
>
> Marius
>
> On Thu, May 4, 2017 at 3:36 AM, Yaron Sheffer <yaronf.ietf@gmail.com 
> <mailto:yaronf.ietf@gmail.com>> wrote:
>
>     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&gt>; 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
>>>     <https://www.ietf.org/mailman/listinfo/id-event>
>>
>
>