Archive of ietf-pkix, by thread

• RE: AKI and SKI problem with RFC 3280?, (continued)
  • RE: AKI and SKI problem with RFC 3280?, Peter Gutmann
  • RE: AKI and SKI problem with RFC 3280?, Stefan Santesson
    • Re: AKI and SKI problem with RFC 3280?, David P. Kemp
    • Re: AKI and SKI problem with RFC 3280?, David P. Kemp
  • Re: AKI and SKI problem with RFC 3280?, Tom Gindin
• new WG, Carl Wallace
• Last Call: 'X.509 Extensions for IP Addresses and AS Identifiers' to Proposed Standard, The IESG
• Re: POLL: Nonce-specific error code for OCSP, Florian Oelmaier
  • Re: POLL: Nonce-specific error code for OCSP, Julien Pierre
    • RE: POLL: Nonce-specific error code for OCSP, Michael Myers
      • Re: POLL: Nonce-specific error code for OCSP, Julien Pierre
      • DISCUSS: Nonce-specific error code for OCSP, Michael Myers
  • <Possible follow-ups>
  • Re: POLL: Nonce-specific error code for OCSP, Terry Hayes
  • RE: POLL: Nonce-specific error code for OCSP, Manger, James H
  • Re: POLL: Nonce-specific error code for OCSP, Frank Balluffi
  • RE: POLL: Nonce-specific error code for OCSP, Deacon, Alex
• draft-ietf-pkix-x509-ipaddr-as-extn-03.txt, Stephen Kent
• I-D ACTION:draft-ietf-pkix-certpathbuild-01.txt, Internet-Drafts
  • RE: I-D ACTION:draft-ietf-pkix-certpathbuild-01.txt, Peter Hesse
    • RE: I-D ACTION:draft-ietf-pkix-certpathbuild-01.txt, Alice Sturgeon
      • RE: I-D ACTION:draft-ietf-pkix-certpathbuild-01.txt, Matt Cooper
• RE: SUMMARY of nonces in OCSP, Ryan M. Hurst
• Nonce encoding (was RE: OCSP response pre-production), Tom Gindin
• Self-Issued certificate requirements?, Faisal Maqsood
  • Re: Self-Issued certificate requirements?, Lars Johansson
  • Re: Self-Issued certificate requirements?, Wen-Cheng Wang
• I-D ACTION:draft-ietf-pkix-x509-ipaddr-as-extn-03.txt, Internet-Drafts
• request for reviewing our interoperability experiment report, Nakagawa
  • Re: request for reviewing our interoperability experiment report, Anders Rundgren
    • Re: request for reviewing our interoperability experiment report, Nakagawa
• Re: would a key-less responder make better security, Peter Gutmann
• OCSP response pre-production (was RE: POLL: Use of nonces in OCS P), Deacon, Alex
  • Re: OCSP response pre-production (was RE: POLL: Use of nonces in OCS P), Paul Hoffman / IMC
  • Re: OCSP response pre-production (was RE: POLL: Use of nonces in OCSP), Denis Pinkas
• OCSP and Nonces, Miguel Rodriguez
  • <Possible follow-ups>
  • RE: OCSP and Nonces, Miguel Rodriguez
• RE: OCSP response pre-production, Ryan M. Hurst
  • <Possible follow-ups>
  • RE: OCSP response pre-production, Ryan M. Hurst
  • RE: OCSP response pre-production, Ryan M. Hurst
  • RE: OCSP response pre-production, Ryan M. Hurst
  • RE: OCSP response pre-production, Ryan M. Hurst
  • RE: OCSP response pre-production, Deacon, Alex
    • RE: OCSP response pre-production, Michael Myers
    • RE: OCSP response pre-production, Paul Hoffman / IMC
      • RE: OCSP response pre-production, Florian Oelmaier
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Paul Hoffman / IMC
  • RE: OCSP response pre-production, Deacon, Alex
    • RE: OCSP response pre-production, Florian Oelmaier
    • RE: OCSP response pre-production, Miguel Rodriguez
  • RE: OCSP response pre-production, Deacon, Alex
    • RE: OCSP response pre-production, Michael Myers
  • RE: OCSP response pre-production, Manger, James H
    • Re: OCSP response pre-production, Denis Pinkas
      • RE: OCSP response pre-production, Florian Oelmaier
      • Re: OCSP response pre-production, Denis Pinkas
      • RE: OCSP response pre-production, Florian Oelmaier
      • Re: OCSP response pre-production, Denis Pinkas
      • RE: OCSP response pre-production, Ambarish Malpani
      • Re: OCSP response pre-production, Julien Stern
      • RE: OCSP response pre-production, Florian Oelmaier
      • RE: OCSP response pre-production, Miguel Rodriguez
      • RE: OCSP response pre-production, Miguel Rodriguez
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Florian Oelmaier
      • Man-in-the-middle attacks (was: OCSP response pre-production), Paul Hoffman / IMC
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Ambarish Malpani
      • RE: OCSP response pre-production, Michael Myers
  • RE: OCSP response pre-production, Ryan M. Hurst
  • RE: OCSP response pre-production, Manger, James H
  • RE: OCSP response pre-production, Manger, James H
  • RE: OCSP response pre-production, Florian Oelmaier
  • Re: OCSP response pre-production, Peter Sylvester
  • RE: OCSP response pre-production, Florian Oelmaier
    • RE: OCSP response pre-production, Paul Hoffman / IMC
      • RE: OCSP response pre-production, Florian Oelmaier
      • RE: OCSP response pre-production, Paul Hoffman / IMC
    • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Florian Oelmaier
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Florian Oelmaier
  • RE: OCSP response pre-production, David Engberg
    • Re: OCSP response pre-production, Jean-Marc Desperrier
      • Re: OCSP response pre-production, David Engberg
      • RE: OCSP response pre-production, Ambarish Malpani
    • RE: OCSP response pre-production, Terry Hayes
      • RE: OCSP response pre-production, Michael Myers
  • RE: OCSP response pre-production, Florian Oelmaier
    • Re: OCSP response pre-production, Julien Stern
      • RE: OCSP response pre-production, Michael Myers
      • Re: OCSP response pre-production, David Engberg
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Michael Myers
      • Re: OCSP response pre-production, David Engberg
      • RE: OCSP response pre-production, Florian Oelmaier
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Florian Oelmaier
      • RE: OCSP response pre-production, Miguel Rodriguez
  • Re: OCSP response pre-production, Florian Oelmaier
  • RE: OCSP response pre-production, Peter Gutmann
  • RE: OCSP response pre-production, Frank Balluffi
    • RE: OCSP response pre-production, Michael Myers
  • RE: OCSP response pre-production, Frank Balluffi
    • Re: OCSP response pre-production, Jean-Marc Desperrier
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Ambarish Malpani
      • Re: OCSP response pre-production, Jean-Marc Desperrier
      • RE: OCSP response pre-production, Florian Oelmaier
      • RE: OCSP response pre-production, Florian Oelmaier
      • Re: OCSP response pre-production, Jean-Marc Desperrier
      • RE: OCSP response pre-production, Florian Oelmaier
  • RE: OCSP response pre-production, Frank Balluffi
  • RE: OCSP response pre-production, Deacon, Alex
    • RE: OCSP response pre-production, Michael Myers
      • POLL: Nonce-specific error code for OCSP, Michael Myers
      • Re: POLL: Nonce-specific error code for OCSP, Denis Pinkas
      • RE: POLL: Nonce-specific error code for OCSP, Michael Myers
      • RE: POLL: Nonce-specific error code for OCSP, Joseph A. Doekbrijder
      • RE: POLL: Nonce-specific error code for OCSP, Miguel Rodriguez
      • Re: POLL: Nonce-specific error code for OCSP, Richard Sinn (Infoblox)
      • DISCUSSION: Nonce-specific error code for OCSP, David Engberg
      • RE: DISCUSSION: Nonce-specific error code for OCSP, Michael Myers
      • RE: DISCUSSION: Nonce-specific error code for OCSP, Florian Oelmaier
      • RE: DISCUSSION: Nonce-specific error code for OCSP, Florian Oelmaier
      • RE: DISCUSSION: Nonce-specific error code for OCSP, Michael Myers
      • RE: DISCUSSION: Nonce-specific error code for OCSP, Florian Oelmaier
      • Re: DISCUSSION: Nonce-specific error code for OCSP, David Engberg
      • RE: DISCUSSION: Nonce-specific error code for OCSP, Michael Myers
      • Re: DISCUSSION: Nonce-specific error code for OCSP, David Engberg
      • RE: POLL: Nonce-specific error code for OCSP, Liaquat Khan
      • Re: POLL: Nonce-specific error code for OCSP, Richard Sinn
      • Re: POLL: Nonce-specific error code for OCSP, Julien Pierre
      • Re: Nonce-specific error code for OCSP, Piyush
• RE: POLL: Use of nonces in OCSP, David Engberg
  • RE: POLL: Use of nonces in OCSP, Michael Myers
    • OCSP response pre-production, Michael Myers
      • Not using nonce does not necessarily allow replay attacks ..., Julien Stern
      • Re: Not using nonce does not necessarily allow replay attacks ..., Vadim Fedukovich
      • [offlist] RE: Not using nonce does not necessarily allow replay attacks ..., Florian Oelmaier
    • Re: POLL: Use of nonces in OCSP, David Engberg
  • Message not available
    • Re: POLL: Use of nonces in OCSP, David Engberg
  • would a key-less responder make better security (was: POLL: Use of nonces in OCSP), Vadim Fedukovich
    • Re: would a key-less responder make better security, David Engberg
      • Re: would a key-less responder make better security, Vadim Fedukovich
      • Re: would a key-less responder make better security, David Engberg
  • <Possible follow-ups>
  • RE: POLL: Use of nonces in OCSP, Ryan M. Hurst
    • Re: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Paul Hoffman / IMC
      • Re: OCSP response pre-production, Dr Stephen Henson
      • Re: OCSP response pre-production, Paul Hoffman / IMC
      • Re: OCSP response pre-production, Dr Stephen N Henson
      • Re: OCSP response pre-production, David Engberg
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Florian Oelmaier
      • Re: OCSP response pre-production, David Engberg
      • RE: OCSP response pre-production, Michael Myers
      • RE: OCSP response pre-production, Florian Oelmaier
• Re: POLL: Use of nonces in OCSP, Peter Gutmann
  • Re: POLL: Use of nonces in OCSP, Yasir Khan
  • <Possible follow-ups>
  • RE: POLL: Use of nonces in OCSP, Wertz, Eric
  • RE: POLL: Use of nonces in OCSP, Miguel Rodriguez
  • RE: POLL: Use of nonces in OCSP, Ryan M. Hurst
    • RE: POLL: Use of nonces in OCSP, Michael Myers
  • RE: POLL: Use of nonces in OCSP, Ryan M. Hurst
  • RE: POLL: Use of nonces in OCSP, Deacon, Alex
  • RE: POLL: Use of nonces in OCSP, Russ Housley
• SCVP additions, Stephen Kent
  • Re: SCVP additions, Denis Pinkas
  • <Possible follow-ups>
  • RE: SCVP additions, Trevor Freeman
  • RE: SCVP additions, Stephen Kent
    • POLL: Use of nonces in OCSP, Michael Myers
      • Re: POLL: Use of nonces in OCSP, Dr Stephen Henson
      • Re: POLL: Use of nonces in OCSP, Dr Stephen Henson
      • Re: POLL: Use of nonces in OCSP, Terry Hayes
      • Re: POLL: Use of nonces in OCSP, Richard Levitte - VMS Whacker
      • RE: POLL: Use of nonces in OCSP, Ambarish Malpani
      • RE: POLL: Use of nonces in OCSP, Florian Oelmaier
      • Re: POLL: Use of nonces in OCSP, Marius Marian
      • SUMMARY of nonces in OCSP, Michael Myers
      • RE: SUMMARY of nonces in OCSP, Michael Myers
      • RE: SUMMARY of nonces in OCSP, Florian Oelmaier
  • RE: SCVP additions, Peter Sylvester
• WG last call re draft-pkix-acpolicies-extn-03.txt, Stephen Kent
  • WG last call re draft-pkix-acpolicies-extn-03.txt, Jim Schaad
    • Re: WG last call re draft-pkix-acpolicies-extn-03.txt, Denis Pinkas
      • Re: WG last call re draft-pkix-acpolicies-extn-03.txt, Russ Housley
      • RE: WG last call re draft-pkix-acpolicies-extn-03.txt, Jim Schaad
      • WG last call: draft-pkix-acpolicies-extn-03.txt, Tim Polk
• draft-ietf-pkix-x509-ipaddr-as-extn-02.txt, Stephen Kent
  • RE: draft-ietf-pkix-x509-ipaddr-as-extn-02.txt, Jim Schaad
• I-D ACTION:draft-ietf-pkix-x509-ipaddr-as-extn-02.txt, Internet-Drafts
• I-D ACTION:draft-ietf-pkix-pkixrep-02.txt, Internet-Drafts
• new version of draft-ietf-pkix-x509-ipaddr-as-extn-02.txt, Charles Lynn
• How a SCVP client authenticates the SCVP server?, Wen-Cheng Wang
  • RE: How a SCVP client authenticates the SCVP server?, Santosh Chokhani
    • Re: How a SCVP client authenticates the SCVP server?, Denis Pinkas
  • <Possible follow-ups>
  • RE: How a SCVP client authenticates the SCVP server?, Trevor Freeman
    • Re: How a SCVP client authenticates the SCVP server?, Denis Pinkas
      • Re: How a SCVP client authenticates the SCVP server?, Wen-Cheng Wang
      • Re: How a SCVP client authenticates the SCVP server?, Denis Pinkas
      • Re: How a SCVP client authenticates the SCVP server?, Wen-Cheng Wang
      • Re: How a SCVP client authenticates the SCVP server?, Denis Pinkas
  • RE: How a SCVP client authenticates the SCVP server?, Stephen Kent
  • RE: How a SCVP client authenticates the SCVP server?, Wen-Cheng Wang
  • RE: How a SCVP client authenticates the SCVP server?, Trevor Freeman
  • RE: How a SCVP client authenticates the SCVP server?, Wen-Cheng Wang
  • RE: How a SCVP client authenticates the SCVP server?, Trevor Freeman
    • Re: How a SCVP client authenticates the SCVP server?, Wen-Cheng Wang
• [OCSP] are several requests for different CAs at once valid ?, Julien Stern
  • RE: [OCSP] are several requests for different CAs at once valid ?, Miguel Rodriguez
  • RE: [OCSP] are several requests for different CAs at once valid ?, Ambarish Malpani
  • Re: [OCSP] are several requests for different CAs at once valid ?, Julien Stern
  • <Possible follow-ups>
  • Re: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ambarish Malpani
  • RE: [OCSP] are several requests for different CAs at once valid ?, Liaquat Khan
  • Re: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
  • Re: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ambarish Malpani
      • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
      • RE: [OCSP] are several requests for different CAs at once valid ?, Ambarish Malpani
  • Re: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
  • Re: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
  • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
  • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
    • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
  • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
    • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
  • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
  • RE: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
      • Re: [OCSP] are several requests for different CAs at once valid ?, Vadim Fedukovich
      • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
      • Re: [OCSP] are several requests for different CAs at once valid ?, Vadim Fedukovich
  • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
  • RE: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
      • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
      • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
      • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
      • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
      • RE: [OCSP] are several requests for different CAs at once valid ?, Ambarish Malpani
      • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
      • RE: [OCSP] are several requests for different CAs at once valid ?, Ambarish Malpani
  • RE: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
    • RE: [OCSP] are several requests for different CAs at once valid ?, Liaquat Khan
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
  • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
  • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
  • RE: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
  • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
    • RE: [OCSP] are several requests for different CAs at once valid ?, Ryan M. Hurst
      • RE: [OCSP] are several requests for different CAs at once valid ?, Ambarish Malpani
      • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
  • RE: [OCSP] are several requests for different CAs at once valid ?, Deacon, Alex
    • RE: [OCSP] are several requests for different CAs at once valid ?, Stephen Kent
  • RE: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
  • RE: [OCSP] are several requests for different CAs at once valid ?, Peter Gutmann
  • RE: [OCSP] are several requests for different CAs at once valid ?, Florian Oelmaier
• SCVP policy, Peter Sylvester
  • <Possible follow-ups>
  • RE: SCVP policy, Trevor Freeman
• RE: WG last call - DER-encoded BIT STRING for IPAddress, Manger, James H
  • RE: WG last call - DER-encoded BIT STRING for IPAddress, Jim Schaad
    • RE: WG last call - DER-encoded BIT STRING for IPAddress, Stephen Kent
• Standards for Web-signing, Anders Rundgren
  • Standards for Web-signing II, Anders Rundgren
    • RE: Standards for Web-signing II, Markus Lorch
      • Re: Standards for Web-signing II, Anders Rundgren
      • RE: Standards for Web-signing II, Florian Oelmaier
• UTF8 revisited, Lars Johansson
  • Re: UTF8 revisited, Jean-Marc Desperrier
• RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Trevor Freeman
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
  • <Possible follow-ups>
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Trevor Freeman
    • AIA for SCVP, Michael Myers
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Liaquat Khan
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Liaquat Khan
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • SCVP delegation (was SCVP-AIA), Ambarish Malpani
      • Re: SCVP delegation (was SCVP-AIA), Stephen Kent
      • RE: SCVP delegation (was SCVP-AIA), Ambarish Malpani
      • RE: SCVP delegation (was SCVP-AIA), Stephen Kent
      • RE: SCVP delegation (was SCVP-AIA), Ambarish Malpani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Santosh Chokhani
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Ambarish Malpani
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Wen-Cheng Wang
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Liaquat Khan
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Michael Myers
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Terwilliger, Ann
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Trevor Freeman
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Wen-Cheng Wang
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Wen-Cheng Wang
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Wen-Cheng Wang
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Gutmann
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Florian Oelmaier
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Wen-Cheng Wang
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Wen-Cheng Wang
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Peter Sylvester
• RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Ryan M. Hurst
  • <Possible follow-ups>
  • RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Stephen Kent
    • RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Ryan M. Hurst
      • RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Stephen Kent
      • RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Tim Polk
• RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID m atching), Terwilliger, Ann
  • RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID m atching), Stephen Kent
  • RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Peter Hesse
• I-D ACTION:draft-ietf-pkix-proxy-08.txt, Internet-Drafts
• Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), chris . gilbert
  • RE: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Peter Hesse
  • Re: Making more of Key IDs (was RE: 3280 Question WRT SKID/AKID matching), Stephen Kent
• RE: IP addr: 01: WG last call, Manger, James H
  • <Possible follow-ups>
  • RE: IP addr: 01: WG last call, Stephen Kent
  • RE: IP addr: 01: WG last call, Charles Lynn
  • RE: IP addr: 01: WG last call, Manger, James H
• 3280 Question WRT SKID/AKID matching, Matt Cooper
  • Re: 3280 Question WRT SKID/AKID matching, Steve Hanna
    • RE: 3280 Question WRT SKID/AKID matching, L Williams
      • RE: 3280 Question WRT SKID/AKID matching, Peter Hesse
      • Re: 3280 Question WRT SKID/AKID matching, Jean-Marc Desperrier
  • <Possible follow-ups>
  • RE: 3280 Question WRT SKID/AKID matching, Tim Moses
• WG last call, Stephen Kent
  • RE: WG last call, Jim Schaad
    • RE: WG last call, Jim Schaad
      • RE: WG last call, Steven Legg
  • <Possible follow-ups>
  • RE: WG last call, Charles Lynn
    • RE: WG last call, Jim Schaad
• Last Call: 'Internet X.509 Public Key Infrastructure Warranty Certificate Extension' to Informational RFC, The IESG
  • Message not available
    • Re: Last Call: 'Warranty Certificate Extension' to Informational RFC, Denis Pinkas
• Document Action: 'Policy Requirements for Time-Stamping Authorities' to Informational RFC, The IESG
• FW:Resend PKIX LDAPv3 schema: component matching or separate ent ries, Sharon Boeyen
• PKIX LDAPv3 schema: component matching or separate entries, Steve Hanna
  • <Possible follow-ups>
  • RE: PKIX LDAPv3 schema: component matching or separate entries, Sharon Boeyen
• I-D ACTION:draft-ietf-pkix-pr-tsa-05.txt, Internet-Drafts
• first comments for SCVP 12, Peter Sylvester
  • <Possible follow-ups>
  • Re: first comments for SCVP 12, Peter Sylvester
• I-D ACTION:draft-deacon-xkms-aia-00.txt, Internet-Drafts
  • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Faisal
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Faisal
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Denis Pinkas
      • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt [SCVP-AIA], Stephen Kent
  • <Possible follow-ups>
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt, Ryan M. Hurst
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt, Deacon, Alex
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt, Ryan M. Hurst
      • Message not available
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt, Ryan M. Hurst
    • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt, Rich Salz
      • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt, Ryan M. Hurst
  • RE: I-D ACTION:draft-deacon-xkms-aia-00.txt, Deacon, Alex
    • Re: I-D ACTION:draft-deacon-xkms-aia-00.txt, Rich Salz
• Multi-valued RDNs, Sharon Boeyen
• Clarification on XMPP log for certificate types, Blake Ramsdell
  • Issuer field on Certificates, Nikolas Mihalopoulos
• Comments on draft-ietf-pkix-sonof3039-01.txt, Jim Schaad
  • <Possible follow-ups>
  • RE: Comments on draft-ietf-pkix-sonof3039-01.txt, Stefan Santesson
• SCVP Comment, Jim Schaad
• I-D ACTION:draft-ietf-pkix-pi-07.txt, Internet-Drafts
  • Re: I-D ACTION:draft-ietf-pkix-pi-07.txt, Denis Pinkas
    • RE: I-D ACTION:draft-ietf-pkix-pi-07.txt, Jim Schaad
• WG Last Call draft-ietf-pkix-SCVP-12.txt, Jim Schaad
• I-D ACTION:draft-ietf-pkix-sca-00.txt, Internet-Drafts
• I-D ACTION:draft-ietf-pkix-logotypes-11.txt, Internet-Drafts
• Document Action: 'Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework' to an Informational RFC, The IESG
• I-D ACTION:draft-ietf-pkix-dnstrings-02.txt, Internet-Drafts
• I-D ACTION:draft-ietf-pkix-sonof3039-01.txt, Internet-Drafts
  • <Possible follow-ups>
  • RE: I-D ACTION:draft-ietf-pkix-sonof3039-01.txt, Stefan Santesson
• draft-ietf-pkix-scvp-12.txt, Frank Balluffi
• Re: Microsoft and multi-valued RDNs (was: draft minutes), Peter Gutmann
  • Re: Microsoft and multi-valued RDNs (was: draft minutes), Michael Ströder
  • Re: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
  • Re: Microsoft and multi-valued RDNs (was: draft minutes), Leif Johansson
    • Re: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Leif Johansson
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Leif Johansson
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Leif Johansson
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), David Chadwick
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Leif Johansson
  • <Possible follow-ups>
  • Re: Microsoft and multi-valued RDNs (was: draft minutes), Peter Gutmann
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Trevor Freeman
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Trevor Freeman
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Peter Gutmann
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Peter Gutmann
    • Re: Microsoft and multi-valued RDNs (was: draft minutes), todd glassey
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Adrian McCullagh
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
    • Re: Microsoft and multi-valued RDNs (was: draft minutes), todd glassey
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Peter Gietz
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), todd glassey
      • Re: Microsoft and multi-valued RDNs (was: draft minutes), Leif Johansson
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Peter Gutmann
    • RE: Microsoft and multi-valued RDNs (was: draft minutes), Stephen Kent
  • RE: Microsoft and multi-valued RDNs (was: draft minutes), Hallam-Baker, Phillip
    • Re: Microsoft and multi-valued RDNs (was: draft minutes), todd glassey
• Draft-ietf-pkix-proxy-06.txt, Jim Schaad
  • Re: Draft-ietf-pkix-proxy-06.txt, Von Welch
    • RE: Draft-ietf-pkix-proxy-06.txt, Jim Schaad
      • RE: Draft-ietf-pkix-proxy-06.txt, Von Welch
      • RE: Draft-ietf-pkix-proxy-06.txt, Paul Hoffman / IMC
• I-D ACTION:draft-ietf-pkix-proxy-07.txt, Internet-Drafts
• Root CA key compromised, Lenka Kadlcakova
  • Re: Root CA key compromised, Joel S. Kazin
• LDAPv3 Profile Issue, David Chadwick
  • RE: LDAPv3 Profile Issue, Steven Legg
    • Re: LDAPv3 Profile Issue, David Chadwick
• Subject Certificate Access, David Chadwick
• Why is privateKeyUsagePeriod deprecated?, Peter Gutmann
  • Re: Why is privateKeyUsagePeriod deprecated?, David A. Cooper
    • Re: Why is privateKeyUsagePeriod deprecated?, David Chadwick
      • Re: Why is privateKeyUsagePeriod deprecated?, Stephen Kent
      • RE: Why is privateKeyUsagePeriod deprecated?, Dean Adams
  • <Possible follow-ups>
  • RE: Why is privateKeyUsagePeriod deprecated?, Sharon Boeyen
  • RE: Why is privateKeyUsagePeriod deprecated?, Montpetit, Daniel
  • Re: Why is privateKeyUsagePeriod deprecated?, Peter Gutmann
    • Re: Why is privateKeyUsagePeriod deprecated?, Michael Ströder
      • Re: Why is privateKeyUsagePeriod deprecated?, Gregory S. Chudov
      • Re: Why is privateKeyUsagePeriod deprecated?, Tony Bartoletti
  • Re: Why is privateKeyUsagePeriod deprecated?, Peter Gutmann
    • Re: Why is privateKeyUsagePeriod deprecated?, Gregory S. Chudov
  • Re: Why is privateKeyUsagePeriod deprecated?, Peter Gutmann
    • Re: Why is privateKeyUsagePeriod deprecated?, Russ Housley
      • RE: Why is privateKeyUsagePeriod deprecated?, Dean Adams
      • RE: Why is privateKeyUsagePeriod deprecated?, Russ Housley
      • Re: Why is privateKeyUsagePeriod deprecated?, Denis Pinkas
      • Re: Why is privateKeyUsagePeriod deprecated?, Stephen Kent

The web site for this mailing list is sponsored by the VPN Consortium. If you have any suggestions for additions or corrections to this Web page, please send them to paul.hoffman@vpnc.org.