110 likes | 251 Views
Public Key Infrastructure Using X.509 (PKIX) Working Group. March 9, 2005 1300-1500. PKIX WG (pkix-wg). Web page: charter, current documents http://www.ietf.org/html.charters/pkix-charter.html Mailing List: ietf-pkix@imc.org To Subscribe: ietf-pkix-request@ imc.org, In Body: subscribe
E N D
Public Key Infrastructure Using X.509 (PKIX) Working Group March 9, 2005 1300-1500
PKIX WG (pkix-wg) • Web page: charter, current documents • http://www.ietf.org/html.charters/pkix-charter.html • Mailing List:ietf-pkix@imc.org • To Subscribe: ietf-pkix-request@ imc.org, In Body: subscribe • Archive: http://www.imc.org/ietf-pkix • Chairs • Stephen Kent kent@bbn.com • Tim Polk tim.polk@nist.gov • Security Area Directors • Russ Housley housley@vigilsec.com • Sam Hartman hartmans@mit.edu
PKIX Agenda for 62nd IETF • Document Status Overview • WG presentations • SCVP • RFC3280bis • Japan Challenge UTF8 Survey • CRL Signer certificate discovery using AIA • CMC drafts • Liasion Presentation • LDAP document suite • OCSP interchange format
Status Review • 5 documents in RFC Editors Queue • One document blocked on normative reference • 1 approved by IESG • 3 Documents with ADs • 12 documents active in WG • 11 currently online, plus SIM
In RFC Editors Queue • PKALgs • CertPath Building • Permanent Identifier • Warranty Extension • 2510bis (CMPbis) • Blocked on 2511bis
One document Approved by IESG • 2511bis (CRMF)
Three Documents With ADs • AC Policies • PKIX Repository • CertStore HTTP
SCVP • In WG Last Call • New Drafts 17 and 18 submitted since Washington • Editors believe that • draft 18 is fully consistent with RFC 3379 • next draft (19) will complete resolution of WG Last Call comments • After submitting -19, editors will request that Steve consider whether rough consensus has been achieved
Subject Identification Method • Last draft posted in July • Resolved most of the comments posted to list • One more draft needed to resolve 4 open issues • Proposed Timeline • New draft April 2005 • WG Last Call April 2005
LDAP document suite • Component matching is the end goal, but a standard and simple fallback mechanism is required • Attribute extraction techniques can be implemented using any LDAP server, but the current drafts are too complex • Need to reduce the complexity so that this is an effective fallback.
RFC 3280bis • -00 draft submitted • Still not posted • Diff file online • Disposition of comments will be posted after this meeting.