Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[P1363:] Comments on P1363-2004 (Re: [P1363:] 1363 v2 D1-pre uploaded)



Dear William Whyte and IEEE P1363 members,

We have some comments on PSEC-KEM part of P1363-2004 draft.
Attached file
  P1363-v2-D1-pre-(PSEC-KEM-revised_with_modification_history2)r.doc
is our proposal.

Best regards,


> Hi List,
> 
> I've uploaded the pre-first draft of the revision of 1363
> to the website. It can be obtained from:
> http://grouper.ieee.org/groups/1363/P1363-Reaffirm/index.html.
> 
> I would greatly appreciate comments on the content (not the 
> formatting) of the non-highlighted text in the document. In
> particular, I would appreciate being informed of:
> 
> * Any new security considerations since 2004 that should be
>   included.
> 
> * Any concerns about the inclusion of specific techniques.
> 
> Note that the yellow highlighted text in the document should
> be considered preliminary and need not yet be read closely.
> 
> Please send me comments by August 14th for review at our
> August 25th teleconference.
> 
> This revision contains:
> 
> * All the material from Std 1363-2000, with the amendments specified
>   in Std 1363a-2004.
> 
> * Additional techniques:
> 
>   * ESIGN-PSS
>   * PSEC-KEM
>   * RSA-KEM
>   * HMQV
> 
> * Additional security considerations and modifications based
>   on them:
> 
>   * Consideration of the subfield-adjusted MOV condition, based
>     on the work of Laura Hitt.
> 
> * Additional changes:
> 
>   * Fix to the CM algorithm in A.12, as noted by Martin Thiim, Dan 
>     Brown, Mike Scott and Marcel Martin.
> 
> Outstanding ToDos:
> 
> * Fix formatting, especially for bulleted and numbered lists.
> * Recreate diagrams using Visio.
> * Review all security considerations and update with results since 2004.
> * Fix all cross-references to be automatically generated and hyperlinked
> * Fix bibliography to be in IEEE style; fix references to bibliography 
>   to be automatically generated and hyperlinked
> * Fix PAR so title is consistent - Standard for Public Key Cryptography 
>   or Standard Specifications for?
> 
>   Areas highlighted in yellow in the draft need particular attention.
> 
> I am unlikely to make further changes, even editorial, to the draft 
> before August 10th, so this is a stable target for comments.
> 
> Looking forward to moving this on.
> 
> Cheers,
> 
> William
> 
> =========================================
> 
> William Whyte,
> 
> Chair, IEEE P1363 Working Group
> 35 Nagog Park Ste 301, Acton, MA 01720
> 
>   +1 978 844 5208  (us office)
>   +1 978 264 0103  (us fax)
> 
> ______________________________________________________________________
> To unsubscribe, mail LISTSERV@xxxxxxxxxxxxxxxxx with
> the body of the message containing: SIGNOFF STDS-P1363-DISCUSS
> Send any concerns to STDS-P1363-DISCUSS-request@xxxxxxxxxxxxxxxxx,
> or manage subscriptions at http://listserv.ieee.org/cgi-bin/wa
> Visit IEEE P1363 on the web at: http://grouper.ieee.org/groups/1363
> ______________________________________________________________________

-- 
Kobayashi Tetsutaro <kobayashi.tetsutaro@xxxxxxxxxxxxx>
TEL: 0422-59-3462     FAX: 0422-59-4015

______________________________________________________________________
To unsubscribe, mail LISTSERV@xxxxxxxxxxxxxxxxx with
the body of the message containing: SIGNOFF STDS-P1363-DISCUSS
Send any concerns to STDS-P1363-DISCUSS-request@xxxxxxxxxxxxxxxxx,
or manage subscriptions at http://listserv.ieee.org/cgi-bin/wa
Visit IEEE P1363 on the web at: http://grouper.ieee.org/groups/1363
______________________________________________________________________

Attachment: P1363-v2-D1-pre-(PSEC-KEM-revised_with_modification_history2)r.doc
Description: Binary data