Archive of ietf-pkix/old-archive-99, by thread

• Re: New proposed solution to the QC biometric issue, (continued)
  • Re: New proposed solution to the QC biometric issue, Peter Williams
  • Re: New proposed solution to the QC biometric issue, Peter Williams
    • Re: New proposed solution to the QC biometric issue, Stephen Kent
  • Re: New proposed solution to the QC biometric issue, Peter Williams
  • Re: New proposed solution to the QC biometric issue, Stefan Santesson
    • Re: New proposed solution to the QC biometric issue, Denis Pinkas
      • Re: New proposed solution to the QC biometric issue, Ben Laurie
• Double quotes in DNs, Martin Lindström
  • Re: Double quotes in DNs, Mark Wahl
• RE: New CMC Draft available - Confirmation Message, Jim Schaad (Exchange)
  • Re: New CMC Draft available - Confirmation Message, Juergen Walter
  • <Possible follow-ups>
  • RE: New CMC Draft available - Confirmation Message, Carlisle Adams
  • RE: New CMC Draft available - Confirmation Message, Bob Jueneman
  • RE: New CMC Draft available - Confirmation Message, Jim Schaad (Exchange)
  • RE: New CMC Draft available - Confirmation Message, Bob Jueneman
• cross-certify?, gang cao
• Changes to RFC 2459, Alfred Arsenault
• Diffie-Hellman DomainParameters, Tolga Acar
• PKIX CMP: Transaction Identifier in use, Amit Kapoor
• Possible ambiguities in encoding of signatures, encrypted keys, Peter Gutmann
  • <Possible follow-ups>
  • RE: Possible ambiguities in encoding of signatures, encrypted keys, William Whyte
  • Re: Possible ambiguities in encoding of signatures, encrypted keys, Peter Gutmann
• About Diffie-Hellman algorithm and Shamir threshold, Xiong Shao Jun
  • Re: About Diffie-Hellman algorithm and Shamir threshold, Russ Housley
  • <Possible follow-ups>
  • RE: About Diffie-Hellman algorithm and Shamir threshold, Carlisle Adams
    • Re: About Diffie-Hellman algorithm and Shamir threshold, Xiong Shao Jun
• optional fields in time stamp responses., Peter Sylvester
• CyberPhone Trust Propagation Was: A $25,000,000,000 PKI, Anders Rundgren
  • Re: CyberPhone Trust Propagation Was: A $25,000,000,000 PKI, Stephen Kent
  • <Possible follow-ups>
  • Re: CyberPhone Trust Propagation Was: A $25,000,000,000 PKI, Anders Rundgren
  • RE: CyberPhone Trust Propagation Was: A $25,000,000,000 PKI, Alan Lloyd
• Time-Stamp: Why not use several hashes?, Manuel Heras Gilsanz
  • Re: Time-Stamp: Why not use several hashes?, Denis Pinkas
    • Re: Time-Stamp: Why not use several hashes?, Manuel Heras Gilsanz
    • Re: Time-Stamp: Why not use several hashes?, Jose A. Manas
  • <Possible follow-ups>
  • RE: Time-Stamp: Why not use several hashes?, Robert Zuccherato
    • Re: Time-Stamp: Why not use several hashes?, Manuel Heras Gilsanz
  • RE: Time-Stamp: Why not use several hashes?, Robert Zuccherato
    • Re: Time-Stamp: Why not use several hashes?, Denis Pinkas
    • Re: Time-Stamp: Why not use several hashes?, Manuel Heras Gilsanz
  • RE: Time-Stamp: Why not use several hashes?, Robert Zuccherato
  • Re: Time-Stamp: Why not use several hashes?, Peter Sylvester
• Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat &Q C-heavy-bio, Anders Rundgren
• RE: SEIS: RE: A $25,000,000,000 PKI Was:Spec. on QC-low-fat &QC-heavy-bio, Simon Corell
• RE: A $25,000,000,000 PKI Was:Spec. on QC-low-fat &QC-heavy-bio, Anders Rundgren
• CMP message format. A naive question, Michael Zolotarev
  • <Possible follow-ups>
  • RE: CMP message format. A naive question, Carlisle Adams
• SEIS: RE: Certificates, Directories, and Distinguished Names, Bob Jueneman
  • <Possible follow-ups>
  • RE: SEIS: RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
  • RE: SEIS: RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
    • RE: SEIS: RE: Certificates, Directories, and Distinguished Names, Stephen Kent
  • RE: SEIS: RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
    • RE: SEIS: RE: Certificates, Directories, and Distinguished Names, Stephen Kent
• Time Stamping: comments on nonce field, Juan G. de la Vega
  • <Possible follow-ups>
  • RE: Time Stamping: comments on nonce field, Robert Zuccherato
    • Re: Time Stamping: comments on nonce field, Denis Pinkas
  • RE: Time Stamping: comments on nonce field, Robert Zuccherato
  • RE: Time Stamping: comments on nonce field, Juan G. de la Vega
  • RE: Time Stamping: comments on nonce field, Juan G. de la Vega
  • RE: Time Stamping: comments on nonce field, Juan G. de la Vega
• Time Stamp: tsa field in TSTInfo, Juan Luis López
  • <Possible follow-ups>
  • RE: Time Stamp: tsa field in TSTInfo, Robert Zuccherato
  • RE: Time Stamp: tsa field in TSTInfo, Peter Sylvester
    • Re: Time Stamp: tsa field in TSTInfo, Denis Pinkas
  • RE: Time Stamp: tsa field in TSTInfo, Michael Zolotarev
  • RE: Time Stamp: tsa field in TSTInfo, Juan Luis López
  • RE: Time Stamp: tsa field in TSTInfo, Peter Sylvester
  • RE: Time Stamp: tsa field in TSTInfo, Robert Zuccherato
    • Re: Time Stamp: tsa field in TSTInfo, Denis Pinkas
  • Re: Time Stamp: tsa field in TSTInfo, Peter Sylvester
  • RE: Time Stamp: tsa field in TSTInfo, Juan Luis López
• RE: A $25,000,000,000 PKI, Michael Zolotarev
• Re: SEIS: Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stefan Santesson
  • Re: SEIS: Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Dan Geer
• A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
  • <Possible follow-ups>
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
    • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
      • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Paul Krumviede
  • RE: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Andrew Probert
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
    • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
  • RE: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Alan Lloyd
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stefan Santesson
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
    • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
    • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stefan Santesson
    • Re: SEIS: Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Patrik Fältström
      • Trust, was Re: SEIS: Re: A $25,000,000,000 PKI, Ed Gerck
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Aram Perez
  • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
    • Re: A $25,000,000,000 PKI Was:Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
• CA vs. EE cert processing, Stephen Kent
  • Re: CA vs. EE cert processing, Paul Hoffman / IMC
  • <Possible follow-ups>
  • RE: CA vs. EE cert processing, Alan Lloyd
    • RE: CA vs. EE cert processing, Stephen Kent
  • Re: CA vs. EE cert processing, John_Wray
    • Re: CA vs. EE cert processing, Stephen Kent
      • Re: CA vs. EE cert processing, Moshe Litvin
      • Re: CA vs. EE cert processing, Stephen Kent
      • Re: CA vs. EE cert processing, Moshe Litvin
      • Re: CA vs. EE cert processing, Stephen Kent
      • Re: CA vs. EE cert processing, Moshe Litvin
  • Re: CA vs. EE cert processing, David P. Kemp
  • Re: CA vs. EE cert processing, Aram Perez
    • Re: CA vs. EE cert processing, Stephen Kent
      • Re: CA vs. EE cert processing, Moshe Litvin
      • Message not available
      • Re: CA vs. EE cert processing, Moshe Litvin
      • Re: CA vs. EE cert processing, Stephen Kent
  • RE: CA vs. EE cert processing, Alan Lloyd
    • RE: CA vs. EE cert processing, Stephen Kent
  • RE: CA vs. EE cert processing, Alan Lloyd
    • RE: CA vs. EE cert processing, Stephen Kent
  • Re: CA vs. EE cert processing, John_Wray
    • Re: CA vs. EE cert processing, Stephen Kent
  • Re: CA vs. EE cert processing, David P. Kemp
    • Re: CA vs. EE cert processing, Moshe Litvin
  • RE: CA vs. EE cert processing, Alan Lloyd
    • RE: CA vs. EE cert processing, Stephen Kent
      • RE: CA vs. EE cert processing, Russ Housley
      • Re: CA vs. EE cert processing, Moshe Litvin
      • Re: CA vs. EE cert processing, Russ Housley
      • Re: CA vs. EE cert processing, Moshe Litvin
  • RE: CA vs. EE cert processing, Alan Lloyd
  • RE: CA vs. EE cert processing, Alan Lloyd
• Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
  • Re: SEIS: Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
  • <Possible follow-ups>
  • RE: Spec. on QC-low-fat & QC-heavy-bio, Anders Rundgren
    • Re: SEIS: RE: Spec. on QC-low-fat & QC-heavy-bio, Stephen Kent
• EESSI - European Electronic Signature Standardization Initiative, Stefan Santesson
• toner sales advertising, remailer
• policy oid registration, and handling, Peter Williams
  • Re: policy oid registration, and handling, Michael Sierchio
• minutes and revised charter, Stephen Kent
• R: 3 Time Stamping issues, Santoni Adriano
  • <Possible follow-ups>
  • Re: R: 3 Time Stamping issues, Peter Sylvester
• New Timestamping Tokens, Todd S. Glassey
• 3 Time Stamping issues, Denis Pinkas
  • Re: 3 Time Stamping issues, Paul Koning
  • <Possible follow-ups>
  • Re: 3 Time Stamping issues, Todd S. Glassey
  • Re: 3 Time Stamping issues, Peter Sylvester
  • RE: 3 Time Stamping issues, Robert Zuccherato
  • Re: 3 Time Stamping issues, Todd S. Glassey
• Does it exist: CA certificate DP ?, Marc Jadoul
• Low-fat leaf certificates, Anders Rundgren
  • Re: Low-fat leaf certificates, Denis Pinkas
  • <Possible follow-ups>
  • Re: Low-fat leaf certificates, Peter Sylvester
  • Re: Low-fat leaf certificates, Bob Jueneman
  • RE: Low-fat leaf certificates, Anders Rundgren
• question, jhoh
  • Re: question, Sung-Hee Park
• Delurking on Biometrics, Zmudzinski, Tom
  • <Possible follow-ups>
  • Re: Delurking on Biometrics, Bob Jueneman
• Time-stamp server. Extra field for MessageImpring, Michael Zolotarev
  • <Possible follow-ups>
  • Re: Time-stamp server. Extra field for MessageImpring, Peter Sylvester
  • RE: Time-stamp server. Extra field for MessageImpring, Michael Zolotarev
  • RE: Time-stamp server. Extra field for MessageImpring, Robert Zuccherato
  • Re: Time-stamp server. Extra field for MessageImpring, Todd S. Glassey
• Time-stamp server. TimePrecision info, Michael Zolotarev
  • Re: Time-stamp server. TimePrecision info, Michael Sierchio
  • <Possible follow-ups>
  • RE: Time-stamp server. TimePrecision info, Michael Zolotarev
  • RE: Time-stamp server. TimePrecision info, Robert Zuccherato
    • RE: Time-stamp server. TimePrecision info, Paul Koning
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
    • Re: Time-stamp server. TimePrecision info, Paul Koning
    • Re: Time-stamp server. TimePrecision info, Tony Bartoletti
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
  • Re: Time-stamp server. TimePrecision info, Peter Sylvester
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
  • RE: Time-stamp server. TimePrecision info, Michael Zolotarev
    • RE: Time-stamp server. TimePrecision info, Paul Koning
    • Re: Time-stamp server. TimePrecision info, Michael McNeil
      • Re: Time-stamp server. TimePrecision info, Paul Koning
      • Re: Time-stamp server. TimePrecision info, Michael McNeil
  • RE: Time-stamp server. TimePrecision info, PHalliden
    • RE: Time-stamp server. TimePrecision info, Paul Koning
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
  • RE: Time-stamp server. TimePrecision info, Robert Zuccherato
  • RE: Time-stamp server. TimePrecision info, Paul Halliden
    • RE: Time-stamp server. TimePrecision info, Paul Koning
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
  • Re: Time-stamp server. TimePrecision info, Robert Klerer
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
    • Re: Time-stamp server. TimePrecision info, Denis Pinkas
      • Re: Time-stamp server. TimePrecision info, Paul Koning
      • Re: Time-stamp server. TimePrecision info, Stephen Kent
      • Re: Time-stamp server. TimePrecision info, Paul Koning
      • Re: Time-stamp server. TimePrecision info, Stephen Kent
      • Re: Time-stamp server. TimePrecision info, Paul Koning
      • Re: Time-stamp server. TimePrecision info, Michael McNeil
      • Re: Time-stamp server. TimePrecision info, Paul Koning
      • Re: Time-stamp server. TimePrecision info, Stephen Kent
      • Re: Time-stamp server. TimePrecision info, Stephen Kent
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
    • Re: Time-stamp server. TimePrecision info, Stephen Kent
    • Re: Time-stamp server. TimePrecision info, Dan Geer
      • Re: Time-stamp server. TimePrecision info, Tony Bartoletti
  • RE: Time-stamp server. TimePrecision info, Robert Zuccherato
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
    • Re: Time-stamp server. TimePrecision info, Stephen Kent
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
    • Re: Time-stamp server. TimePrecision info, Stephen Kent
  • Re: Time-stamp server. TimePrecision info, Todd S. Glassey
  • Re: Time-stamp server. TimePrecision info, Paul Koning
  • RE: Time-stamp server. TimePrecision info, Michael Zolotarev
  • RE: Time-stamp server. TimePrecision info, Meggison, Tim
    • RE: Time-stamp server. TimePrecision info, Bill Lattin
  • RE: Time-stamp server. TimePrecision info, Sweigert, David
• Conclusion - Biometric inclusion in QC, Stefan Santesson
  • Re: Conclusion - Biometric inclusion in QC, Denis Pinkas
  • <Possible follow-ups>
  • Re: Conclusion - Biometric inclusion in QC, Stefan Santesson
    • Re: Conclusion - Biometric inclusion in QC, Denis Pinkas
  • Re: Conclusion - Biometric inclusion in QC, Stefan Santesson
  • Re: Conclusion - Biometric inclusion in QC, Lynn.Wheeler
• [no subject], Scott Kern
• PKIX notice files, and markup, Peter Williams
  • Re: PKIX notice files, and markup, Russ Housley
  • <Possible follow-ups>
  • Re: PKIX notice files, and markup, Peter Sylvester
  • Re: PKIX notice files, and markup, Peter Williams
• IS&N'99 Barcelona approaching (27th-29th April), Jaime Delgado
• Re: 2 Where is the Silver Bullet?, Tony Bartoletti
• Re: QC Certificates, Directories, and Distinguished Names, Stefan Santesson
• Trivia, Bob Jueneman
• "Alternatively-encoded" extensions, Peter Williams
  • Object IDs for PKIBody types?, Timothy Fisher
  • Re: "Alternatively-encoded" extensions, Timothy Fisher
  • Re: "Alternatively-encoded" extensions, Stephen Kent
  • <Possible follow-ups>
  • Re: "Alternatively-encoded" extensions, David P. Kemp
  • RE: "Alternatively-encoded" extensions, BalluffiF
  • RE: "Alternatively-encoded" extensions, BalluffiF
• I-D ACTION:draft-ietf-pkix-cmc-03.txt, Internet-Drafts
• I-D ACTION:draft-ietf-pkix-roadmap-01.txt, Internet-Drafts
• Changes to RFC2459, Jim Schaad (Exchange)
  • Re: Changes to RFC2459, Brian Korver
  • Re: Changes to RFC2459, Stephen Kent
    • Re: Changes to RFC2459, Moshe Litvin
      • Re: Changes to RFC2459, Stephen Kent
      • Re: Changes to RFC2459, Moshe Litvin
  • <Possible follow-ups>
  • Re: Changes to RFC2459, David P. Kemp
  • RE: Changes to RFC2459, Alex Deacon
    • RE: Changes to RFC2459, Stephen Kent
  • Re: Changes to RFC2459, Peter Gutmann
  • Re: Changes to RFC2459, klobucar
    • Re: Changes to RFC2459, Tim Polk
  • RE: Changes to RFC2459, Jim Schaad (Exchange)
    • RE: Changes to RFC2459, Stephen Kent
      • Re: Changes to RFC2459, Moshe Litvin
      • Re: Changes to RFC2459, Stephen Kent
      • Re: Changes to RFC2459, Moshe Litvin
  • Re: Changes to RFC2459, Peter Williams
    • Re: Changes to RFC2459, Roger Younglove
  • Re: Changes to RFC2459, Peter Gutmann
    • Re: Changes to RFC2459, Michael Sierchio
    • Re: Changes to RFC2459, Moshe Litvin
    • Re: Changes to RFC2459, Stephen Kent
  • Re: Changes to RFC2459, Terry Hayes
    • Re: Changes to RFC2459, Stephen Kent
      • Re: Changes to RFC2459, Terry Hayes
      • Re: Changes to RFC2459, Stephen Kent
  • Re: Changes to RFC2459, Peter Gutmann
    • Re: Changes to RFC2459, Stephen Kent
  • Re: Changes to RFC2459, Peter Gutmann
  • RE: Changes to RFC2459, Meggison, Tim
• Correct use of subject DN and subjectAltName, Mark Shuttleworth
  • Re: Correct use of subject DN and subjectAltName, Stephen Kent
  • <Possible follow-ups>
  • Re: Correct use of subject DN and subjectAltName, Stefan Santesson
  • Re: Correct use of subject DN and subjectAltName, Bob Jueneman
  • Re: Correct use of subject DN and subjectAltName, Bob Jueneman
• Re: SEIS: Certificates, Directories, and Distinguished Names, Stefan Santesson
  • <Possible follow-ups>
  • Re: SEIS: Certificates, Directories, and Distinguished Names, Bob Jueneman
• Biometrics in Qualified Certificates, Stefan Santesson
  • Re: Biometrics in Qualified Certificates, Michael Sierchio
  • Re: Biometrics in Qualified Certificates, Stephen Kent
  • <Possible follow-ups>
  • RE: Biometrics in Qualified Certificates, Anders Rundgren
  • RE: Biometrics in Qualified Certificates, Stefan Santesson
    • RE: Biometrics in Qualified Certificates, Stephen Kent
  • Re: Biometrics in Qualified Certificates, Mike Smith
  • RE: Biometrics in Qualified Certificates, Anders Rundgren
  • Re: Biometrics in Qualified Certificates, Stefan Santesson
    • Re: Biometrics in Qualified Certificates, Stephen Kent
  • RE: Biometrics in Qualified Certificates, Stefan Santesson
  • Re: Biometrics in Qualified Certificates, Peter Williams
    • Re: Biometrics in Qualified Certificates, Stephen Kent
  • Re: Biometrics in Qualified Certificates, Stefan Santesson
• QC Biometric Support. Was: Location and Identification, Anders Rundgren
  • <Possible follow-ups>
  • RE: QC Biometric Support. Was: Location and Identification, Andrew Probert
  • RE: QC Biometric Support. Was: Location and Identification, Alan Lloyd
  • RE: QC Biometric Support. Was: Location and Identification, Anders Rundgren
• Pictures in QCs - No problems!, Anders Rundgren
  • <Possible follow-ups>
  • Re: Pictures in QCs - No problems!, Peter Gutmann
  • Re: Pictures in QCs - No problems!, David P. Kemp
    • Re: SEIS: Re: Pictures in QCs - No problems!, Ed Gerck
  • RE: Pictures in QCs - No problems!, Anders Rundgren
    • Re: Pictures in QCs - No problems!, Dale Gustafson
• Certificates, Directories, and Distinguished Names, Bob Jueneman
  • <Possible follow-ups>
  • RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
  • Re: Certificates, Directories, and Distinguished Names, Stephen Kent
  • RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
    • RE: Certificates, Directories, and Distinguished Names, Stephen Kent
  • RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
    • RE: Certificates, Directories, and Distinguished Names, Stephen Kent
  • RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
    • RE: Certificates, Directories, and Distinguished Names, Stephen Kent
  • RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
    • RE: Certificates, Directories, and Distinguished Names, Tony Bartoletti
    • RE: Certificates, Directories, and Distinguished Names, Stephen Kent
  • RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
    • RE: Certificates, Directories, and Distinguished Names, Tony Bartoletti
    • RE: Certificates, Directories, and Distinguished Names, Stephen Kent
  • RE: Certificates, Directories, and Distinguished Names, Alan Lloyd
• Updated Project List for Minutes, Warwick Ford
• Cross certification message protection (RFC2510), Michael_Shanzer
  • Re: Cross certification message protection (RFC2510), Juergen Walter
  • <Possible follow-ups>
  • Re: Cross certification message protection (RFC2510), Michael_Shanzer
  • RE: Cross certification message protection (RFC2510), Carlisle Adams
• Location and Identification, Bob Jueneman
  • <Possible follow-ups>
  • Re: Location and Identification, Bob Jueneman
    • Re: Location and Identification, Tony Bartoletti
    • Re: Location and Identification, Stephen Kent
  • RE: Location and Identification, Andrew Probert
    • RE: Location and Identification, Tony Bartoletti
  • Re: Location and Identification, Stefan Santesson
    • Re: Location and Identification, Paul Koning
    • Re: Location and Identification, Tony Bartoletti
  • Re: Location and Identification, tgindin
    • Re: Location and Identification, Stephen Kent
  • Re: Location and Identification, Tolga Acar
  • Re: Location and Identification, Bob Jueneman
  • Re: Location and Identification, Bob Jueneman
    • Re: Location and Identification, Jan Nielsen
  • Re: Location and Identification, Stefan Santesson
  • Re: Location and Identification, Stefan Santesson
  • Re: Location and Identification, Stephen Kent
• Can the responder change values in a cross cert request?, Mary_Ellen_Zurko
• PKIPublicationInfo controls in CMP, John_Wray
• question about system time checking in CMP, Mary_Ellen_Zurko
• QC - there ARE biometric standards, Anders Rundgren
• Question: Using Certificate Extensions for Applications, Keith Johnston
  • Question: Getting an OID for a certificate extension, Keith Johnston
  • Re: Question: Using Certificate Extensions for Applications, Stephen Kent
    • Re: Question: Using Certificate Extensions for Applications, Keith Johnston
      • Re: Question: Using Certificate Extensions for Applications, Tony Bartoletti
      • Re: Question: Using Certificate Extensions for Applications, Juergen Walter
      • Re: Question: Using Certificate Extensions for Applications, Tony Bartoletti
      • Re: Question: Using Certificate Extensions for Applications, Stephen Kent
      • Re: Question: Using Certificate Extensions for Applications, Juergen Walter
      • Re: Question: Using Certificate Extensions for Applications, Keith Johnston
      • Re: Question: Using Certificate Extensions for Applications, Stephen Kent
  • <Possible follow-ups>
  • Re: Question: Using Certificate Extensions for Applications, Mary_Ellen_Zurko
• revised charter, Stephen Kent
  • <Possible follow-ups>
  • Re: revised charter, Francois Rousseau
• meeting minutes, 1st draft, Stephen Kent
• LDAP, mderuyte
• CertificateStatus in PKIX-LDAP Schema?, Vesna Hassler
• Re: SEIS: Re: Regarding "Given names", Petra Glöckner
• CRL version field confusion, Martin Lindström
  • Re: CRL version field confusion, Stephen Kent
    • Re: CRL version field confusion, David Chadwick
  • RE: CRL version field confusion, Ambarish Malpani
    • Re: CRL version field confusion, Srinivas Pandrangi
      • Re: CRL version field confusion, Russ Housley
  • <Possible follow-ups>
  • Re: CRL version field confusion, Hoyt.Kesterson
    • Re: CRL version field confusion, Stephen Kent
  • Re: CRL version field confusion, Martin Lindström
    • Re: CRL version field confusion, Stephen Kent
  • Re: CRL version field confusion, tgindin
• CFP: ISOC Year 2000 Network & Distr. System Security (NDSS 2000), David M. Balenson
• Re: SEIS: Regarding "Given names", Bob Jueneman
  • <Possible follow-ups>
  • Re: SEIS: Regarding "Given names", Bob Jueneman
    • Re: SEIS: Regarding "Given names", Stephen Kent
    • Re: SEIS: Regarding "Given names", Juergen Walter
• Signature request ?, Sergio Tabanelli
  • Re: Signature request ?, Stephen Kent
• QC Sample Sucks (a bit), Anders Rundgren
  • Re: QC Sample Sucks (a bit), Stephen Kent
    • Re: QC Sample Sucks (a bit), Michael Roe
      • Re: QC Sample Sucks (a bit), Stephen Kent
  • Re: QC Sample Sucks (a bit), Petra Glöckner
    • Re: QC Sample Sucks (a bit), Juergen Walter
  • <Possible follow-ups>
  • RE: QC Sample Sucks (a bit), Anders Rundgren
    • RE: QC Sample Sucks (a bit), Stephen Kent
    • Re: QC Sample Sucks (a bit), Michael Sierchio
  • Re: QC Sample Sucks (a bit), Anders Rundgren
  • Re: QC Sample Sucks (a bit), Stefan Santesson
  • RE: QC Sample Sucks (a bit), Anders Rundgren
  • RE: QC Sample Sucks (a bit), Anders Rundgren
    • RE: QC Sample Sucks (a bit), Stephen Kent
  • Re: QC Sample Sucks (a bit), Anders Rundgren
    • Re: QC Sample Sucks (a bit), Stephen Kent
  • RE: QC Sample Sucks (a bit), Anders Rundgren
• Communications and Multimedia Security '99, CMS'99
• Information site for Qualified certificates progress, Stefan Santesson
• rfc2527 implementations, Janus Liebregts
• Equivalent policies in path validation procedure, klobucar
• Regarding "Given names", Bob Jueneman
  • <Possible follow-ups>
  • Re: Regarding "Given names", Zahid Ahmed
    • Re: Regarding "Given names", Stephen Kent
  • Re: Regarding "Given names", Anders Rundgren
• High-level Technical Workshop on Smart Cards, Linda Barnett
• X.509 Attribute Certificates extensions in PKIX Certificates?, Zahid Ahmed
  • <Possible follow-ups>
  • RE: X.509 Attribute Certificates extensions in PKIX Certificates?, Michael Crerar
    • RE: X.509 Attribute Certificates extensions in PKIX Certificates?, Francois Rousseau
  • RE: X.509 Attribute Certificates extensions in PKIX Certificates?, Anders Rundgren
• Questions on Root CA key Update in rfc2510 (CMP), Sergio Tabanelli
  • Re: Questions on Root CA key Update in rfc2510 (CMP), Juergen Walter
• Workshop on Countering Cyber-Terrorism, Clifford Neuman
• relational searching over distributed directories, Alan Lloyd
• Netx ABA ISC meeting announcement, Todd S. Glassey
• New CMC Draft available, Jim Schaad (Exchange)
  • <Possible follow-ups>
  • RE: New CMC Draft available, Carlisle Adams
    • Re: New CMC Draft available, Juergen Walter
  • RE: New CMC Draft available, Jim Schaad (Exchange)
    • Re: New CMC Draft available - Confirmation Message, Juergen Walter
  • RE: New CMC Draft available, Carlisle Adams
• Protocol Action: X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP to Proposed Standard, The IESG
• Protocol Action: Internet X.509 Public Key Infrastructure LDAPv2 Schema to Proposed Standard, The IESG
• Protocol Action: Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP to Proposed Standard, The IESG
• Call for Papers: CQRE, Detlef Hühnlein
• Re: PKIX Path determination/construction/processingandAKIpointer hanging, Bob Jueneman
  • <Possible follow-ups>
  • Re: PKIX Path determination/construction/processingandAKIpointer hanging, Bob Jueneman
• Please reply, Michael Sierchio
• Certificate mapping (was: Re: Qualified Certificates draft -Country name), Bob Jueneman
• Re: PKIX Path determination/construction/processing andAKIpointer hanging, Bob Jueneman
  • <Possible follow-ups>
  • Re: PKIX Path determination/construction/processing andAKIpointer hanging, Peter Williams
  • Re: PKIX Path determination/construction/processing andAKIpointer hanging, David P. Kemp
• RE: A web of directories - Finding PKIX Servers, Alan Lloyd
  • Re: A web of directories - Finding PKIX Servers, Andreas Berger
  • <Possible follow-ups>
  • Re: A web of directories - Finding PKIX Servers, Bob Jueneman
• RE: OCSP Service Locator and RFC2459's Authority InformationAccess, Bob Jueneman
  • <Possible follow-ups>
  • RE: OCSP Service Locator and RFC2459's Authority InformationAccess, Bob Jueneman
  • RE: OCSP Service Locator and RFC2459's Authority InformationAccess, Bob Jueneman
• Fw: 1999 WET-ICE Enterprise Security Workshop, Yahya Al-Salqan
• Cert binding to ?, Martin Smith
  • Re: Cert binding to ?, Tony Bartoletti
  • Re: Cert binding to ?, Stephen Kent
    • Re: Cert binding to ?, Martin Smith
  • <Possible follow-ups>
  • RE: Cert binding to ?, Andrew Probert
  • RE: Cert binding to ?, Alan Lloyd
    • Re: Cert binding to ?, Martin Smith
  • RE: Cert binding to ?, WHenry
  • RE: Cert binding to ?, Alan Lloyd
• I-D ACTION:draft-ietf-pkix-dhpop-00.txt, Internet-Drafts
• Mapping certificate to directories, Bob Jueneman
  • <Possible follow-ups>
  • RE: Mapping certificate to directories, Andrew Probert
  • RE: Mapping certificate to directories, Bob Jueneman
• Re: PKIX Path determination/construction/processing and AKIpointer hanging, Mike Smith
  • <Possible follow-ups>
  • Re: PKIX Path determination/construction/processing and AKIpointer hanging, Peter Williams
  • Re: PKIX Path determination/construction/processing and AKIpointer hanging, David P. Kemp
  • Re: PKIX Path determination/construction/processing and AKIpointer hanging, Peter Williams
  • Re: PKIX Path determination/construction/processing and AKIpointer hanging, David P. Kemp
  • Re: PKIX Path determination/construction/processing and AKIpointer hanging, Peter Williams
    • Re: PKIX Path determination/construction/processing and AKIpointer hanging, Brian Korver
  • RE: PKIX Path determination/construction/processing and AKIpointer hanging, Alan Lloyd
  • Re: PKIX Path determination/construction/processing and AKIpointer hanging, David P. Kemp
  • Re: PKIX Path determination/construction/processing and AKIpointer hanging, Peter Williams
• Call For Papers: CQRE [Secure], Detlef Hühnlein
• PKIX Path determination/construction/processing and AKI pointer hanging, Peter Williams
• OCSP Service Locator and RFC2459's Authority Information Access, Rich Salz
  • <Possible follow-ups>
  • Re: OCSP Service Locator and RFC2459's Authority Information Access, Peter Williams
  • RE: OCSP Service Locator and RFC2459's Authority Information Access, salzr
  • RE: OCSP Service Locator and RFC2459's Authority Information Access, Michael Myers
    • RE: OCSP Service Locator and RFC2459's Authority Information Acce ss, salzr
  • RE: OCSP Service Locator and RFC2459's Authority Information Access, Michael Myers
  • RE: OCSP Service Locator and RFC2459's Authority Information Access, Michael Myers
  • RE: OCSP Service Locator and RFC2459's Authority Information Access, Peter Sylvester
  • RE: OCSP Service Locator and RFC2459's Authority Information Access, Michael Myers
• NIST Reference Implementation available, Tim Polk
• Bug in RFC 2459, Peter Gutmann
  • Re: Bug in RFC 2459, Stephen Kent
  • <Possible follow-ups>
  • RE: Bug in RFC 2459, Alex Deacon
  • Re: Bug in RFC 2459, David P. Kemp
  • Re: Bug in RFC 2459, Peter Gutmann
• A web of directories, Bob Jueneman
  • Re: A web of directories, Stephen Kent
  • Re: A web of directories - Finding PKIX Servers, Andreas Berger
    • Re: A web of directories - Finding PKIX Servers, Marc Jadoul
  • <Possible follow-ups>
  • RE: A web of directories, Kurn, David
  • Re: A web of directories, Mike Smith
  • RE: A web of directories, Kurn, David
  • Re: RE: A web of directories, Mike Smith
  • Re: A web of directories, tgindin
  • RE: A web of directories, Andrew Probert
  • RE: A web of directories, tgindin
  • RE: A web of directories, Bob Jueneman
  • Re: A web of directories, Bob Jueneman
  • Re: RE: A web of directories, Bob Jueneman
  • Re: A web of directories, Bob Jueneman
    • Re: A web of directories, Rich Salz
  • Re: A web of directories, Bob Jueneman
  • RE: A web of directories, salzr
  • RE: A web of directories, Kurn, David
  • Re: A web of directories, Bob Jueneman
    • Re: A web of directories, Francois Rousseau
  • RE: A web of directories, Larry Layten
    • RE: A web of directories, Stephen Kent
      • Re: A web of directories, Mark Wahl

The web site for this mailing list is sponsored by the Internet Mail Consortium. If you have any suggestions for additions or corrections to this Web page, please send them to phoffman@imc.org.