140 likes | 318 Views
IEEE P1363.2 Consolidation of Schemes. November 20, 2003 Teleconference. P1363.2 consolidation. History Summary of latest draft Other standards alignment Suggestions & recommendations mailing list & meeting discussions Resolution. History -- last 12 months. Dec 2002
E N D
IEEE P1363.2Consolidation of Schemes November 20, 2003 Teleconference
P1363.2 consolidation • History • Summary of latest draft • Other standards alignment • Suggestions & recommendations • mailing list & meeting discussions • Resolution IEEE P1363.2 Consolidation
History -- last 12 months • Dec 2002 • first drafts of scheme comparison table • Jan-Mar 2003 • discussed possible fixes for AMP • discussed finalizing method definition • new ISO/IEC draft • Jun 2003 • update for AMP • Aug-Nov 2003 • Draft D11 • meeting and mailing list discussion IEEE P1363.2 Consolidation
Summary of Draft D11 • BPKAS • PAK, PPK • SPEKE • APKAS • AMP (w/ proposed fixes) • BSPEKE1, BSPEKE2, WSPEKE • PAKZ • SRP3 (DL only), SRP5, SRP6 • PKRS • PKRS1 IEEE P1363.2 Consolidation
Other standards and drafts • IETF RFC 2945 & dependents • SRP3 • Internet drafts • BSPEKE, SPEKE, WSPEKE • SRP6 • ISO/IEC WD 17440-4 • PKRS1, SPEKE, SRP3 IEEE P1363.2 Consolidation
Suggestions & recommendations • Mailing list discussion • August meeting discussion • Other standards and drafts IEEE P1363.2 Consolidation
Mailing list discussion • Excerpts from • Jablon 01 Aug • MacKenzie 05 Aug • Jablon 05 Aug • MacKenzie 06 Aug • Kwon 07 Aug • Wu 07 Aug • Brown 06 Nov • Issues categorized by family of method • Between families: AMP vs. SRP • Within the family: PAK, SPEKE, AMP, SRP IEEE P1363.2 Consolidation
Discussion of AMP vs. SRP families • Jablon 01 Aug • Remove SRP5 & SRP6 if keeping fixed AMP • MacKenzie 05 Aug • Remove one of SRP5 or AMP • Kwon 07 Aug • Keep AMP and Keep one or two SRPs • AMP: faster client; SRP: faster server • Wu 07 Aug • Keep SRP6 & SRP3 (used in standards & products) • Brown 06 Nov • Keep some forms of SRP3 and SRP6 IEEE P1363.2 Consolidation
Discussion of PAK family • Jablon 01 Aug • Remove PPK (keeping PAK) • MacKenzie 05 Aug • Keep PPK (it uses same primitives, PPK: no key conf. or msg order; PAK: more efficient) IEEE P1363.2 Consolidation
Discussion of SPEKE family • Jablon 01 Aug • Remove BSPEKE1 (keeping BSPEKE2) • MacKenzie 05 Aug • Remove two of {BSPEKE1, BSPEKE2, WSPEKE} • Jablon 05 Aug • Keep WSPEKE {shared primitives, WSPEKE is more efficient; BSPEKE2 older, in products} • MacKenzie 06 Aug • Ok to keep WSPEKE and BSPEKE2 IEEE P1363.2 Consolidation
Discussion of AMP family • Jablon 01 Aug • Keep fixed AMP • MacKenzie 05 Aug • Remove one of SRP5 or AMP • Kwon 07 Aug • Keep AMP • AMP: faster client; SRP: faster server • Keep two AMPs • fixed AMP (LAMP[Kw03]) plus AMP2 (AMP[Kw03]) • discussed in Aug. meeting IEEE P1363.2 Consolidation
Discussion of SRP family • Jablon 01 Aug • Remove SRP6 and SRP6 • MacKenzie 05 Aug • Remove one of SRP3 or SRP6 • Wu 07 Aug • Keep SRP6 & SRP3 (used in standards & products) • Brown 06 Nov • Remove SRP5 (needs msg order), and either • Keep {DL,EC}SRP3/6 • adapting DL +v/+3v to EC *REDP1(v), or • Keep DL-SRP3 and {DL,EC}SRP6 IEEE P1363.2 Consolidation
August meeting discussion • Summary of AMP methods • 3 vs. 4-pass protocols • Precomputation ability presumed IEEE P1363.2 Consolidation
Resolution • Answer remaining questions • Propose motions • Vote IEEE P1363.2 Consolidation