[Openid-specs-ab] Opinions sought about pre-final IETF spec references in errata

Nat Sakimura sakimura at gmail.com
Fri Aug 8 05:48:35 UTC 2014


Ok. Then, +1 for the rev.


2014-08-08 14:25 GMT+09:00 Mike Jones <Michael.Jones at microsoft.com>:

>  Per 1 – I did the investigation earlier today on the only spec affected
> by the JWS Header -> JOSE Header change is Core, which we’re already
> changing.
>
>
>
> Per 2 – it’s a very limited task.
>
>
>
> Per 3 – if we’re going to apply errata, we might as well bring the spec up
> to date with what’s happened in the specs we depend upon.
>
>
>
> *From:* openid-specs-ab-bounces at lists.openid.net [mailto:
> openid-specs-ab-bounces at lists.openid.net] *On Behalf Of *Nat Sakimura
> *Sent:* Thursday, August 07, 2014 10:15 PM
> *To:* Brian Campbell
> *Cc:* openid-specs-ab at lists.openid.net
> *Subject:* Re: [Openid-specs-ab] Opinions sought about pre-final IETF
> spec references in errata
>
>
>
> Right.
>
>
>
> My concerns are:
>
>
>
> 1) if there are significant change in the terminology that may cause
> changes in multiple specs.
>
>     IMHO, all of the spec suite should use a consistent terminology, and
> adopting the current
>
>     draft JWx means potentially we have to updated all of them instead of
> just Core.
>
>     This may be a larger than what we want to do right now or small enough
> that we can do it.
>
>     I have no data point on this.
>
> 2) if it is more than a moderate task, then would there be a risk that we
> would have to
>
>     repeat it when it becomes the RFC.
>
> 3) would not the frequent revving in this respect cause the impression of
> the instability?
>
>
>
> If all of them are acceptable risk, then lets do the rev.
>
>
>
> Nat
>
>
>
> 2014-08-08 7:52 GMT+09:00 Brian Campbell <bcampbell at pingidentity.com>:
>
> Likewise, I prefer updating the pre-final spec references. My motivation
> in asking was only that if there were significant effort or risk in doing
> an interim update, it might be worthwhile to wait for the RFCs. But it
> doesn't sound like that's the case so updating with this errata makes sense.
>
>
>
> On Thu, Aug 7, 2014 at 11:44 AM, Torsten Lodderstedt <
> torsten at lodderstedt.net> wrote:
>
> I prefer updating the pre-final spec references
>
>
> Am 07.08.2014 um 19:11 schrieb Mike Jones <Michael.Jones at microsoft.com>:
>
>  We’re soon to publish errata for the final OpenID Connect specs.  Brian
> Campbell asked on today’s call whether we should update the pre-final IETF
> spec references at the same time, given that there have been no breaking
> changes.  As background, the current JOSE specs are at draft 31, whereas
> we’re referencing draft -18.  The new drafts are clearer, but mean the same
> thing.  The one terminology change that would go with this would be
> updating the terms JWS Header and JWE Header to the new term JOSE Header,
> which is what’s used in the current IETF specs.
>
>
>
> As further background, as discussed on the call, it could be up to another
> year before the JOSE and JWT specs are final.  The same could be true for
> the OAuth Assertions specs.
>
>
>
> Which do you prefer?
>
>   - updating the pre-final spec references
>
>   - making the minimum errata changes possible to the final specs
>
>
>
>                                                             -- Mike
>
>
>
>   _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>
>
>
>   --
>
> [image: Ping Identity logo] <https://www.pingidentity.com/>
>
> *Brian Campbell*
> Distinquished Engineer
>
> *@*
>
> bcampbell at pingidentity.com
>
> [image: phone]
>
> +1 720.317.2061
>
> Connect with us…
>
> [image: twitter logo] <https://twitter.com/pingidentity>[image: youtube
> logo] <https://www.youtube.com/user/PingIdentityTV>[image: LinkedIn logo]
> <https://www.linkedin.com/company/21870>[image: Facebook logo]
> <https://www.facebook.com/pingidentitypage>[image: Google+ logo]
> <https://plus.google.com/u/0/114266977739397708540>[image: slideshare
> logo] <http://www.slideshare.net/PingIdentity>[image: flipboard logo]
> <http://flip.it/vjBF7>[image: rss feed icon]
> <https://www.pingidentity.com/blogs/>
>
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>
>
>
>
>
> --
> Nat Sakimura (=nat)
>
> Chairman, OpenID Foundation
> http://nat.sakimura.org/
> @_nat_en
>



-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20140808/ecbc8d80/attachment.html>


More information about the Openid-specs-ab mailing list