keyassure Discussion Archive - Thread Index

[Prev Page] [Next Page] [Date Index] [IETF Mailing List Directory] [keyassure List Information]

• [keyassure] The draft and subj alt names, Olle E. Johansson
  • Re: [keyassure] The draft and subj alt names, Richard L. Barnes
    • Re: [keyassure] The draft and subj alt names, Jay Daley
      • Re: [keyassure] The draft and subj alt names, Richard L. Barnes
      • Re: [keyassure] The draft and subj alt names, Jay Daley
      • Re: [keyassure] The draft and subj alt names, Richard L. Barnes
      • Re: [keyassure] The draft and subj alt names, Paul Wouters
      • Re: [keyassure] The draft and subj alt names, Jeff Schmidt
      • Re: [keyassure] The draft and subj alt names, Martin Rex
      • Re: [keyassure] The draft and subj alt names, OndÅej SurÃ
  • <Possible follow-ups>
  • Re: [keyassure] The draft and subj alt names, =JeffH
• [keyassure] Use cases document., Warren Kumari
• [keyassure] Musing on design based on proposed use cases, Richard L. Barnes
  • Re: [keyassure] Musing on design based on proposed use cases, Eric Rescorla
    • Re: [keyassure] Musing on design based on proposed use cases, Richard L. Barnes
• [keyassure] Another comment from the mic, Eric Rescorla
  • Re: [keyassure] Another comment from the mic, Stephen Kent
  • Message not available
    • Re: [keyassure] Another comment from the mic, Eric Rescorla
• [keyassure] Objective: Restrictive versus Supplementary Models, Eric Rescorla
  • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Paul Wouters
    • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Stephen Kent
    • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Richard L. Barnes
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
  • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Yoav Nir
  • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Richard L. Barnes
    • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Eric Rescorla
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Richard L. Barnes
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Michael Richardson
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Jim Schaad
    • Re: [keyassure] Objective: Restrictive versus Supplementary Models, James Cloos
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Richard L. Barnes
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Jay Daley
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Eric Rescorla
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Jay Daley
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Richard L. Barnes
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Eric Rescorla
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Richard L. Barnes
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Paul Wouters
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Yoav Nir
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, James Cloos
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, James Cloos
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Paul Wouters
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Richard L. Barnes
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Yoav Nir
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Michael Richardson
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Yoav Nir
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Yoav Nir
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Paul Wouters
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Yoav Nir
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Paul Wouters
  • Re: [keyassure] Objective: Restrictive versus Supplementary Models, James Cloos
  • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
    • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Eric Rescorla
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Martin Rex
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Eric Rescorla
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Warren Kumari
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Michael Richardson
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Paul Wouters
      • Re: [keyassure] Objective: Restrictive versus Supplementary Models, Eric Rescorla
• [keyassure] PROPOSAL: Revision of DANE client requirements, Zack Weinberg
  • [keyassure] TLSA record does not mandate the given certificate, Michael Richardson
    • Re: [keyassure] TLSA record does not mandate the given certificate, Zack Weinberg
      • Re: [keyassure] TLSA record does not mandate the given certificate, Jay Daley
      • Re: [keyassure] TLSA record does not mandate the given certificate, Zack Weinberg
      • Re: [keyassure] TLSA record does not mandate the given certificate, Jay Daley
      • Re: [keyassure] TLSA record does not mandate the given certificate, Zack Weinberg
      • Re: [keyassure] TLSA record does not mandate the given certificate, Paul Wouters
      • Re: [keyassure] TLSA record does not mandate the given certificate, Richard L. Barnes
      • Re: [keyassure] TLSA record does not mandate the given certificate, Zack Weinberg
  • Re: [keyassure] PROPOSAL: Revision of DANE client requirements, Paul Wouters
    • Re: [keyassure] PROPOSAL: Revision of DANE client requirements, Zack Weinberg
      • Re: [keyassure] PROPOSAL: Revision of DANE client requirements, Paul Wouters
• Re: [keyassure] [dane] #14: Bare Public Keys, dane issue tracker
  • <Possible follow-ups>
  • Re: [keyassure] [dane] #14: Bare Public Keys, dane issue tracker
• [keyassure] Mis-issued certs for Google / Yahoo / Skype, etc., Warren Kumari
  • Re: [keyassure] Mis-issued certs for Google / Yahoo / Skype, etc., OndÅej SurÃ
• Re: [keyassure] [dane] #9: Self-Signed Certificates, dane issue tracker
• Re: [keyassure] [dane] #11: Hash Function Strength, dane issue tracker
  • <Possible follow-ups>
  • Re: [keyassure] [dane] #11: Hash Function Strength, dane issue tracker
• Re: [keyassure] [dane] #5: Protocol support -- TLS / DTLS / IPsec or larger., dane issue tracker
• [keyassure] [dane] #23: Asserting DANE exclusivity for an entire domain, dane issue tracker
  • Re: [keyassure] [dane] #23: Asserting DANE exclusivity for an entire domain, Paul Wouters
    • Re: [keyassure] [dane] #23: Asserting DANE exclusivity for an entire domain, Matt McCutchen
• [keyassure] [dane] #22: Provide the security of the strongest digest supported by both sides, dane issue tracker
  • Re: [keyassure] [dane] #22: Provide the security of the strongest digest supported by both sides, dane issue tracker
• [keyassure] Starting Working Group Last Call for draft-ietf-dane-protocol-06, Warren Kumari
• [keyassure] Issues that no longer issues?, Warren Kumari
  • Re: [keyassure] Issues that no longer issues?, Paul Wouters
    • [keyassure] Bare keys again, Paul Hoffman
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Martin Rex
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Eric Rescorla
      • Re: [keyassure] Bare keys again, Phillip Hallam-Baker
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Jeff Schmidt
      • Re: [keyassure] Bare keys again, Paul Hoffman
      • Re: [keyassure] Bare keys again, Henry Story
      • Re: [keyassure] Bare keys again, Paul Hoffman
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Douglas Otis
      • Re: [keyassure] Bare keys again, Douglas Otis
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Ben Laurie
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Matt McCutchen
      • Re: [keyassure] Bare keys again, Martin Rex
      • Re: [keyassure] Bare keys again, Martin Rex
      • Re: [keyassure] Bare keys again, Stephen Kent
      • Re: [keyassure] Bare keys again, Paul Hoffman
      • Re: [keyassure] Bare keys again, Eric Rescorla
      • Re: [keyassure] Bare keys again, Paul Wouters
      • Re: [keyassure] Bare keys again, Eric Rescorla
  • Re: [keyassure] Issues that no longer issues?, OndÅej SurÃ
• [keyassure] Call for Participation: SATIN 2011, Richard Clayton
• [keyassure] End entity certificate matching, trust anchors, and protocol-06, Paul Hoffman
  • Re: [keyassure] End entity certificate matching, trust anchors, and protocol-06, Peter Gutmann
  • [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Peter Palfrader
    • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Jakob Schlyter
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Peter Palfrader
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Paul Hoffman
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Paul Wouters
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Peter Palfrader
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Stephen Kent
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Richard L. Barnes
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Jay Daley
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Richard L. Barnes
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Jay Daley
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Eric Rescorla
      • Re: [keyassure] CN/SAN matching (was: End entity certificate, Martin Rex
      • Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06), Richard L. Barnes
  • <Possible follow-ups>
  • Re: [keyassure] End entity certificate matching, trust anchors, and protocol-06, Peter Gutmann
• [keyassure] I-D Action:draft-ietf-dane-protocol-06.txt, Internet-Drafts
• Re: [keyassure] [dane] #21: Need to specify which crypto algorithms and certificate types are mandatory to implement, dane issue tracker
• [keyassure] Not yet for WG consideration: draft-hoffman-dane-smime-00.txt, Paul Hoffman
• Re: [keyassure] [dane] #19: Format for TLSA DNS lookup., dane issue tracker
• Re: [keyassure] [dane] protocol #19 (new): Format for TLSA DNS lookup., Warren Kumari
• [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Warren Kumari
  • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Phillip Hallam-Baker
    • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Stephen Farrell
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Nicholas Weaver
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Chris Palmer
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Stephen Farrell
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Nicholas Weaver
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Stephen Farrell
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Stephen Farrell
      • [keyassure] crypto hash alg deprecation is a myth, Martin Rex
      • Re: [keyassure] crypto hash alg deprecation is a myth, Rob Stradling
      • Re: [keyassure] crypto hash alg deprecation is a myth, Phillip Hallam-Baker
      • Re: [keyassure] crypto hash alg deprecation is a myth, Andrew Sullivan
      • Re: [keyassure] crypto hash alg deprecation is a myth, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Warren Kumari
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Sean Turner
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Nicholas Weaver
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Yoav Nir
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Andrew Sullivan
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Andrew Sullivan
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, bmanning
  • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Paul Hoffman
    • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Jakob Schlyter
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Paul Hoffman
  • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Warren Kumari
    • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Scott Schmit
    • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Murray S. Kucherawy
    • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Murray S. Kucherawy
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
    • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Ben Laurie
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Jakob Schlyter
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", George Barwood
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Yoav Nir
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Chris Palmer
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Warren Kumari
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Chris Palmer
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Chris Palmer
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Brian Smith
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Jakob Schlyter
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Sean Turner
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Nicholas Weaver
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, bmanning
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Yoav Nir
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Tony Hansen
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Martin Rex
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, bmanning
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Phillip Hallam-Baker
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Chris Palmer
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Warren Kumari
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Paul Hoffman
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Warren Kumari
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Peter Gutmann
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, bmanning
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Ben Laurie
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, George Barwood
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto, Rob Stradling
      • Re: [keyassure] Opening issue #21: "Need to specify which crypto algorithms and certificate types are mandatory to implement", Jakob Schlyter
• [keyassure] Meeting in Prague., Warren Kumari
  • Re: [keyassure] Meeting in Prague., Warren Kumari
• [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Internet-Drafts
  • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Jakob Schlyter
    • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Ben Laurie
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Jakob Schlyter
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Martin Rex
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Paul Hoffman
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Martin Rex
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Paul Hoffman
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Peter Gutmann
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Stephen Kent
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Martin Rex
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-05.txt, Stephen Kent
• [keyassure] Interpreting certificates (and summary), Scott Schmit
  • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
    • Re: [keyassure] Interpreting certificates (and summary), Paul Wouters
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Paul Wouters
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Paul Wouters
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Paul Wouters
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Paul Wouters
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Martin Rex
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Peter Gutmann
  • Re: [keyassure] Interpreting certificates (and summary), Paul Wouters
  • Re: [keyassure] Interpreting certificates (and summary), Stephen Kent
    • Re: [keyassure] Interpreting certificates (and summary), Scott Schmit
      • Re: [keyassure] Interpreting certificates (and summary), Stephen Kent
  • Re: [keyassure] Interpreting certificates (and summary), Martin Rex
    • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
      • Re: [keyassure] Interpreting certificates (and summary), Martin Rex
      • Re: [keyassure] Interpreting certificates (and summary), Zack Weinberg
      • Re: [keyassure] Interpreting certificates (and summary), Paul Hoffman
      • Re: [keyassure] Interpreting certificates (and summary), Zack Weinberg
      • Re: [keyassure] Interpreting certificates (and summary), Phillip Hallam-Baker
• [keyassure] [dane] protocol #21 (new): Need to specify which crypto algorithms and certificate types are mandatory to implement, dane issue tracker
• [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, dane issue tracker
  • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Peter Gutmann
    • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Paul Hoffman
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Scott Schmit
    • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Phillip Hallam-Baker
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Stephen Kent
  • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Stephen Kent
    • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Lawrence Conroy
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Ilari Liusvaara
    • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Paul Hoffman
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Stephen Kent
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Paul Hoffman
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Phillip Hallam-Baker
    • Re: [keyassure] [dane] protocol #20 (new): Change the format of the, Martin Rex
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the, Stephen Kent
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of, Martin Rex
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of, Stephen Kent
      • Message not available
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the, Phillip Hallam-Baker
  • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Warren Kumari
    • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Ilari Liusvaara
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Jakob Schlyter
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Phillip Hallam-Baker
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Carl Wallace
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Phillip Hallam-Baker
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Paul Wouters
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Peter Gutmann
      • Re: [keyassure] [dane] protocol #20 (new): Change the format of the two fields to have fewer certificate types, Paul Wouters
• [keyassure] The SSL Proxy Issue, Phillip Hallam-Baker
  • Re: [keyassure] The SSL Proxy Issue, Adam Langley
    • Re: [keyassure] The SSL Proxy Issue, Phillip Hallam-Baker
      • Re: [keyassure] The SSL Proxy Issue, Paul Hoffman
      • Re: [keyassure] The SSL Proxy Issue, Steingruebl, Andy
      • Re: [keyassure] The SSL Proxy Issue, Paul Hoffman
      • Re: [keyassure] The SSL Proxy Issue, Phillip Hallam-Baker
      • Re: [keyassure] The SSL Proxy Issue, Scott Schmit
      • Re: [keyassure] The SSL Proxy Issue, Paul Hoffman
      • Re: [keyassure] The SSL Proxy Issue, Phillip Hallam-Baker
      • Re: [keyassure] The SSL Proxy Issue, Paul Hoffman
      • Re: [keyassure] The SSL Proxy Issue, Yoav Nir
      • Re: [keyassure] The SSL Proxy Issue, Yoav Nir
  • Re: [keyassure] The SSL Proxy Issue, Steingruebl, Andy
    • Re: [keyassure] The SSL Proxy Issue, Steingruebl, Andy
• Re: [keyassure] [dane] protocol #3 (closed): Format of the record., dane issue tracker
• [keyassure] Bootstrapping Dane Adoption, Henry Story
  • Re: [keyassure] Bootstrapping Dane Adoption, Adam Langley
    • Re: [keyassure] Bootstrapping Dane Adoption, Henry Story
      • Re: [keyassure] Bootstrapping Dane Adoption, Adam Langley
      • Re: [keyassure] Bootstrapping Dane Adoption, Henry Story
      • Re: [keyassure] Bootstrapping Dane Adoption, Matt McCutchen
      • Re: [keyassure] Bootstrapping Dane Adoption, Adam Langley
      • Re: [keyassure] Bootstrapping Dane Adoption, Henry Story
      • Re: [keyassure] Bootstrapping Dane Adoption, Adam Langley
    • Re: [keyassure] Bootstrapping Dane Adoption, Richard L. Barnes
      • Re: [keyassure] Bootstrapping Dane Adoption, Matt McCutchen
    • Re: [keyassure] Bootstrapping Dane Adoption, Paul Wouters
      • Re: [keyassure] Bootstrapping Dane Adoption, Adam Langley
      • Re: [keyassure] Bootstrapping Dane Adoption, Paul Wouters
      • Re: [keyassure] Bootstrapping Dane Adoption, Adam Langley
      • Re: [keyassure] Bootstrapping Dane Adoption, Paul Wouters
      • Re: [keyassure] Bootstrapping Dane Adoption, Adam Langley
      • Re: [keyassure] Bootstrapping Dane Adoption, Paul Wouters
      • Re: [keyassure] Bootstrapping Dane Adoption, Yoav Nir
      • Re: [keyassure] Bootstrapping Dane Adoption, Yoav Nir
      • Re: [keyassure] Bootstrapping Dane Adoption, Phillip Hallam-Baker
      • Re: [keyassure] Bootstrapping Dane Adoption, Richard L. Barnes
      • Re: [keyassure] Bootstrapping Dane Adoption, Richard L. Barnes
      • Re: [keyassure] Bootstrapping Dane Adoption, Andrew Sullivan
      • Re: [keyassure] Bootstrapping Dane Adoption, Martin Rex
      • Re: [keyassure] Bootstrapping Dane Adoption, Mark Andrews
      • Re: [keyassure] Bootstrapping Dane Adoption, John Gilmore
      • Re: [keyassure] Bootstrapping Dane Adoption, Richard L. Barnes
      • Re: [keyassure] Bootstrapping Dane Adoption, Mark Andrews
      • Re: [keyassure] Bootstrapping Dane Adoption, Martin Rex
• [keyassure] Proof-of-concept implementation for NSS, Matt McCutchen
  • Re: [keyassure] Proof-of-concept implementation for NSS, Paul Wouters
• Re: [keyassure] [dane] protocol #14 (new): Bare Public Keys, dane issue tracker
• [keyassure] publishing the public key, Henry Story
  • Re: [keyassure] publishing the public key, Ilari Liusvaara
    • Re: [keyassure] publishing the public key, Henry Story
    • Re: [keyassure] publishing the public key, Scott Schmit
      • Re: [keyassure] publishing the public key, Paul Wouters
      • Re: [keyassure] publishing the public key, Paul Hoffman
      • Re: [keyassure] publishing the public key, Paul Wouters
      • Re: [keyassure] publishing the public key, Ilari Liusvaara
      • Re: [keyassure] publishing the public key, Paul Hoffman
      • Re: [keyassure] publishing the public key, Paul Wouters
      • Re: [keyassure] publishing the public key, Peter Gutmann
      • Re: [keyassure] publishing the public key, Paul Wouters
      • Re: [keyassure] publishing the public key, Paul Hoffman
      • Re: [keyassure] publishing the public key, Paul Wouters
      • Re: [keyassure] publishing the public key, Paul Hoffman
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Stephen Kent
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Stephen Kent
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Paul Hoffman
      • Re: [keyassure] publishing the public key, Henry Story
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Message not available
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Stephen Kent
    • Re: [keyassure] publishing the public key, Phillip Hallam-Baker
  • Re: [keyassure] publishing the public key, Paul Wouters
    • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Paul Hoffman
    • Re: [keyassure] publishing the public key, Martin Rex
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Martin Rex
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, John Gilmore
  • Re: [keyassure] publishing the public key, Paul Hoffman
  • <Possible follow-ups>
  • Re: [keyassure] publishing the public key, Paul Wouters
  • Re: [keyassure] publishing the public key, Paul Wouters
    • Re: [keyassure] Issue #14 - publishing the public key, Warren Kumari
      • Re: [keyassure] Issue #14 - publishing the public key, Paul Hoffman
    • Re: [keyassure] publishing the public key, Henry Story
  • Re: [keyassure] publishing the public key, Paul Wouters
    • Re: [keyassure] publishing the public key, Henry Story
  • Re: [keyassure] publishing the public key, Yaron Sheffer
    • Re: [keyassure] publishing the public key, Ilari Liusvaara
      • Re: [keyassure] publishing the public key, Yaron Sheffer
    • Re: [keyassure] publishing the public key, Paul Wouters
  • Re: [keyassure] publishing the public key, Peter Gutmann
  • Re: [keyassure] publishing the public key, Peter Gutmann
  • Re: [keyassure] publishing the public key, Peter Gutmann
    • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Phillip Hallam-Baker
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Paul Hoffman
      • Re: [keyassure] publishing the public key, Paul Wouters
      • Re: [keyassure] publishing the public key, Phillip Hallam-Baker
      • Re: [keyassure] publishing the public key, Peter Gutmann
      • Re: [keyassure] publishing the public key, Peter Gutmann
      • Re: [keyassure] publishing the public key, Phillip Hallam-Baker
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Henry Story
      • Re: [keyassure] publishing the public key, Peter Gutmann
      • Re: [keyassure] publishing the public key, Henry Story
• [keyassure] Binding to full TLS encapsulation or STARTTLS, Matt McCutchen
  • Re: [keyassure] Binding to full TLS encapsulation or STARTTLS, Phillip Hallam-Baker
• [keyassure] dane-04 trust anchors, Yaron Sheffer
  • Re: [keyassure] dane-04 trust anchors, Phillip Hallam-Baker
  • Re: [keyassure] dane-04 trust anchors, Paul Hoffman
    • Re: [keyassure] dane-04 trust anchors, Jim Schaad
  • Re: [keyassure] dane-04 trust anchors, Paul Wouters
    • Re: [keyassure] dane-04 trust anchors, Yaron Sheffer
    • Re: [keyassure] dane-04 trust anchors, Scott Schmit
      • Re: [keyassure] dane-04 trust anchors, Martin Rex
      • Re: [keyassure] dane-04 trust anchors, Henry Story
  • <Possible follow-ups>
  • Re: [keyassure] dane-04 trust anchors, Yaron Sheffer
    • Re: [keyassure] dane-04 trust anchors, Paul Hoffman
  • Re: [keyassure] dane-04 trust anchors, Yaron Sheffer
    • Re: [keyassure] dane-04 trust anchors, Stephen Farrell
      • Re: [keyassure] dane-04 trust anchors, Paul Hoffman
    • Re: [keyassure] dane-04 trust anchors, Paul Hoffman
• [keyassure] Special, four issues (#2, #9, #13, #18) for the price of one...., Warren Kumari
  • Re: [keyassure] Special, four issues (#2, #9, #13, #18) for the price of one...., Paul Hoffman
    • Re: [keyassure] Special, four issues (#2, #9, #13, #18) for the price of one...., Matt McCutchen
      • Re: [keyassure] Special, four issues (#2, #9, #13, #18) for the price of one...., Paul Hoffman
      • Re: [keyassure] Special, four issues (#2, #9, #13, #18) for the price of one...., Simon Josefsson
      • Re: [keyassure] Special, four issues (#2, #9, #13, #18) for the price of one...., Paul Hoffman
• [keyassure] Issue #3: Format of the record., Warren Kumari
  • Re: [keyassure] Issue #3: Format of the record., Matt McCutchen
  • Re: [keyassure] Issue #3: Format of the record., Phillip Hallam-Baker
    • Re: [keyassure] Issue #3: Format of the record., Nicholas Weaver
      • Re: [keyassure] Issue #3: Format of the record., Steingruebl, Andy
  • Re: [keyassure] Issue #3: Format of the record., Paul Wouters
    • Re: [keyassure] Issue #3: Format of the record., Warren Kumari
• Re: [keyassure] [dane] protocol #17 (closed): Should draft-ietf-dane-protocol support TLS only or be more ambitious?, dane issue tracker
• [keyassure] New -04 issued, Paul Hoffman
• [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Internet-Drafts
  • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Scott Schmit
    • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Paul Hoffman
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Stephen Kent
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Paul Hoffman
      • Message not available
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Ben Laurie
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Stephen Kent
      • Message not available
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Ben Laurie
      • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Stephen Kent
    • Re: [keyassure] I-D Action:draft-ietf-dane-protocol-04.txt, Stephen Kent
• [keyassure] WebID at W3C and keyassure, Henry Story
  • Message not available
    • Re: [keyassure] WebID at W3C and keyassure, Henry Story
      • Re: [keyassure] WebID at W3C and keyassure, Paul Hoffman
      • Re: [keyassure] WebID at W3C and keyassure, Henry Story
      • Re: [keyassure] WebID at W3C and keyassure, Phillip Hallam-Baker
      • Re: [keyassure] WebID at W3C and keyassure, Henry Story
      • Re: [keyassure] WebID at W3C and keyassure, Phillip Hallam-Baker
      • Re: [keyassure] WebID at W3C and keyassure, Henry Story
      • Re: [keyassure] WebID at W3C and keyassure, Jakob Schlyter
      • Re: [keyassure] WebID at W3C and keyassure, Phillip Hallam-Baker
      • Re: [keyassure] WebID at W3C and keyassure, Jakob Schlyter
      • Re: [keyassure] WebID at W3C and keyassure, Phillip Hallam-Baker
• [keyassure] Asserting DANE exclusivity for an entire domain, Matt McCutchen
  • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Phillip Hallam-Baker
    • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Zack Weinberg
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Nicholas Weaver
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Zack Weinberg
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Paul Wouters
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Zack Weinberg
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Martin Rex
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Zack Weinberg
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Matt McCutchen
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Martin Rex
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Paul Wouters
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Zack Weinberg
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Andrew Sullivan
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Zack Weinberg
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Andrew Sullivan
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Zack Weinberg
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Paul Wouters
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Matt McCutchen
      • Re: [keyassure] Asserting DANE exclusivity for an entire domain, Ilari Liusvaara