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

[Paul Kyzivat <[e-mail]>]

On 8/4/16 12:45 PM, Christer Holmberg wrote:
> Hi Dave,
>
> Since this discussion seems to be about JSON and SIP in general, perhaps it should be moved to SIPCORE?
>
> Note that I am authoring another draft (not related to STIR), which also defines a signature calculated based on SIP header field information. It has been suggested - by one of the SIPCORE chairs - to calculate and carry the signature as a JWT :)

I have been loosely following this discussion. IIUC, one of Dave's 
arguments is that SIP implementations don't currently involve JSON, so 
introducing it with STIR will further complicate those implementations.

But, again IIUC, the use of JSON with passport doesn't require anyone to 
*parse* JSON. It is only necessary to *generate* a very special purpose 
JSON and then generate a signature over it.

If I'm right about that, the use of JSON will be no particular burden. 
It doesn't require a JSON "stack". Generating it is hardly more 
complicated than what it replaced: generating a string that is a 
concatenation of a number of bits of data separated by colons.

I don't see what the problem is.

	Thanks,
	Paul