http://tools.ietf.org/html/rfc4106 calls it “Initialization Vector (IV)” so I
think the reasonable choices are either “initialization_vector” (the current
name) or “iv” (the possible shortened name). “Nonce” means very different
things in other protocols, so I think we really should steer completely clear
of it, to prevent confusion.
-- Mike
From: Manger, James H [mailto:[email protected]]
Sent: Tuesday, May 07, 2013 5:34 PM
To: Mike Jones; Richard Barnes; Jim Schaad
Cc: [email protected]; jose issue tracker;
[email protected]
Subject: RE: [jose] #20: Shorter names for JSON serialization
How about “nonce”, instead of “iv”?
“nonce” is used for the equivalent field in other RFCs about AEAD algorithms:
RFC 5116 AEAD, RFC 5297 SIV, RFC 3610 CCM. Some of these use the name “IV” for
different things than the AEAD nonce.
NIST 800-38D GCM does uses “IV”, though it is defined as “A nonce that is
associated with an invocation of authenticated encryption on a particular
plaintext and AAD”. RFC 5084 “CCM & GCM in CMS” even says:
“To have a common set of terms for AES-CCM and AES-GCM, the AES-GCM IV is
referred to as a nonce in the remainder of this document.”
--
James Manger
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Mike Jones
Sent: Wednesday, 8 May 2013 7:41 AM
To: Richard Barnes; Jim Schaad
Cc:
[email protected]<mailto:[email protected]>;
jose issue tracker; [email protected]<mailto:[email protected]>
Subject: Re: [jose] #20: Shorter names for JSON serialization
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
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
