trans  

Messages by Date

• 2015/05/31 [Trans] Work on dnssec logging Melinda Shore
• 2015/05/29 [Trans] LogEntryType for SCTs in case of TLS extension? Ondrej Mikle
• 2015/05/24 Re: [Trans] Threat Analysis for CT adopted by the working group Melinda Shore
• 2015/05/24 Re: [Trans] Threat Analysis for CT adopted by the working group Karen Seo
• 2015/05/21 Re: [Trans] Empty extra_data Linus Nordberg
• 2015/05/21 [Trans] [trans] #84 (rfc6962-bis): Clarify that root certs have empty certificate_chain trans issue tracker
• 2015/05/18 Re: [Trans] question: short lived certs Robin Wilton
• 2015/05/18 Re: [Trans] question: short lived certs Ben Laurie
• 2015/05/18 Re: [Trans] question: short lived certs Eran Messeri
• 2015/05/18 [Trans] question: short lived certs Stephen Farrell
• 2015/05/18 Re: [Trans] [trans] #82 (rfc6962-bis): Add a way to get the SCTs for entries returned by get-entries trans issue tracker
• 2015/05/18 Re: [Trans] [trans] #82 (rfc6962-bis): Add a way to get the SCTs for entries returned by get-entries (was: add integrity validation to get-entries (and fetching SCTs?)) trans issue tracker
• 2015/05/18 Re: [Trans] [trans] #82 (rfc6962-bis): add integrity validation to get-entries (and fetching SCTs?) trans issue tracker
• 2015/05/13 Re: [Trans] Empty extra_data Linus Nordberg
• 2015/05/12 Re: [Trans] Empty extra_data Paul Wouters
• 2015/05/12 Re: [Trans] Empty extra_data Linus Nordberg
• 2015/05/12 Re: [Trans] Empty extra_data Rob Stradling
• 2015/05/12 [Trans] Empty extra_data Linus Nordberg
• 2015/04/25 Re: [Trans] Threat Analysis for CT adopted by the working group Karen Seo
• 2015/04/24 Re: [Trans] Threat Analysis for CT adopted by the working group Melinda Shore
• 2015/04/24 Re: [Trans] Threat Analysis for CT adopted by the working group Karen Seo
• 2015/04/22 Re: [Trans] [pkix] Certificate Transparency and user agent warnings Jeffrey Walton
• 2015/04/22 Re: [Trans] [pkix] Certificate Transparency and user agent warnings Rob Stradling
• 2015/04/12 [Trans] Threat Analysis for CT adopted by the working group Paul Wouters
• 2015/04/03 Re: [Trans] Open source CT log implementations Leif Johansson
• 2015/04/02 Re: [Trans] Open source CT log implementations Tony Arcieri
• 2015/04/02 Re: [Trans] Open source CT log implementations Tomas Gustavsson
• 2015/04/02 Re: [Trans] Open source CT log implementations Ben Laurie
• 2015/04/02 [Trans] Open source CT log implementations Tony Arcieri
• 2015/04/01 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Warren Kumari
• 2015/04/01 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Melinda Shore
• 2015/04/01 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Karen Seo
• 2015/04/01 [Trans] Fwd: Date change for CARIS submissions Melinda Shore
• 2015/04/01 Re: [Trans] [trans] #82 (rfc6962-bis): add integrity validation to get-entries (and fetching SCTs?) trans issue tracker
• 2015/04/01 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Karen Seo
• 2015/04/01 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Rick Andrews
• 2015/04/01 Re: [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSA Watson Ladd
• 2015/04/01 Re: [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSA Daniel Kahn Gillmor
• 2015/04/01 Re: [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSA Russ Housley
• 2015/04/01 [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSA trans issue tracker
• 2015/04/01 Re: [Trans] [trans] #82 (rfc6962-bis): add integrity validation to get-entries (and fetching SCTs?) trans issue tracker
• 2015/04/01 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Linus Nordberg
• 2015/03/31 Re: [Trans] Poll for adoption of working group draft on threat analysisfor CT Stephen Kent
• 2015/03/31 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Daniel Kahn Gillmor
• 2015/03/31 [Trans] [trans] #82 (client-behavior): add integrity validation to get-entries (and fetching SCTs?) trans issue tracker
• 2015/03/31 Re: [Trans] Poll for adoption of working group draft on threat analysisfor CT Salz, Rich
• 2015/03/31 Re: [Trans] [trans] #79 (rfc6962-bis): Precertificate signature must be over something other than just the TBSCertificate trans issue tracker
• 2015/03/31 Re: [Trans] Poll for adoption of working group draft on threat analysisfor CT Rob Stradling
• 2015/03/31 Re: [Trans] Use of private OIDs in WG (standard-track) documents Rob Stradling
• 2015/03/31 [Trans] [trans] #81 (rfc6962-bis): OIDs and IANA Considerations trans issue tracker
• 2015/03/31 [Trans] [trans] #80 (client-behavior): Re-introduce the issuer key hash into the Precertificate trans issue tracker
• 2015/03/30 [Trans] Minutes uploaded Melinda Shore
• 2015/03/30 Re: [Trans] Use of private OIDs in WG (standard-track) documents Melinda Shore
• 2015/03/30 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Warren Kumari
• 2015/03/30 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Salz, Rich
• 2015/03/30 Re: [Trans] Use of Private OIDs in WG document (Re: [pkix] a question of cert (and OCSP) extension syntax) Nico Williams
• 2015/03/30 Re: [Trans] Use of private OIDs in WG document Russ Housley
• 2015/03/30 Re: [Trans] [trans] #79 (rfc6962-bis): Precertificate signature must be over something other than just the TBSCertificate Erwann Abalea
• 2015/03/30 Re: [Trans] Use of private OIDs in WG document Rob Stradling
• 2015/03/29 Re: [Trans] Use of private OIDs in WG document Russ Housley
• 2015/03/28 Re: [Trans] Use of Private OIDs in WG document (Re: [pkix] a question of cert (and OCSP) extension syntax) Melinda Shore
• 2015/03/28 [Trans] Use of Private OIDs in WG document (Re: [pkix] a question of cert (and OCSP) extension syntax) Massimiliano Pala
• 2015/03/28 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Leif Johansson
• 2015/03/27 [Trans] Use of private OIDs in WG document Massimiliano Pala
• 2015/03/27 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Salz, Rich
• 2015/03/27 Re: [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] Tom Ritter
• 2015/03/27 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Massimiliano Pala
• 2015/03/27 Re: [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] Tao Effect
• 2015/03/27 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Melinda Shore
• 2015/03/27 Re: [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] Tao Effect
• 2015/03/27 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Massimiliano Pala
• 2015/03/27 Re: [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] paul
• 2015/03/27 Re: [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] Tao Effect
• 2015/03/27 Re: [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] Paul Wouters
• 2015/03/27 Re: [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] Dmitry Belyavsky
• 2015/03/27 [Trans] Question regarding new gossip protocols [Was: Certificate transparency on blockchains] Tao Effect
• 2015/03/27 Re: [Trans] [trans] #79 (rfc6962-bis): Precertificate signature must be over something other than just the TBSCertificate trans issue tracker
• 2015/03/27 Re: [Trans] [trans] #79 (rfc6962-bis): Precertificate signature must be over something other than just the TBSCertificate trans issue tracker
• 2015/03/27 [Trans] [trans] #79 (rfc6962-bis): Precertificate signature must be over something other than just the TBSCertificate trans issue tracker
• 2015/03/27 Re: [Trans] AIA/cRL for logged certificates Rob Stradling
• 2015/03/27 Re: [Trans] AIA/cRL for logged certificates Carl Wallace
• 2015/03/27 Re: [Trans] [trans] #4 (rfc6962-bis): Should we sign TBS for Certificates? trans issue tracker
• 2015/03/27 Re: [Trans] [trans] #4 (rfc6962-bis): Should we sign TBS for Certificates? trans issue tracker
• 2015/03/27 Re: [Trans] [Cryptography] Certificate transparency on blockchains Tao Effect
• 2015/03/26 Re: [Trans] [Cryptography] Certificate transparency on blockchains Tom Ritter
• 2015/03/26 Re: [Trans] draft-linus-trans-gossip-ct-01 doesn't work Tom Ritter
• 2015/03/26 Re: [Trans] draft-linus-trans-gossip-ct-01 doesn't work Nico Williams
• 2015/03/26 Re: [Trans] draft-linus-trans-gossip-ct-01 doesn't work Paul Wouters
• 2015/03/26 [Trans] draft-linus-trans-gossip-ct-01 doesn't work Watson Ladd
• 2015/03/25 Re: [Trans] IETF 92 Meeting minutes Salz, Rich
• 2015/03/25 Re: [Trans] IETF 92 Meeting minutes Stephen Kent
• 2015/03/25 Re: [Trans] draft-linus-trans-gossip-ct-01: gossiping STHs Tom Ritter
• 2015/03/24 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Linus Nordberg
• 2015/03/24 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Benjamin Kaduk
• 2015/03/24 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Benjamin Kaduk
• 2015/03/24 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Benjamin Kaduk
• 2015/03/24 Re: [Trans] IETF 92 Meeting minutes Melinda Shore
• 2015/03/24 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Linus Nordberg
• 2015/03/24 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Linus Nordberg
• 2015/03/23 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Leif Johansson
• 2015/03/23 Re: [Trans] Poll for adoption of working group draft on threat analysis for CT Karen Seo
• 2015/03/23 [Trans] Poll for adoption of working group draft on threat analysis for CT Melinda Shore
• 2015/03/23 [Trans] IETF 92 Meeting minutes Salz, Rich
• 2015/03/23 Re: [Trans] [trans] #58 (rfc6962-bis): Limit the number of STH's allowed to be published per time unit (was: Stipulate a maximum number of STH's published per time unit) trans issue tracker
• 2015/03/23 Re: [Trans] [trans] #58 (rfc6962-bis): Stipulate a maximum number of STH's published per time unit (was: Maximise number of STH's published per time unit) trans issue tracker
• 2015/03/23 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Benjamin Kaduk
• 2015/03/23 Re: [Trans] comments on draft-linus-trans-gossip-ct-01 Benjamin Kaduk
• 2015/03/23 Re: [Trans] comments on draft-linux-trans-gossip-ct-01 Linus Nordberg
• 2015/03/23 Re: [Trans] comments on draft-linux-trans-gossip-ct-01 Linus Nordberg
• 2015/03/22 Re: [Trans] comments on draft-linux-trans-gossip-ct-01 Tom Ritter
• 2015/03/22 [Trans] comments on draft-ietf-trans-rfc6962-bis-07 Benjamin Kaduk
• 2015/03/22 [Trans] comments on draft-zhang-trans-ct-binary-codes-01 Benjamin Kaduk
• 2015/03/22 [Trans] On version expectations of trans participants Benjamin Kaduk
• 2015/03/22 [Trans] comments on draft-linux-trans-gossip-ct-01 Benjamin Kaduk
• 2015/03/22 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Russ Housley
• 2015/03/21 [Trans] Slides, please! Melinda Shore
• 2015/03/20 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Melinda Shore
• 2015/03/20 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Stephen Kent
• 2015/03/20 [Trans] [trans] #78 (client-behavior): algorithm agility discussion is inadequate trans issue tracker
• 2015/03/20 [Trans] [trans] #77 (client-behavior): normative client behavior specified in Section 5 trans issue tracker
• 2015/03/20 [Trans] [trans] #76 (client-behavior): Normative client behavior specified in Section 3.4 trans issue tracker
• 2015/03/20 [Trans] [trans] #75 (client-behavior): run on sentence in section 3 trans issue tracker
• 2015/03/20 [Trans] [trans] #74 (client-behavior): normative statement of TLS client behavior in Section 3 trans issue tracker
• 2015/03/20 [Trans] [trans] #73 (client-behavior): Section 3 text re log cert validation is ambiguous trans issue tracker
• 2015/03/20 [Trans] [trans] #72 (client-behavior): Section 2.1.4 cites specific algorithms trans issue tracker
• 2015/03/20 [Trans] [trans] #71 (client-behavior): Section 1 does not define mis-issuance trans issue tracker
• 2015/03/20 [Trans] Clarification on Precertificate Signing Certificates Linus Nordberg
• 2015/03/17 Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax Manger, James
• 2015/03/16 [Trans] Follow-up on closing the SCT encoding issue Melinda Shore
• 2015/03/16 Re: [Trans] One, not three gossip drafts Melinda Shore
• 2015/03/16 [Trans] One, not three gossip drafts (was: Agenda uploaded) Linus Nordberg
• 2015/03/16 [Trans] Agenda uploaded Melinda Shore
• 2015/03/16 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Stephen Kent
• 2015/03/16 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Russ Housley
• 2015/03/16 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Nico Williams
• 2015/03/16 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Rob Stradling
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Paul Wouters
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Nico Williams
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Erwann Abalea
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Stephen Farrell
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Rob Stradling
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Rob Stradling
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Russ Housley
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Stephen Farrell
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Russ Housley
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Rob Stradling
• 2015/03/13 Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Stephen Farrell
• 2015/03/13 [Trans] Bad Technical Decision: Closing out the SCT encoding discussion Russ Housley
• 2015/03/12 Re: [Trans] [trans] #24 (rfc6962-bis): Add a section about log metadata trans issue tracker
• 2015/03/12 [Trans] Closing out the SCT encoding discussion Melinda Shore
• 2015/03/12 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Stephen Farrell
• 2015/03/12 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Stephen Kent
• 2015/03/12 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Stephen Kent
• 2015/03/12 Re: [Trans] changes to attack analysis Stephen Kent
• 2015/03/12 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Stephen Farrell
• 2015/03/12 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Rob Stradling
• 2015/03/12 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Stephen Kent
• 2015/03/11 Re: [Trans] [trans] #34 (rfc6962-bis): use of RFC 5246 syntax to define the SCT Paul Wouters
• 2015/03/11 Re: [Trans] changes to attack analysis Stephen Kent
• 2015/03/10 Re: [Trans] draft-linus-trans-gossip-ct-01 Melinda Shore
• 2015/03/09 Re: [Trans] draft-linus-trans-gossip-ct-01 Daniel Kahn Gillmor
• 2015/03/09 [Trans] draft-linus-trans-gossip-ct-01 Linus Nordberg
• 2015/03/09 Re: [Trans] changes to attack analysis Rob Stradling
• 2015/03/09 Re: [Trans] [trans] #14 (rfc6962-bis): Clarify ASN.1 encoding trans issue tracker
• 2015/03/09 Re: [Trans] changes to attack analysis Stephen Kent
• 2015/03/09 [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-07.txt internet-drafts
• 2015/03/09 [Trans] I-D Action: draft-ietf-trans-rfc6962-bis-06.txt internet-drafts
• 2015/03/09 Re: [Trans] [trans] #62 (rfc6962-bis): change title for section 1 trans issue tracker
• 2015/03/09 Re: [Trans] [trans] #61 (rfc6962-bis): Precertificates are not proper nouns trans issue tracker
• 2015/03/09 Re: [Trans] [trans] #62 (rfc6962-bis): change title for section 1 trans issue tracker
• 2015/03/09 Re: [Trans] [trans] #61 (rfc6962-bis): Precertificates are not proper nouns trans issue tracker
• 2015/03/09 Re: [Trans] [trans] #61 (rfc6962-bis): Precertificates are not proper nouns trans issue tracker
• 2015/03/06 Re: [Trans] changes to attack analysis Ben Laurie
• 2015/03/06 Re: [Trans] [trans] #60 (rfc6962-bis): The number of redacted labels should be revealed in the Precertificate trans issue tracker
• 2015/03/06 Re: [Trans] [trans] #67 (rfc6962-bis): no specification of how a log advertises the max cert chain length it will accept trans issue tracker
• 2015/03/06 Re: [Trans] [trans] #67 (rfc6962-bis): no specification of how a log advertises the max cert chain length it will accept trans issue tracker
• 2015/03/06 [Trans] [trans] #68 (client-behavior): specification of sha-256 for the SCT trans issue tracker
• 2015/03/06 Re: [Trans] comments on -05 (Abstract, Section 1 and Section 2) Ben Laurie
• 2015/03/06 Re: [Trans] changes to attack analysis Ben Laurie
• 2015/03/06 [Trans] comments on -05 (Sections 3.5 + 3.6) Stephen Kent
• 2015/03/06 [Trans] [trans] #70 (client-behavior): STH spec needs to define top-level extension syntax trans issue tracker
• 2015/03/06 [Trans] comments on -05 (Sections 3.3, 3.4 and 3.4.1) Stephen Kent
• 2015/03/06 [Trans] comments on -05 (Section 3.1) Stephen Kent
• 2015/03/06 Re: [Trans] changes to attack analysis Stephen Kent
• 2015/03/06 Re: [Trans] comments on -05 (Abstract, Section 1 and Section 2) Stephen Kent
• 2015/03/06 [Trans] [trans] #69 (client-behavior): old data name (sha256_root_hash) in 3.6 trans issue tracker
• 2015/03/06 [Trans] [trans] #66 (client-behavior): revise the description of what logs MAY do re cert syntax checking trans issue tracker
• 2015/03/06 [Trans] [trans] #67 (rfc6962-bis): no specification of how a log advertises the max cert chain length it will accept trans issue tracker
• 2015/03/06 [Trans] [trans] #65 (client-behavior): remove section 5.4 and reference to "Auditor" in section 3 trans issue tracker
• 2015/03/06 [Trans] [trans] #63 (client-behavior): remove all normative references to client behavior trans issue tracker
• 2015/03/06 [Trans] [trans] #64 (client-behavior): remove specification of signature and hash lags from section 2 trans issue tracker
• 2015/03/06 [Trans] [trans] #62 (rfc6962-bis): change title for section 1 trans issue tracker
• 2015/03/06 Re: [Trans] comments on -05 (Abstract, Section 1 and Section 2) Ben Laurie
• 2015/03/06 Re: [Trans] [trans] #59 (rfc6962-bis): Clarify STH versioning Ben Laurie
• 2015/03/06 Re: [Trans] [trans] #60 (rfc6962-bis): The number of redacted labels should be revealed in the Precertificate trans issue tracker
• 2015/03/06 Re: [Trans] [trans] #24 (rfc6962-bis): Add a section about log metadata trans issue tracker
• 2015/03/06 Re: [Trans] [trans] #8 (client-privacy): Need a way to obtain Merkle proofs for a batch for certificates around the SCT timestamp trans issue tracker
• 2015/03/05 [Trans] comments on -05 (Abstract, Section 1 and Section 2) Stephen Kent
• 2015/03/05 [Trans] comments on -05 (Section 3) Stephen Kent
• 2015/03/05 Re: [Trans] [trans] #59 (rfc6962-bis): Clarify STH versioning Stephen Kent

• Earlier messages
• Later messages