JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants
draft-ietf-oauth-jwt-bearer-12
Yes
(Kathleen Moriarty)
No Objection
(Adrian Farrel)
(Alia Atlas)
(Barry Leiba)
(Benoît Claise)
(Brian Haberman)
(Jari Arkko)
(Joel Jaeggli)
(Martin Stiemerling)
(Ted Lemon)
Note: This ballot was opened for revision 10 and is now closed.
Kathleen Moriarty Former IESG member
Yes
Yes
(for -10)
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
(for -10)
Unknown
Alia Atlas Former IESG member
No Objection
No Objection
(for -10)
Unknown
Barry Leiba Former IESG member
No Objection
No Objection
(for -10)
Unknown
Benoît Claise Former IESG member
No Objection
No Objection
(for -10)
Unknown
Brian Haberman Former IESG member
No Objection
No Objection
(for -10)
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(for -10)
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
(for -10)
Unknown
Martin Stiemerling Former IESG member
No Objection
No Objection
(for -10)
Unknown
Pete Resnick Former IESG member
No Objection
No Objection
(2014-10-14 for -10)
Unknown
I'm not going to repeat stuff that is identical to draft-ietf-oauth-saml2-bearer (and I did find that using <https://www.ietf.org/rfcdiff?url1=draft-ietf-oauth-saml2-bearer-21&difftype=--html&submit=Go%21&url2=draft-ietf-oauth-jwt-bearer-10> was very helpful). Please refer to my comments on that document.
Richard Barnes Former IESG member
(was Discuss)
No Objection
No Objection
(2014-10-15 for -11)
Unknown
"keyed message digest" -> "MAC" Both this and the SAML document could save a lot of bits by just being subsections of the -assertions document.
Stephen Farrell Former IESG member
No Objection
No Objection
(2014-10-16 for -10)
Unknown
- 2.1, assertion parameter: How come this one does not talk about base64url whereas the saml one does?
Ted Lemon Former IESG member
No Objection
No Objection
(for -10)
Unknown