trans  

Messages by Thread

• • Re: [Trans] evaluating an SCT in the absence of the cert's issuer key Linus Nordberg
• [Trans] trans - New Meeting Session Request for IETF 96 "IETF Meeting Session Request Tool"
• [Trans] STHExtension expression Daniel Kahn Gillmor
  • Re: [Trans] STHExtension expression Rob Stradling
• [Trans] IETF 96 planning Melinda Shore
• [Trans] I-D Action: draft-ietf-trans-threat-analysis-05.txt internet-drafts
• [Trans] slight timing whoops Stephen Kent
  • Re: [Trans] revised threat analysis doc David A. Cooper
  • Re: [Trans] slight timing whoops Bryan Ford
  • Re: [Trans] slight timing whoops Stephen Kent
• [Trans] revised threat analysis doc Stephen Kent
• [Trans] Proposal: Allow redaction of exactly one DNS-ID Eran Messeri
  • Re: [Trans] Proposal: Allow redaction of exactly one DNS-ID Andrew Ayer
  • Re: [Trans] Proposal: Allow redaction of exactly one DNS-ID Paul Wouters
• [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-14.txt internet-drafts
• [Trans] Issue with redaction and CN-IDs Rick Andrews
  • Re: [Trans] Issue with redaction and CN-IDs Peter Bowen
  • Re: [Trans] Issue with redaction and CN-IDs Rick Andrews
  • Re: [Trans] Issue with redaction and CN-IDs Peter Bowen
  • Re: [Trans] Issue with redaction and CN-IDs Rob Stradling
  • Re: [Trans] Issue with redaction and CN-IDs Stephen Kent
  • Re: [Trans] Issue with redaction and CN-IDs Salz, Rich
  • Re: [Trans] Issue with redaction and CN-IDs Peter Bowen
  • Re: [Trans] Issue with redaction and CN-IDs Rob Stradling
  • Re: [Trans] Issue with redaction and CN-IDs Peter Bowen
  • Re: [Trans] Issue with redaction and CN-IDs Rob Stradling
• [Trans] revisions to Section 3.3 and 3.4 Stephen Kent
  • Re: [Trans] revisions to Section 3.3 and 3.4 Paul Wouters
• [Trans] Fwd: [Crosspost/FYI] Name redaction in CT logs Paul Wouters
• [Trans] Fwd: Remote Participation for IETF 95: Meetecho Details Melinda Shore
• [Trans] Open issues update Melinda Shore
  • Re: [Trans] Open issues update Salz, Rich
• Re: [Trans] Why "Poison Extension" disappeared in rfc6962-bis? Yusuke OSUMI
  • Re: [Trans] Why "Poison Extension" disappeared in rfc6962-bis? Ben Laurie
  • Re: [Trans] Why "Poison Extension" disappeared in rfc6962-bis? Yusuke OSUMI
  • Re: [Trans] Why "Poison Extension" disappeared in rfc6962-bis? Yusuke OSUMI
• Re: [Trans] [trans] #111 (to-be-decided): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (to-be-decided): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (to-be-decided): Consider using the cached-info TLS extension trans issue tracker
  • Re: [Trans] [trans] #111 (to-be-decided): Consider using the cached-info TLS extension trans issue tracker
• [Trans] proposed text to address Bryan's concerns Stephen Kent
• [Trans] updated Section 3.3 Stephen Kent
  • Re: [Trans] updated Section 3.3 Paul Wouters
  • Re: [Trans] updated Section 3.3 Stephen Kent
  • Re: [Trans] updated Section 3.3 Paul Wouters
  • Re: [Trans] updated Section 3.3 Stephen Kent
  • Re: [Trans] updated Section 3.3 Paul Wouters
  • Re: [Trans] updated Section 3.3 Stephen Kent
  • Re: [Trans] updated Section 3.3 Stephen Kent
  • Re: [Trans] updated Section 3.3 Stephen Kent
  • Re: [Trans] updated Section 3.3 Ben Laurie
• [Trans] I-D Action: draft-ietf-trans-gossip-02.txt internet-drafts
• [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-13.txt internet-drafts
• Re: [Trans] Co-existence of V1 and V2 embedded SCTs in certificates Rob Stradling
  • Re: [Trans] Co-existence of V1 and V2 embedded SCTs in certificates Eran Messeri
  • Re: [Trans] Co-existence of V1 and V2 embedded SCTs in certificates Barreira Iglesias, Iñigo
• [Trans] revised text for colluding, malicious CAs Stephen Kent
• [Trans] [trans] #157 (rfc6962-bis): Conflate Version and TransType trans issue tracker
  • Re: [Trans] [trans] #157 (rfc6962-bis): Conflate Version and TransType trans issue tracker
  • Re: [Trans] [trans] #157 (rfc6962-bis): Conflate Version and TransType trans issue tracker
  • Re: [Trans] [trans] #157 (rfc6962-bis): Conflate Version and TransType trans issue tracker
  • Re: [Trans] [trans] #157 (rfc6962-bis): Conflate Version and TransType trans issue tracker
• Re: [Trans] [trans] #156 (rfc6962-bis): Can inclusion proofs properly substitute SCTs? trans issue tracker
  • Re: [Trans] [trans] #156 (rfc6962-bis): Can inclusion proofs properly substitute SCTs? trans issue tracker
  • Re: [Trans] [trans] #156 (rfc6962-bis): Can inclusion proofs properly substitute SCTs? trans issue tracker
  • Re: [Trans] [trans] #156 (rfc6962-bis): Can inclusion proofs properly substitute SCTs? trans issue tracker
  • Re: [Trans] [trans] #156 (rfc6962-bis): Can inclusion proofs properly substitute SCTs? trans issue tracker
  • Re: [Trans] [trans] #156 (rfc6962-bis): Can inclusion proofs properly substitute SCTs? trans issue tracker
• [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Salz, Rich
  • Re: [Trans] text to address DKG's conspiring CAs attack Melinda Shore
  • Re: [Trans] text to address DKG's conspiring CAs attack Salz, Rich
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Ben Laurie
  • Re: [Trans] text to address DKG's conspiring CAs attack Rob Stradling
  • Re: [Trans] text to address DKG's conspiring CAs attack Ben Laurie
  • Re: [Trans] text to address DKG's conspiring CAs attack Rob Stradling
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Rob Stradling
  • Re: [Trans] text to address DKG's conspiring CAs attack Ben Laurie
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Rob Stradling
  • Re: [Trans] text to address DKG's conspiring CAs attack Salz, Rich
  • Re: [Trans] text to address DKG's conspiring CAs attack Rob Stradling
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Ben Laurie
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack Tom Ritter
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Rob Stradling
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Stephen Kent
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Melinda Shore
  • Re: [Trans] text to address DKG's conspiring CAs attack Melinda Shore
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Watson Ladd
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Melinda Shore
  • Re: [Trans] text to address DKG's conspiring CAs attack Ben Laurie
  • Re: [Trans] text to address DKG's conspiring CAs attack Ben Laurie
  • Re: [Trans] text to address DKG's conspiring CAs attack Carl Wallace
  • Re: [Trans] text to address DKG's conspiring CAs attack Carl Wallace
  • Re: [Trans] text to address DKG's conspiring CAs attack Carl Wallace
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
  • Re: [Trans] text to address DKG's conspiring CAs attack Ben Laurie
  • Re: [Trans] text to address DKG's conspiring CAs attack David A. Cooper
• [Trans] trans - Requested session has been scheduled for IETF 95 "IETF Secretariat"
• [Trans] [trans] #155 (rfc6962-bis): Describe how to match SCTs to certificates trans issue tracker
  • Re: [Trans] [trans] #155 (rfc6962-bis): Describe how to match SCTs to certificates trans issue tracker
• [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Paul Wouters
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Salz, Rich
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Tom Ritter
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Stephen Kent
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Bryan Ford
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Ben Laurie
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Bryan Ford
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Ben Laurie
  • Re: [Trans] [draft2] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Stephen Kent
  • Re: [Trans] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Paul Wouters
  • Re: [Trans] Working Group Last Call for draft-ietf-trans-threat-analysis (fwd) Stephen Kent
• [Trans] DNS for CT Ben Laurie
  • Re: [Trans] DNS for CT Paul Hoffman
• [Trans] can CT defend against dual CA compromise? Daniel Kahn Gillmor
  • Re: [Trans] can CT defend against dual CA compromise? Rob Stradling
  • Re: [Trans] can CT defend against dual CA compromise? Tom Ritter
  • Re: [Trans] can CT defend against dual CA compromise? Rob Stradling
  • Re: [Trans] can CT defend against dual CA compromise? Rob Stradling
  • Re: [Trans] can CT defend against dual CA compromise? Tom Ritter
  • Re: [Trans] can CT defend against dual CA compromise? Daniel Kahn Gillmor
  • Re: [Trans] can CT defend against dual CA compromise? Tom Ritter
  • Re: [Trans] can CT defend against dual CA compromise? Daniel Kahn Gillmor
• [Trans] [trans] #154 (rfc6962-bis): CSR extension to convey a certificate subscriber's CT preferences to the CA trans issue tracker
  • Re: [Trans] [trans] #154 (rfc6962-bis): CSR extension to convey a certificate subscriber's CT preferences to the CA trans issue tracker
  • Re: [Trans] [trans] #154 (rfc6962-bis): CSR extension to convey a certificate subscriber's CT preferences to the CA trans issue tracker
  • Re: [Trans] [trans] #154 (rfc6962-bis): CSR extension to convey a certificate subscriber's CT preferences to the CA trans issue tracker
  • Re: [Trans] [trans] #154 (to-be-decided): CSR extension to convey a certificate subscriber's CT preferences to the CA trans issue tracker
• [Trans] Oh... Rob Stradling
  • Re: [Trans] Oh... Stephen Farrell
  • Re: [Trans] Oh... Rob Stradling
  • Re: [Trans] Oh... Russ Housley
• [Trans] Looking for feedback on open issue Melinda Shore
  • Re: [Trans] Looking for feedback on open issue Stephen Kent
  • Re: [Trans] Looking for feedback on open issue Stephen Kent
• [Trans] I-D Action: draft-ietf-trans-threat-analysis-04.txt internet-drafts
• [Trans] [trans] #153 (rfc6962-bis): Finish documenting support for RFC6962 (v1) structures in TransInfo trans issue tracker
  • Re: [Trans] [trans] #153 (rfc6962-bis): Finish documenting support for RFC6962 (v1) structures in TransInfo trans issue tracker
  • Re: [Trans] [trans] #153 (rfc6962-bis): Finish documenting support for RFC6962 (v1) structures in TransInfo trans issue tracker
  • Re: [Trans] [trans] #153 (rfc6962-bis): Finish documenting support for RFC6962 (v1) structures in TransInfo trans issue tracker
  • Re: [Trans] [trans] #153 (rfc6962-bis): Finish documenting support for RFC6962 (v1) structures in TransInfo trans issue tracker
• Re: [Trans] [trans] #57 (rfc6962-bis): Clients MUST NOT match the redaction label with a "*" label trans issue tracker
  • Re: [Trans] [trans] #57 (rfc6962-bis): Clients MUST NOT match the redaction label with a "*" label trans issue tracker
  • Re: [Trans] [trans] #57 (rfc6962-bis): Clients MUST NOT match the redaction label with a "*" label trans issue tracker
  • Re: [Trans] [trans] #57 (rfc6962-bis): Clients MUST NOT match the redaction label with a "*" label trans issue tracker
  • Re: [Trans] [trans] #57 (rfc6962-bis): Clients MUST NOT match the redaction label with a "*" label trans issue tracker
• Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem trans issue tracker
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem trans issue tracker
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem trans issue tracker
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem trans issue tracker
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem trans issue tracker
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem trans issue tracker
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem Stephen Kent
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem Stephen Kent
  • Re: [Trans] [trans] #118 (rfc6962-bis): Monitor function description problem Stephen Kent
• Re: [Trans] [trans] #87 (rfc6962-bis): Add reference to threat analysis document trans issue tracker
  • Re: [Trans] [trans] #87 (rfc6962-bis): Add reference to threat analysis document trans issue tracker
  • Re: [Trans] [trans] #87 (rfc6962-bis): Add reference to threat analysis document trans issue tracker
• [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-12.txt internet-drafts
• Re: [Trans] [trans] #71 (threat-analysis): Section 1 does not define mis-issuance trans issue tracker
• Re: [Trans] [trans] #102 (rfc6962-bis): "root" should be "trust anchor" trans issue tracker
  • Re: [Trans] [trans] #102 (rfc6962-bis): "root" should be "trust anchor" trans issue tracker
  • Re: [Trans] [trans] #102 (rfc6962-bis): "root" should be "trust anchor" trans issue tracker
  • Re: [Trans] [trans] #102 (rfc6962-bis): "root" should be "trust anchor" trans issue tracker
• Re: [Trans] Review of the architecture document (draft 1) Stephen Kent
  • Re: [Trans] Review of the architecture document (draft 1) Stephen Kent
• [Trans] awaiting threat doc editorial comments Stephen Kent
• [Trans] trans - New Meeting Session Request for IETF 95 "IETF Meeting Session Request Tool"
• [Trans] proposed CA/Subject changes Karen Seo
  • Re: [Trans] proposed CA/Subject changes Melinda Shore
  • Re: [Trans] proposed CA/Subject changes Salz, Rich
  • Re: [Trans] proposed CA/Subject changes Rob Stradling
  • Re: [Trans] proposed CA/Subject changes Karen Seo
  • Re: [Trans] proposed CA/Subject changes Melinda Shore
  • Re: [Trans] proposed CA/Subject changes Stephen Farrell
  • Re: [Trans] proposed CA/Subject changes Karen Seo
  • Re: [Trans] proposed CA/Subject changes Melinda Shore
  • Re: [Trans] proposed CA/Subject changes Eran Messeri
  • Re: [Trans] proposed CA/Subject changes Stephen Kent
  • Re: [Trans] proposed CA/Subject changes Rob Stradling
  • Re: [Trans] proposed CA/Subject changes Stephen Kent

• Earlier messages
• Later messages