Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4
Stephen Kent
2015-11-10
trans
/arch/msg/trans/apgU3SjeaLbn7NLvIkVc9dgIjsM/
2114062
1646673
Re: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant neededRe: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant needed
Stephen Kent
2015-11-10
trans
/arch/msg/trans/a2Xae3i0CEDQ7fqnwdQyHclRlHk/
2114061
1646612
Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4
Stephen Kent
2015-11-10
trans
/arch/msg/trans/tvZa7tLlxS5asE_U09gByHBRhus/
2114057
1646673
Re: [Trans] add-chain return valueRe: [Trans] add-chain return value
Adam Eijdenberg
2015-11-09
trans
/arch/msg/trans/hivBLPSB3Ps5rHsFwSH9efmOS9M/
2113584
1646567
[Trans] add-chain return value[Trans] add-chain return value
Peter Bowen
2015-11-08
trans
/arch/msg/trans/LN1uYAq0ySXuzsWQxM3NDvTEAUQ/
2113125
1646567
Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015
Melinda Shore
2015-11-05
trans
/arch/msg/trans/fiOiDtgncLpY8z-5fN256icc4zU/
2110867
1646605
Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015
Tom Ritter
2015-11-04
trans
/arch/msg/trans/jmW5sq8oKiy1vk8FkZAWaNHUawk/
2110447
1646605
Re: [Trans] [trans] #104 (rfc6962-bis): Add SCT Inclusion Proof extensionRe: [Trans] [trans] #104 (rfc6962-bis): Add SCT Inclusion Proof extension
trans issue tracker
2015-11-04
trans
/arch/msg/trans/10YTz4k3slFvnKtpWrezXpCuCVY/
2110392
1646604
[Trans] [trans] #114 (rfc6962-bis): Name the OCSP Stapling TLS extension correctly[Trans] [trans] #114 (rfc6962-bis): Name the OCSP Stapling TLS extension correctly
trans issue tracker
2015-11-04
trans
/arch/msg/trans/MJbuMzGJQj692NB04dZQDdriNd8/
2110349
1646568
Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015
Jeremy Rowley
2015-11-04
trans
/arch/msg/trans/rL3oV33fX4TlYPfbv2f7jxexI6I/
2110348
1646605
Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015
Jeremy Rowley
2015-11-04
trans
/arch/msg/trans/qBIhhRerAIhjJMdVzEfaVeVhEZo/
2110347
1646605
Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015Re: [Trans] [ct-policy] Re: Certificate Transparency Newsletter - August 2015
Rob Stradling
2015-11-04
trans
/arch/msg/trans/zoHYwwGjVOJGVNuwuTokAD_FfpI/
2110338
1646605
[Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension[Trans] [trans] #113 (rfc6962-bis): Add advice about the tls-feature TLS extension
trans issue tracker
2015-11-04
trans
/arch/msg/trans/Gg0A6H8zqhDiXGKyB4FDoRd_zD0/
2110336
1646569
[Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension[Trans] [trans] #112 (rfc6962-bis): Consider permitting the status_request_v2 TLS extension
trans issue tracker
2015-11-03
trans
/arch/msg/trans/0k2AcnWr1rewzSKm1oczhUekOeE/
2109346
1646570
[Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension[Trans] [trans] #111 (rfc6962-bis): Consider using the cached-info TLS extension
trans issue tracker
2015-11-03
trans
/arch/msg/trans/1H8kr34CGtJZBq1tjV3qKB1-9CQ/
2109323
1646571
Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4
trans issue tracker
2015-11-03
trans
/arch/msg/trans/ZUmq4MFEUH4iMTpzHUtrkSQrSkw/
2109233
1646673
Re: [Trans] [trans] #102 (rfc6962-bis): "root" should be "trust anchor"Re: [Trans] [trans] #102 (rfc6962-bis): "root" should be "trust anchor"
trans issue tracker
2015-11-03
trans
/arch/msg/trans/xVTGmrxkcuIYQRANsV9tafuEMDA/
2109218
1646608
Re: [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSARe: [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSA
trans issue tracker
2015-11-03
trans
/arch/msg/trans/Vsm-XC9j5N3rbD_EP9nuAZbC9HU/
2109171
1646653
Re: [Trans] [trans] #81 (rfc6962-bis): OIDs and IANA ConsiderationsRe: [Trans] [trans] #81 (rfc6962-bis): OIDs and IANA Considerations
trans issue tracker
2015-11-03
trans
/arch/msg/trans/ADUm3hUxEVtEvM8fakAi-fE3npU/
2109163
1646655
Re: [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSARe: [Trans] [trans] #83 (rfc6962-bis): CT should mandate the use of deterministic ECDSA
trans issue tracker
2015-11-03
trans
/arch/msg/trans/Yztql0JCJ3-Tg_w9xrdtFmIQryo/
2108604
1646653
Re: [Trans] [trans] #81 (rfc6962-bis): OIDs and IANA ConsiderationsRe: [Trans] [trans] #81 (rfc6962-bis): OIDs and IANA Considerations
trans issue tracker
2015-11-03
trans
/arch/msg/trans/b_x3oe1ouf8gH30Y5C9_adATv9E/
2108587
1646655
Re: [Trans] [trans] #78 (rfc6962-bis): algorithm agility discussion is inadequateRe: [Trans] [trans] #78 (rfc6962-bis): algorithm agility discussion is inadequate
trans issue tracker
2015-11-03
trans
/arch/msg/trans/l5Cj6IFsvYFhY_63Hwag2ySGpv4/
2108583
1646671
Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4Re: [Trans] [trans] #76 (rfc6962-bis): Normative client behavior specified in Section 3.4
trans issue tracker
2015-11-03
trans
/arch/msg/trans/i_8BpMURSuy0JNd9H_ZaUlxLOd8/
2108572
1646673
Re: [Trans] [trans] #64 (rfc6962-bis): remove specification of signature and hash lags from section 2Re: [Trans] [trans] #64 (rfc6962-bis): remove specification of signature and hash lags from section 2
trans issue tracker
2015-11-03
trans
/arch/msg/trans/-YQEWjNkAwPiNJmx1hz7_fvukyQ/
2108565
1646697
Re: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant neededRe: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant needed
trans issue tracker
2015-11-03
trans
/arch/msg/trans/OQY1nkfo-0QJP604KRuDIyRCcnI/
2108547
1646612
Re: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant neededRe: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant needed
trans issue tracker
2015-11-03
trans
/arch/msg/trans/zg6UqYUeCuM7Nb3LGqyitps7jHg/
2108542
1646612
Re: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant neededRe: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant needed
trans issue tracker
2015-11-03
trans
/arch/msg/trans/vCCt2GNp25CazwAmoIanDbh5ICM/
2108541
1646612
Re: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant neededRe: [Trans] [trans] #99 (rfc6962-bis): Clearer definition of when a certificate is CT-compliant needed
trans issue tracker
2015-11-03
trans
/arch/msg/trans/-LlwwHF3A1JlWjtwk7xOpESZg8Q/
2108535
1646612
Re: [Trans] BOF for dnssec transparencyRe: [Trans] BOF for dnssec transparency
Paul Wouters
2015-11-03
trans
/arch/msg/trans/tf-BNfpoJgArFtjWZJchOdl2LIg/
2108498
1646572
Re: [Trans] IETF 94 TRANS minutes DraftRe: [Trans] IETF 94 TRANS minutes Draft
Karen Seo
2015-11-02
trans
/arch/msg/trans/_17jOkWEYQ0k4qfhhj51dLAGmIo/
2108144
1646573
[Trans] Milestones changed for trans WG[Trans] Milestones changed for trans WG
IETF Secretariat
2015-11-02
trans
/arch/msg/trans/7FW_XbFuC8T-gj0SBO_a4GD4b6k/
2107900
1646861
[Trans] Milestones changed for trans WG[Trans] Milestones changed for trans WG
IETF Secretariat
2015-11-02
trans
/arch/msg/trans/ioJTUUPXORe7JtWLGl4cow7hOz4/
2107889
1646861
[Trans] BOF for dnssec transparency[Trans] BOF for dnssec transparency
Paul Wouters
2015-11-02
trans
/arch/msg/trans/GqCapo4D61y1WZnIMSwgQKrH7QQ/
2107871
1646572
Re: [Trans] IETF 94 TRANS minutes DraftRe: [Trans] IETF 94 TRANS minutes Draft
Melinda Shore
2015-11-02
trans
/arch/msg/trans/AAB5ItvBO7FhvBqNljD88iu2eLA/
2107870
1646573
[Trans] IETF 94 TRANS minutes Draft[Trans] IETF 94 TRANS minutes Draft
Salz, Rich
2015-11-02
trans
/arch/msg/trans/jaE8b3y67VcSzHcpaunvqvEoTb8/
2107834
1646573
[Trans] Threat model document review[Trans] Threat model document review
Paul Wouters
2015-11-02
trans
/arch/msg/trans/6DZyzBmd_MpF7UjkuVmeIVTGXEo/
2107814
1646574
Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogIDRe: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID
trans issue tracker
2015-10-28
trans
/arch/msg/trans/C_JbONt8phmQyNATQgekeycfcDE/
2104943
1646603
Re: [Trans] [trans] #110 (rfc6962-bis): Reorganize requirements into appropriate sectionsRe: [Trans] [trans] #110 (rfc6962-bis): Reorganize requirements into appropriate sections
trans issue tracker
2015-10-28
trans
/arch/msg/trans/mk9zFVHKh417rmU3ZC0MnbMx0AE/
2104942
1646580
Re: [Trans] [trans] #105 (rfc6962-bis): Shrink LogIDRe: [Trans] [trans] #105 (rfc6962-bis): Shrink LogID
trans issue tracker
2015-10-28
trans
/arch/msg/trans/eGxhYxlr_xCvm-0mevCeC4zxpGk/
2104670
1646603
Re: [Trans] [trans] #110 (rfc6962-bis): Reorganize requirements into appropriate sectionsRe: [Trans] [trans] #110 (rfc6962-bis): Reorganize requirements into appropriate sections
trans issue tracker
2015-10-28
trans
/arch/msg/trans/59FA8DrCAnEXVZFjN4vaXOXOIsA/
2104667
1646580
40 Messages