trans  

Messages by Thread

• • Re: [Trans] [trans] #126 (rfc6962-bis): text leaves open the possibility that a submitter might not verify the returned SCT trans issue tracker
• [Trans] [trans] #125 (rfc6962-bis): change "will return" to "MUST return" trans issue tracker
• [Trans] [trans] #124 (rfc6962-bis): introduction needs work trans issue tracker
  • Re: [Trans] [trans] #124 (rfc6962-bis): introduction needs work trans issue tracker
  • Re: [Trans] [trans] #124 (rfc6962-bis): introduction needs work trans issue tracker
• [Trans] Fwd: I-D Action: draft-kent-trans-architecture-01.txt Stephen Kent
• [Trans] [trans] #123 (rfc6962-bis): log clients description too informal, incomplete trans issue tracker
  • Re: [Trans] [trans] #123 (rfc6962-bis): log clients description too informal, incomplete trans issue tracker
  • Re: [Trans] [trans] #123 (rfc6962-bis): log clients description too informal, incomplete Stephen Kent
  • Re: [Trans] [trans] #123 (rfc6962-bis): log clients description too informal, incomplete Stephen Kent
  • Re: [Trans] [trans] #123 (rfc6962-bis): log clients description too informal, incomplete trans issue tracker
• [Trans] [trans] #122 (rfc6962-bis): TLS server requirements trans issue tracker
  • Re: [Trans] [trans] #122 (rfc6962-bis): TLS server requirements trans issue tracker
  • Re: [Trans] [trans] #122 (rfc6962-bis): TLS server requirements Stephen Kent
  • Re: [Trans] [trans] #122 (rfc6962-bis): TLS server requirements Paul Wouters
  • Re: [Trans] [trans] #122 (rfc6962-bis): TLS server requirements Stephen Kent
  • Re: [Trans] [trans] #122 (rfc6962-bis): TLS server requirements Paul Wouters
  • Re: [Trans] [trans] #122 (rfc6962-bis): TLS server requirements Stephen Kent
  • Re: [Trans] [trans] #122 (rfc6962-bis): TLS server requirements trans issue tracker
• [Trans] [trans] #121 (rfc6962-bis): log metadata dissemination trans issue tracker
  • Re: [Trans] [trans] #121 (rfc6962-bis): log metadata dissemination trans issue tracker
  • Re: [Trans] [trans] #121 (rfc6962-bis): log metadata dissemination trans issue tracker
  • Re: [Trans] [trans] #121 (rfc6962-bis): log metadata dissemination trans issue tracker
  • Re: [Trans] [trans] #121 (rfc6962-bis): log metadata dissemination trans issue tracker
• [Trans] [trans] #120 (rfc6962-bis): public vs. private logs? trans issue tracker
  • Re: [Trans] [trans] #120 (rfc6962-bis): public vs. private logs? trans issue tracker
  • Re: [Trans] [trans] #120 (rfc6962-bis): public vs. private logs? trans issue tracker
  • Re: [Trans] [trans] #120 (rfc6962-bis): public vs. private logs? trans issue tracker
  • Re: [Trans] [trans] #120 (rfc6962-bis): public vs. private logs? trans issue tracker
• [Trans] [trans] #119 (rfc6962-bis): confusing wording about log checking in Introduction trans issue tracker
  • Re: [Trans] [trans] #119 (rfc6962-bis): confusing wording about log checking in Introduction trans issue tracker
  • Re: [Trans] [trans] #119 (rfc6962-bis): confusing wording about log checking in Introduction trans issue tracker
  • Re: [Trans] [trans] #119 (rfc6962-bis): confusing wording about log checking in Introduction trans issue tracker
  • Re: [Trans] [trans] #119 (rfc6962-bis): confusing wording about log checking in Introduction trans issue tracker
• [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem trans issue tracker
• [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" trans issue tracker
  • Re: [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" trans issue tracker
  • Re: [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" Stephen Kent
  • Re: [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" trans issue tracker
  • Re: [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" Stephen Kent
  • Re: [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" Rob Stradling
  • Re: [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" Stephen Kent
  • Re: [Trans] [trans] #117 (rfc6962-bis): log description as "untrusted" trans issue tracker
• [Trans] [trans] #116 (rfc6962-bis): ned definition for mis-issuance trans issue tracker
  • [Trans] Fwd: [trans] #116 (rfc6962-bis): ned definition for mis-issuance Melinda Shore
  • Re: [Trans] Fwd: [trans] #116 (rfc6962-bis): ned definition for mis-issuance Stephen Kent
  • Re: [Trans] [trans] #116 (rfc6962-bis): ned definition for mis-issuance trans issue tracker
  • Re: [Trans] [trans] #116 (rfc6962-bis): ned definition for mis-issuance Stephen Kent
  • Re: [Trans] [trans] #116 (rfc6962-bis): ned definition for mis-issuance Rob Stradling
  • Re: [Trans] [trans] #116 (rfc6962-bis): ned definition for mis-issuance trans issue tracker
• [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
  • Re: [Trans] [trans] #115 (rfc6962-bis): Verify that recommended consistency checking algorithm is correct trans issue tracker
• [Trans] log metadata questions David Mandelberg
  • Re: [Trans] log metadata questions Matt Palmer
• [Trans] add-chain return value Peter Bowen
• [Trans] [trans] #114 (rfc6962-bis): Name the OCSP Stapling TLS extension correctly trans issue tracker
  • Re: [Trans] [trans] #114 (rfc6962-bis): Name the OCSP Stapling TLS extension correctly trans issue tracker
  • Re: [Trans] [trans] #114 (rfc6962-bis): Name the OCSP Stapling TLS extension correctly trans issue tracker
• [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension trans issue tracker
  • Re: [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension trans issue tracker
  • Re: [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension trans issue tracker
  • Re: [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension trans issue tracker
  • Re: [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension trans issue tracker
  • Re: [Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension trans issue tracker
• [Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension trans issue tracker
  • Re: [Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension trans issue tracker
  • Re: [Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension trans issue tracker
  • Re: [Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension trans issue tracker
  • Re: [Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension trans issue tracker
• [Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension trans issue tracker
• [Trans] Milestones changed for trans WG IETF Secretariat
  • [Trans] Milestones changed for trans WG IETF Secretariat
  • [Trans] Milestones changed for trans WG IETF Secretariat
• [Trans] BOF for dnssec transparency Paul Wouters
  • Re: [Trans] BOF for dnssec transparency Paul Wouters
• [Trans] IETF 94 TRANS minutes Draft Salz, Rich
  • Re: [Trans] IETF 94 TRANS minutes Draft Melinda Shore
  • Re: [Trans] IETF 94 TRANS minutes Draft Karen Seo
  • Re: [Trans] IETF 94 TRANS minutes Draft Daniel Kahn Gillmor
• [Trans] Threat model document review Paul Wouters
• [Trans] Upcoming meeting Melinda Shore
  • [Trans] Upcoming meeting Melinda Shore
• [Trans] Draft agenda posted Melinda Shore
• [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Tom Ritter
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Robin Wilton
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Katriel Cohn-Gordon
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Tom Ritter
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Linus Nordberg
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Tom Ritter
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Ben Laurie
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Daniel Kahn Gillmor
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Tom Ritter
  • Re: [Trans] Gossip: Unsticking a client caught with potential evidence of log misbehavior Ben Laurie
• [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-10.txt internet-drafts
• [Trans] I-D Action: draft-ietf-trans-gossip-01.txt internet-drafts
• [Trans] [trans] #110 (rfc6962-bis): Reorganize requirements into appropriate sections trans issue tracker
  • Re: [Trans] [trans] #110 (rfc6962-bis): Reorganize requirements into appropriate sections trans issue tracker
  • Re: [Trans] [trans] #110 (rfc6962-bis): Reorganize requirements into appropriate sections trans issue tracker
• [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior trans issue tracker
  • Re: [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior trans issue tracker
  • Re: [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior Stephen Kent
  • Re: [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior trans issue tracker
  • Re: [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior trans issue tracker
  • Re: [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior trans issue tracker
  • Re: [Trans] [trans] #109 (rfc6962-bis): log shutdown timeline and behavior trans issue tracker
• [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-09.txt internet-drafts
• [Trans] really posted the update this time Stephen Kent
• [Trans] I-D Action: draft-ietf-trans-threat-analysis-03.txt internet-drafts
• [Trans] whoops? Stephen Kent
• [Trans] new version of threat/attack model Stephen Kent
• [Trans] I-D Action: draft-ietf-trans-threat-analysis-02.txt internet-drafts
• [Trans] architecture document Stephen Kent
• [Trans] Please review the attack model draft Melinda Shore
• [Trans] [trans] #108 (rfc6962-bis): TLS session resumption: Server MUST NOT send SCTs trans issue tracker
  • Re: [Trans] [trans] #108 (rfc6962-bis): TLS session resumption: Server MUST NOT send SCTs trans issue tracker
  • Re: [Trans] [trans] #108 (rfc6962-bis): TLS session resumption: Server MUST NOT send SCTs trans issue tracker
  • Re: [Trans] [trans] #108 (rfc6962-bis): TLS session resumption: Server MUST NOT send SCTs trans issue tracker
  • Re: [Trans] [trans] #108 (rfc6962-bis): TLS session resumption: Server MUST NOT send SCTs trans issue tracker
• [Trans] FYI: Certificate Transparency catches Symantec Paul Wouters
  • Re: [Trans] FYI: Certificate Transparency catches Symantec Matt Palmer
• [Trans] [trans] #107 (rfc6962-bis): Struct-ify STH trans issue tracker
  • Re: [Trans] [trans] #107 (rfc6962-bis): Struct-ify STH trans issue tracker
  • Re: [Trans] [trans] #107 (rfc6962-bis): Struct-ify STH trans issue tracker
  • Re: [Trans] [trans] #107 (rfc6962-bis): Struct-ify STH trans issue tracker
• Re: [Trans] [trans] #5 (rfc6962-bis): Add extensions to STH trans issue tracker
  • Re: [Trans] [trans] #5 (rfc6962-bis): Add extensions to STH trans issue tracker
  • Re: [Trans] [trans] #5 (rfc6962-bis): Add extensions to STH trans issue tracker
  • Re: [Trans] [trans] #5 (rfc6962-bis): Add extensions to STH trans issue tracker
• [Trans] Usage of Private Information Retrieval (PIR) in CT? Matt Palmer
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Linus Nordberg
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Rob Stradling
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Stephen Kent
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Rob Stradling
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Karen Seo
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Karen Seo
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Paul Wouters
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Stephen Kent
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Stephen Kent
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Rob Stradling
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Stephen Kent
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Rob Stradling
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Stephen Kent
  • Re: [Trans] Usage of Private Information Retrieval (PIR) in CT? Rob Stradling
• [Trans] Tutorial on how to deploy an internal CT log server? Ronald del Rosario
  • Re: [Trans] Tutorial on how to deploy an internal CT log server? Ronald del Rosario
• [Trans] I-D Action: draft-ietf-trans-gossip-00.txt internet-drafts
• [Trans] Tracking via multiple STHs (was Call for adoption, draft-linus-trans-gossip-ct) Tom Ritter
• [Trans] [trans] #106 (rfc6962-bis): Include LogID in the STH structure (TreeHeadSignature) trans issue tracker
  • Re: [Trans] [trans] #106 (rfc6962-bis): Include LogID in the STH structure (TreeHeadSignature) trans issue tracker
  • Re: [Trans] [trans] #106 (rfc6962-bis): Include LogID in the STH structure (TreeHeadSignature) trans issue tracker
• [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Stephen Kent
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Rob Stradling
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Stephen Kent
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Rob Stradling
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Stephen Kent
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Ben Laurie
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Stephen Kent
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Rob Stradling
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID Stephen Kent
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
  • Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID trans issue tracker
• [Trans] [trans] #104 (rfc6962-bis): Add SCT Inclusion Proof extension trans issue tracker
  • Re: [Trans] [trans] #104 (rfc6962-bis): Add SCT Inclusion Proof extension trans issue tracker
  • Re: [Trans] [trans] #104 (rfc6962-bis): Add SCT Inclusion Proof extension trans issue tracker
  • Re: [Trans] [trans] #104 (rfc6962-bis): Add SCT Inclusion Proof extension trans issue tracker
  • Re: [Trans] [trans] #104 (rfc6962-bis): Add SCT Inclusion Proof extension trans issue tracker
• [Trans] Certificate Transparency Newsletter - August 2015 Adam Eijdenberg
  • Re: [Trans] Certificate Transparency Newsletter - August 2015 Rob Stradling
  • Re: [Trans] Certificate Transparency Newsletter - August 2015 Rob Stradling
  • Re: [Trans] Certificate Transparency Newsletter - August 2015 Tom Ritter
  • Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015 Rob Stradling
  • Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015 Tom Ritter
  • Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015 Rob Stradling
  • Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015 Jeremy Rowley

• Earlier messages
• Later messages