Re: Web Object Encryption and Signing (WOES) at IETF

Seem two ways to approach it: just as there exist encoding rules to code asn1 abstract values (in cert type) as XML, there could be code to json, instead. or, a native structure is defined in json, assuming it can be canonicalized.

A third approach does exist. A very minimal der-encoded cert exists, with 1string extension: some json with native coding of xyz control system (eg pkix). H.p and I once suggested this, where JavaScript was used rather than json values. it was laughed at, at the time (when pki was at it's zenith).



On Feb 17, 2011, at 2:34 PM, Nathan <nathan@webr3.org> wrote:

> Peter Saint-Andre wrote:
>> Dear WebID folks,
>> Given the discussions here about simplifying the representation of
>> public keys, you might want to know that some IETF participants have
>> established a dedicated email list for discussion about requirements and
>> potential implementation of JSON to provide security services for
>> Web-based applications. You can subscribe here:
>> https://www.ietf.org/mailman/listinfo/woes
>> In addition, an informal side meeting is planned for this topic at IETF
>> 80 in Prague during the week of March 28.
> 
> wonderful, and good to see all the sec groups getting pinged about it, we (over in this xg) should definitely keep tabs and be as involved as we can - imo of course.
> 
> Cheers Peter,
> 
> Nathan
> 
>

Received on Friday, 18 February 2011 10:02:01 UTC