Re: [stir] JWT/JSON (was - Re: Review of: draft-ietf-stir-passport-05)

[Christer Holmberg <[e-mail]>]

Hi,

>> The idea (afaik) is
>> to split the encoded string into different pieces, and place those in 
>> different SIP header field/parameters. But, HOW that split is done, 
>> and how the string is re-generated on the receiving side, must be clarified.
>
> The need for this additional packaging is a basic specification requirement.  (Again, I don't
> understanding submitting a document for last call that is missing basic specification details.)
>
> I also don't understand the need for breaking the json result into multiple SIP header fields.

It's actually within one single header field, but one piece is sent as a header field value, while another piece is sent as a header field parameter value.

Example (simplified):

	Identity: <one-piece>;param=<another-piece>

>Why isn't it just stuffed into a single header field, like STIR-Signature: or the like?

That was my question too. Something like:

	Identity:<the-whole-piece>

But, at the end of the day, I want something that works, and Jon promised to describe how the "splitting" works in the next revision of the draft.

Regards,

Christer