Issues
------
* tlswg/draft-ietf-tls-esni (+3/-21/💬28)
3 issues created:
- Make anonymity set references consistent (reference single definition?) (by
klinvill)
https://github.com/tlswg/draft-ietf-tls-esni/issues/568
- Are mandatory ECH extensions deployable? (by sftcd)
https://github.com/tlswg/draft-ietf-tls-esni/issues/567
- MUST NOT use retry configs may be too strong (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/565
19 issues received 28 new comments:
- #567 Are mandatory ECH extensions deployable? (9 by davidben, dennisjackson,
sftcd)
https://github.com/tlswg/draft-ietf-tls-esni/issues/567
- #565 Requirements language around retry configs may be too strong (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/565
- #547 "Don't fallback to non-ECH" option (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/547
- #545 Server reuse of key share leaks the target domain for a given connection (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/545
- #544 What does ECH acceptance mean in Split Mode? (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/544
- #543 RFC9180 recommended max for info is too short for ECH (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/543
- #542 Use of MAY in section 5 needs to be fixed up (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/542
- #524 How to retry in ECH is ambiguous (2 by chris-wood, dennisjackson)
https://github.com/tlswg/draft-ietf-tls-esni/issues/524
- #520 HRR rejection and ECH contents (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/520
- #519 Anonymity set definition should include behavior (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/519
- #517 Question on Section 10.2 (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/517
- #516 split-mode may be more a three-way thing than a two-way thing (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/516
- #515 Improve guidance for Second ClientHello construction in the event of HRR (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/515 [editorial]
- #476 Feature Request: `ECHConfigList.permit_plaintext` (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/476 [parked]
- #454 Make the definition of key protocol elements easier to find (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/454 [editorial]
- #451 Reserve some code points for GREASE (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/451 [pre-wglc]
- #440 Mitigate HRR when possible (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/440 [parked]
- #430 Make it easy to reference EncodedClientHelloInner decoding concerns (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/430 [editorial]
- #395 Add some more structure to "Offering ECH" (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/395 [editorial]
21 issues closed:
- Lessen possibility of client implementation choices undermining GREASE cover https://github.com/tlswg/draft-ietf-tls-esni/issues/512 [parked]
- Anonymity set definition should include behavior https://github.com/tlswg/draft-ietf-tls-esni/issues/519
- What does ECH acceptance mean in Split Mode? https://github.com/tlswg/draft-ietf-tls-esni/issues/544
- Split mode correlation attacks https://github.com/tlswg/draft-ietf-tls-esni/issues/513 [editorial]
- Do ECHConfig extensions use the same ExtensionType enum from TLS? https://github.com/tlswg/draft-ietf-tls-esni/issues/555
- Move ECH references over to draft-ietf-tls-svcb-ech https://github.com/tlswg/draft-ietf-tls-esni/issues/554
- Hard to imagine ECH handling in constant time - ponder and document? https://github.com/tlswg/draft-ietf-tls-esni/issues/400 [ready-for-text] [editorial]
- Question related to section 10.9.3 (Prevent SNI-Based Denial-of-Service Attacks) https://github.com/tlswg/draft-ietf-tls-esni/issues/551
- Add some more structure to "Offering ECH" https://github.com/tlswg/draft-ietf-tls-esni/issues/395 [editorial]
- split-mode may be more a three-way thing than a two-way thing https://github.com/tlswg/draft-ietf-tls-esni/issues/516
- Improve guidance for Second ClientHello construction in the event of HRR https://github.com/tlswg/draft-ietf-tls-esni/issues/515 [editorial]
- Use of MAY in section 5 needs to be fixed up https://github.com/tlswg/draft-ietf-tls-esni/issues/542
- Make the definition of key protocol elements easier to find https://github.com/tlswg/draft-ietf-tls-esni/issues/454 [editorial]
- HRR rejection and ECH contents https://github.com/tlswg/draft-ietf-tls-esni/issues/520
- Make it easy to reference EncodedClientHelloInner decoding concerns https://github.com/tlswg/draft-ietf-tls-esni/issues/430 [editorial]
- Question on Section 10.2 https://github.com/tlswg/draft-ietf-tls-esni/issues/517
- Mitigate HRR when possible https://github.com/tlswg/draft-ietf-tls-esni/issues/440 [parked]
- Feature Request: `ECHConfigList.permit_plaintext` https://github.com/tlswg/draft-ietf-tls-esni/issues/476 [parked]
- Server reuse of key share leaks the target domain for a given connection https://github.com/tlswg/draft-ietf-tls-esni/issues/545
- "Don't fallback to non-ECH" option https://github.com/tlswg/draft-ietf-tls-esni/issues/547
- RFC9180 recommended max for info is too short for ECH https://github.com/tlswg/draft-ietf-tls-esni/issues/543
Pull requests
-------------
* tlswg/draft-ietf-tls-esni (+10/-10/💬11)
10 pull requests submitted:
- Add text describing deployment impacts of no SNI access (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/566
- Clarify attacker capabilities (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/564
- TCP is not the only transport (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/563
- Punt on new transport connection specifics (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/562
- Cross-implementation decisions may be differentiators (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/561
- Note behavior and give an example alongside configurations (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/560
- Note timing side channels (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/559
- Remove alternative designs (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/558
- Create a new ECH config extension registry (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/557
- Cite draft-ietf-tls-svcb-ech for ECH in DNS (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/556
5 pull requests received 11 new comments:
- #566 Add text describing deployment impacts of no SNI access (3 by
chris-wood, dennisjackson)
https://github.com/tlswg/draft-ietf-tls-esni/pull/566
- #564 Clarify attacker capabilities (4 by chris-wood, dennisjackson, kazuho)
https://github.com/tlswg/draft-ietf-tls-esni/pull/564
- #562 Punt on new transport connection specifics (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/562
- #561 Cross-implementation decisions may be differentiators (1 by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/pull/561
- #560 Note behavior and give an example alongside configurations (2 by chris-wood, klinvill)
https://github.com/tlswg/draft-ietf-tls-esni/pull/560
10 pull requests merged:
- Cross-implementation decisions may be differentiators
https://github.com/tlswg/draft-ietf-tls-esni/pull/561
- Note behavior and give an example alongside configurations
https://github.com/tlswg/draft-ietf-tls-esni/pull/560
- Clarify attacker capabilities
https://github.com/tlswg/draft-ietf-tls-esni/pull/564
- Add text describing deployment impacts of no SNI access
https://github.com/tlswg/draft-ietf-tls-esni/pull/566
- Remove alternative designs
https://github.com/tlswg/draft-ietf-tls-esni/pull/558
- Create a new ECH config extension registry
https://github.com/tlswg/draft-ietf-tls-esni/pull/557
- Cite draft-ietf-tls-svcb-ech for ECH in DNS
https://github.com/tlswg/draft-ietf-tls-esni/pull/556
- Note timing side channels
https://github.com/tlswg/draft-ietf-tls-esni/pull/559
- TCP is not the only transport
https://github.com/tlswg/draft-ietf-tls-esni/pull/563
- Fix typo retry_configs
https://github.com/tlswg/draft-ietf-tls-esni/pull/552
Repositories tracked by this digest:
-----------------------------------
* https://github.com/tlswg/draft-ietf-tls-semistatic-dh
* https://github.com/tlswg/draft-ietf-tls-md5-sha1-deprecate
* https://github.com/tlswg/draft-ietf-tls-esni
* https://github.com/tlswg/certificate-compression
* https://github.com/tlswg/draft-ietf-tls-external-psk-importer
* https://github.com/tlswg/draft-ietf-tls-ticketrequest
* https://github.com/tlswg/tls13-spec
* https://github.com/tlswg/tls-flags
* https://github.com/tlswg/dtls13-spec
* https://github.com/tlswg/dtls-conn-id
* https://github.com/tlswg/tls-subcerts
* https://github.com/tlswg/oldversions-deprecate
* https://github.com/tlswg/sniencryption
* https://github.com/tlswg/tls-exported-authenticator
* https://github.com/tlswg/draft-ietf-tls-ctls
* https://github.com/tlswg/external-psk-design-team
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
