| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Matt,Should "EAD" in the above read "Associated Data"?On Jun 17, 2008, at 8:37 AM, Matt Ball wrote:Here is proposed text in fulfillment of the following action item:
AI 58, Matt: Look at 1619 and see if we can use the key backup structure for 1619.2. Provide text that goes to section 6 4 clause.
Proposed text against P1619.2/D3. This replaces paragraph 4 in clause 6:
6.1 Exporting and archiving cryptographic keys
A P1619.2-compliant implementation may support a key backup structure as defined in this subclause. If supported, the key backup structure shall follow the requirements in IEEE Std 1619-2007, Clause 7 "Exporting and archiving XTS-AES-128 and XTS-AES-256 keys" with the following modifications:
- The StandardNumber element (see 7.1.2 in IEEE std 1619-2007) shall be "IEEE STD 1619.2-####" {Editor's Note: Replace the #### with the actual year of publication of the standard}
- The EAD in this standard corresponds to the "Tweak" in IEEE Std 1619-2007.
David
- The TransformName element (see 7.1.5 in IEEE Std 1619-2007) shall be one of the following strings:
- "XCB-AES-128" - The XCB-AES transform (see 5.3) with a 128-bit AES key
- "XCB-AES-256" - The XCB-AES transform (see 5.3) with a 256-bit AES key
- "EME2-AES-128" - The XCB-AES transform (see 5.2) with a 48-byte EME2-AES key
- "EME2-AES-256" - The XCB-AES transform (see 5.2) with a 64-byte EME2-AES key
- The KeyLength element (see 7.1.6 in IEEE Std 1619-2007) shall be one of the following integers, according to the TransformName element:
- "XCB-AES-128" - KeyLength shall be 128
- "XCB-AES-256" - KeyLength shall be 256
- "EME2-AES-128" - KeyLength shall be 384
- "EME2-AES-256" - KeyLength shall be 512
--
Thanks!
Matt Ball, IEEE P1619.x SISWG Chair
M.V. Ball Technical Consulting, Inc.
Phone: 303-469-2469, Cell: 303-717-2717
http://www.mvballtech.com
http://www.linkedin.com/in/matthewvball