<Chair>

Sorry for the delay in getting these out, I have had network issues which prevented me from doing so earlier.

The Minutes are now available at http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-interim-2013-jose-1

Note that we are looking to hold a next virtual interim sometime during mid-June.  Probably the week of June 17 if memory serves.

Jim

FYI, this note had previously been sent to the JOSE interim working group meeting participants.  It discusses the correspondences between the agreed-upon JSON Serialization and Compact Serialization formats and how to transform one into the other.

                                                            -- Mike

A transformation from JWS and JWE objects using the compact serializations to ones using the JSON Serialization is always possible as simple syntactic transformation.  The transformation from the compact JWS “hdr.msg.sig” into a JSON-serialized JWS is:

  {"protected":"hdr",

   "signatures":[{"signature":"sig"}],

   "payload":"msg"

  }

The transformation from the compact JWE “hdr.ekey.iv.ct.tag” into a JSON-serialized JWE is:

  {"protected":"hdr",

   "recipients":[{"encrypted_key":"ekey"}],

   "initialization_vector":"iv",

   "ciphertext":"ct",

   "authentication_tag":"tag"

  }

Transformations from JSON Serializations for single recipients into the Compact Serializations are always possible.  When the “header” fields (containing unprotected header parameter values) aren’t used, the transformation is purely syntactic – being the inverse of those above.

When “header” fields are used, the contents of their JSON objects are merged into the “protected” header object contents, with the resulting merged header contents being used as the header for the compact serializations.  For instance, this JWE:

  {"protected":"base64url(“{"enc":"A128GCM"}”)",

   "header":{"kid":"3"},

   "recipients":[

    {"header":{"alg":"A128KW"},

     "encrypted_key":"ekey"}],

   "initialization_vector":"iv",

   "ciphertext":"ct",

   "authentication_tag":"tag"

  }

Would use this header value in the compact serialization:

  base64url(“{"enc":"A128GCM","kid":"3","alg":"A128KW"}”)

The rest of the JSON serialization -> compact serialization is purely syntactic, and as above.

By design, a transformation from a multi-recipient JWE or multi-signature JWS to the compact serializations is not possible.

                                                            -- Mike

From: John Bradley
Sent: 5/1/2013 11:50 AM
To: Richard Barnes
Cc: Jim Schaad; Mike Jones; Pete Resnick; Sean Turner; Matt Miller; Joe Hildebrand; Peter Saint-Andre; Brian Campbell; Karen O'Donoghue; Eric Rescorla; Hannes Tschofenig
Subject: Re: Draft write-up of discussion on JSON Serialization with some non-protected fields