[Openid-specs-heart] Updated Technical Specifications

[Eve Maler]

Hey all-- To see the blow-by-blow specifics of what has changed in the
specs published at the main bitbucket link
<http://openid.bitbucket.org/HEART/>, you can peruse the issues that were
closed related to them. To do this, start at that link and visit either the
Issues <https://bitbucket.org/openid/heart/issues?status=new&status=open>
tab that appears there directly, or the Repository
<https://bitbucket.org/openid/heart> tab and then the Issues link on the
left. You'll see that there are currently no open issues left; select the
"All" filter.

Issues 2, 3, 4, and 5 were dealt with in this round. (Issue 1 was closed
prior to our ballot.)

   - Issue 2 <https://bitbucket.org/openid/heart/issues/2/kid-field-in-jwts>
   was "'kid' field in JWTs".
      - Click on "<<cset 6af7a9b036bc
      <https://bitbucket.org/openid/heart/commits/6af7a9b036bc>>>" in the
      comment portion to see the exact text changes (in this case, just to the
      OAuth security profile).
      - This is a fairly minor technical change.
   - Issue 3 <https://bitbucket.org/openid/heart/issues/3/sub-in-jwt> was
   ""sub" in JWT".
      - It was resolved with no change to the specs.
   - Issue 4
   <https://bitbucket.org/openid/heart/issues/4/introspection-example-is-out-of-sync>
   was "Introspection example is out of sync".
      - Click on "<<cset f9dfea60316e
      <https://bitbucket.org/openid/heart/commits/f9dfea60316e>>>" in the
      comment portion to see the exact text changes (in this case, just to the
      OAuth security profile).
      - This is a really small technical change.
   - Issue 5
   <https://bitbucket.org/openid/heart/issues/5/clarify-compliance-of-different-components>
   was "Clarify compliance of different components".
      - Click on "<<cset dabd27b48f22
      <https://bitbucket.org/openid/heart/commits/dabd27b48f22>>>" in the
      comment portion to see the exact text changes (in this case, to
all of the
      security profiles).
      - This is the most "interesting" of the issues, related to the
      feedback we got about connecting the HEART profiles to the
outside world of
      specs that it lives in.

If you have a chance, try to take a quick look at the text changes by the
time we get onto the call tomorrow. Thanks!


*Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology
Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
Check out the 2016 schedule <https://summits.forgerock.com> for *ForgeRock
Summits and UnSummits*!

On Sat, Apr 30, 2016 at 11:02 AM, Justin Richer <jricher at mit.edu> wrote:

> We’ve updated the HEART specifications based on feedback during the first
> implementer’s draft period. The new specs have been checked into git and
> are available on the group’s page:
>
> http://openid.bitbucket.org/HEART/
>
>  — Justin
>
>
> _______________________________________________
> Openid-specs-heart mailing list
> Openid-specs-heart at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-heart
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20160501/d3e14f62/attachment.html>