[jose] #17: add 'aud' and 'iss' to 4.1 Reserved Header Parameter Names

["jose issue tracker" <[e-mail]>]

#17: add 'aud' and 'iss' to 4.1 Reserved Header Parameter Names

 Recipients of an encrypted token sometimes are not the audience, and may
 not know who the issuer is. Allowing these values to be in the header
 enables a recipient to have a hint if the token needs to be handed to
 another party for processing, and a hint of who the issuer was. These
 values are not confirmed until validation of the token has been performed,
 but enables the appropriate parties and keys to be used to validate.

 Suggested added text:

 4.1.x The "iss" (issuer) Header Parameter

 The "iss" (issuer) header parameter identifies the principal that
 issued the JWT.  The processing of this header parameter is generally
 application specific.  The "iss" value is case sensitive.  This
 header parameter is OPTIONAL.

 4.1.x The "aud" (audience) Header Parameter

 The "aud" (audience) header parameter identifies the audience that the
 JWT is intended for.  The principal intended to process the
 JWT MUST be identified with the value of the audience header parameter.
 If
 the principal processing the header parameter does not identify itself
 with the
 identifier in the "aud" header parameter value then the JWT MUST be
 rejected.  The interpretation of the audience value is generally
 application specific.  The "aud" value is case sensitive.  This
 header parameter is OPTIONAL.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-jose-json-web-
  [e-mail]   |  [e-mail]
     Type:  enhancement  |     Status:  new
 Priority:  major        |  Milestone:
Component:  json-web-    |    Version:
  encryption             |   Keywords:
 Severity:  -            |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/17>
jose <http://tools.ietf.org/jose/>