> -----Original Message----- > From: jose [mailto:[email protected]] On Behalf Of Martin Thomson > Sent: Tuesday, October 21, 2014 1:03 AM > To: ? Matt Miller > Cc: [email protected]; Richard Barnes; draft-ietf-jose-json-web- > [email protected]; Mike Jones; The IESG; [email protected] > Subject: Re: [jose] Richard Barnes' Discuss on draft-ietf-jose-json-web- > encryption-33: (with DISCUSS and COMMENT) > > On 20 October 2014 09:53, ? Matt Miller <[email protected]> wrote: > > As I think I've said in previous discussions about the JSON > > serialization, I can live with something verbose *BUT* would rather > > like a lighter syntax for the single-encrypt JSON serialization. > > While multiple recipients is not quite as rare in encryption as it is > > for signing, single-encrypt is still the more common usecase, and so > > optimizing for it seems like a good thing. > > I've had a similar concern. Multiple recipients is more the exception.
How much multiple recipients is the exception depends on the frequency of encrypting both for the recipient and for the sender or just for the recipient. S/MIME always has at least two recipients for encryption because the sender gets a copy as well. It is the case that single signing is the most common case in S/MIME. Jim > > _______________________________________________ > jose mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/jose _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
