Issues
------
* tlswg/tls-key-update (+1/-4/💬5)
 1 issues created:
 - Stronger PCS (by yaronf)
https://github.com/tlswg/tls-key-update/issues/94
 5 issues received 5 new comments:
 - #94 Stronger PCS (1 by yaroslavros)
https://github.com/tlswg/tls-key-update/issues/94 - #90 Exporter_secret probably should != exporter_secret_0 (1 by tireddy2) https://github.com/tlswg/tls-key-update/issues/90 - #78 Ambiguities in version -06: Protocol diagram and state machine (1 by tireddy2) https://github.com/tlswg/tls-key-update/issues/78 - #56 DTLS retransmit (1 by tireddy2) https://github.com/tlswg/tls-key-update/issues/56 - #46 Explain interactions with other handshake messages (1 by tireddy2) https://github.com/tlswg/tls-key-update/issues/46
 4 issues closed:
- Explain interactions with other handshake messages https://github.com/tlswg/tls-key-update/issues/46 - DTLS retransmit https://github.com/tlswg/tls-key-update/issues/56 - Ambiguities in version -06: Protocol diagram and state machine https://github.com/tlswg/tls-key-update/issues/78 - Exporter_secret probably should != exporter_secret_0 https://github.com/tlswg/tls-key-update/issues/90


Pull requests
-------------
* tlswg/draft-ietf-tls-esni (+1/-0/💬0)
 1 pull requests submitted:
 -  (by grittygrease)
* tlswg/tls-key-update (+1/-0/💬1)
 1 pull requests submitted:
 -  (by tireddy2)
 1 pull requests received 1 new comments:
 - #93 Update to Appendix (1 by tireddy2)
https://github.com/tlswg/tls-key-update/pull/93
* tlswg/tls-trust-anchor-ids (+1/-0/💬0)
 1 pull requests submitted:
 -  (by dadrian)
* tlswg/tlswg-wiki (+3/-0/💬1)
 3 pull requests submitted:
 -  (by muhammad-usama-sardar)
- (by seanturner) - (by seanturner)
 1 pull requests received 1 new comments:
 - #25 Update codepoint registration (1 by richsalz)
https://github.com/tlswg/tlswg-wiki/pull/25

Repositories tracked by this digest:
-----------------------------------
* https://github.com/tlswg/certificate-compression
* https://github.com/tlswg/dnssec-chain-extension
* https://github.com/tlswg/draft-deprecate-obsolete-kex
* https://github.com/tlswg/draft-ietf-tls-cert-abridge
* https://github.com/tlswg/draft-ietf-tls-ctls
* https://github.com/tlswg/draft-ietf-tls-ecdhe-psk-aead
* https://github.com/tlswg/draft-ietf-tls-ech-keylogfile
* https://github.com/tlswg/draft-ietf-tls-esni
* https://github.com/tlswg/draft-ietf-tls-external-psk-importer
* https://github.com/tlswg/draft-ietf-tls-grease
* https://github.com/tlswg/draft-ietf-tls-iana-registry-updates
* https://github.com/tlswg/draft-ietf-tls-md5-sha1-deprecate
* https://github.com/tlswg/draft-ietf-tls-mlkem
* https://github.com/tlswg/draft-ietf-tls-semistatic-dh
* https://github.com/tlswg/draft-ietf-tls-svcb-ech
* https://github.com/tlswg/draft-ietf-tls-ticketrequest
* https://github.com/tlswg/draft-ietf-tls-tls13-vectors
* https://github.com/tlswg/dtls-conn-id
* https://github.com/tlswg/dtls-rrc
* https://github.com/tlswg/dtls13-spec
* https://github.com/tlswg/oldversions-deprecate
* https://github.com/tlswg/rfc4492bis
* https://github.com/tlswg/rfc8447bis
* https://github.com/tlswg/rfc8773bis
* https://github.com/tlswg/sniencryption
* https://github.com/tlswg/sslkeylogfile
* https://github.com/tlswg/sslv3-diediedie
* https://github.com/tlswg/super-jumbo-record-limit
* https://github.com/tlswg/tls13-spec
* https://github.com/tlswg/tls-exported-authenticator
* https://github.com/tlswg/tls-fatt
* https://github.com/tlswg/tls-flags
* https://github.com/tlswg/tls-key-share-prediction
* https://github.com/tlswg/tls-key-update
* https://github.com/tlswg/tls-mldsa
* https://github.com/tlswg/tls-record-limit
* https://github.com/tlswg/tls-subcerts
* https://github.com/tlswg/tls-trust-anchor-ids
* https://github.com/tlswg/tls12-frozen
* https://github.com/tlswg/tls13-pkcs1
* https://github.com/tlswg/tls13-rfc
* https://github.com/tlswg/tlswg-wiki


--
To have a summary like this sent to your list, see: 
https://github.com/ietf-github-services/activity-summary
_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to