[jose] #24: Move JWS headers into signature block

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

#24: Move JWS headers into signature block

 The JWS JSON serialization currently has a header and protected header at
 the top level and at the per-signature level.  The ones at the top level
 are unnecessary, since every signer can do things differently, and each
 can choose to sign different attributes.  So both protected and
 unprotected headers should move into the "signatures" objects.

 OLD:
 """
      {"protected":<integrity-protected shared header contents>",
       "unprotected":<non-integrity-protected shared header contents>",
       "payload":"<payload contents>"
       "signatures":[
        {"header":"<per-signature unprotected header 1 contents>",
         "signature":"<signature 1 contents>"},
        ...
        {"header":"<per-signature unprotected header N contents>",
         "signature":"<signature N contents>"}],
      }
 """

 NEW:
 """
      {
       "payload":"<payload contents>"
       "signatures":[
        {"header":"<per-signature unprotected header 1 contents>",
         "protected":"<per-signature protected header 1 contents>",
         "signature":"<signature 1 contents>"},
        ...
        {"header":"<per-signature unprotected header N contents>",
         "protected":"<per-signature protected header N contents>",
         "signature":"<signature N contents>"}],
      }
 """

 This makes the compact form equivalent to:

 {
     "payload": "<JWS Encoded Payload>",
     "signatures": [{
         "protected": "<JWS Encoded Header>",
         "signature": "<JWS Signature Value>"
     }]
 }

 It also makes detached signatures natural, since you just can take the
 object out of the signatures array.

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

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