The payload and the ciphertext are actually quite different kinds of fields -
in particular, one is plain text and the other is encrypted. Calling them both
"data" would blur this distinction and potentially cause confusion. I'd rather
that we continued using different names when the things being named are
different.
-- Mike
From: Richard Barnes [mailto:[email protected]]
Sent: Wednesday, May 08, 2013 8:43 AM
To: Vladimir Dzhuvinov / NimbusDS
Cc: [email protected]; jose issue tracker;
[email protected]
Subject: Re: [jose] #20: Shorter names for JSON serialization
"iv" and "tag" would be OK. I still prefer "mac" over "tag", for consistency
with CMS, and just because I think MAC is a more uniformly used phrase.
What about "data" for "payload" and "ciphertext"?
On Wed, May 8, 2013 at 9:39 AM, Vladimir Dzhuvinov / NimbusDS
<[email protected]<mailto:[email protected]>> wrote:
+1 for "iv" and "tag"
--
Vladimir Dzhuvinov : www.NimbusDS.com<http://www.NimbusDS.com> :
[email protected]<mailto:[email protected]>
-------- Original Message --------
Subject: Re: [jose] #20: Shorter names for JSON serialization
From: Mike Jones
<[email protected]<mailto:[email protected]>>
Date: Tue, May 07, 2013 10:40 pm
To: Richard Barnes <[email protected]<mailto:[email protected]>>, Jim Schaad
<[email protected]<mailto:[email protected]>>
Cc:
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>,
jose issue tracker
<[email protected]<mailto:trac%[email protected]>>,
"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
What about "iv" and "tag"? For the other names, I'd
actually prefer staying with those that are full words rather than those
that are abbreviations of words, since they're more descriptive. But
I agree that "initialization_vector" and "authentication_tag"
were overkill.
-- Mike
From: Richard Barnes [mailto:[email protected]<mailto:[email protected]>]
Sent: Monday, May 06, 2013 2:51 PM
To: Jim Schaad
Cc: jose issue tracker;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
Subject: Re: [jose] #20: Shorter names for JSON serialization
Even that's the name for the corresponding field in CMS
AuthEnvelopedData and AuthenticatedData?
On Monday, May 6, 2013, Jim Schaad wrote:
I would be againist calling the authentication_tag mac. I don't object
to
something like AuthTag. It is not necessarily a MAC in all cases so
calling
it one make thing problematical - much like calling a mac a sig.
Jim
> -----Original Message-----
> From: [email protected]<mailto:[email protected]>
> [mailto:[email protected]<mailto:[email protected]>] On Behalf
Of
> jose issue tracker
> Sent: Monday, May 06, 2013 2:29 PM
> To:
> [email protected]<mailto:[email protected]>;
> [email protected]<mailto:[email protected]>
> Cc: [email protected]<mailto:[email protected]>
> Subject: [jose] #20: Shorter names for JSON serialization
>
> #20: Shorter names for JSON serialization
>
> I noticed as I was doing some programming with the JSON syntax for
JWE/JWS
> that the current field names in the JSON format are unnecessarily
> cumbersome. Nobody in the real world names a variable
> "initialization_vector", it's "iv". Proposed changes:
>
> || OLD || NEW ||
> || signatures || sigs ||
> || signature || sig ||
> || payload || data ||
> || recipients || keys ||
> || ciphertext || data ||
> || initialization_vector || iv ||
> || authentication_tag || mac ||
>
> --
>
-------------------------+----------------------------------------------
> -------------------------+---
> Reporter: [email protected]<mailto:[email protected]> | Owner:
> draft-ietf-jose-json-web-
> Type: defect |
> [email protected]<mailto:[email protected]>
> Priority: minor | Status: new
> Component: json-web- | Milestone:
> encryption | Version:
> Severity: - | Keywords:
>
-------------------------+----------------------------------------------
> -------------------------+---
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/20>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> [email protected]<mailto:[email protected]>
> https://www.ietf.org/mailman/listinfo/jose
_______________________________________________
jose mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/jose
_______________________________________________
jose mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/jose
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
