Tracking issue - Gathering Test Vectors

[pinkforest]

I've done some initial plumbing for internal self-validation at

• Upgrade 0.23, re-organise external examples and tests as external #28

I have a static test generator I'm working on similar to wycheproof I did for curve25519-dalek:

• ed25519: Add wycheproofs dalek-cryptography/curve25519-dalek#640

Plumbing sources progress

• Self-test / map between rustls / CryptoProvider Validaton / Tests #31
• Add / ensure IETF TLS 1.3 test vectors covered #30
• Integration tests - Internal localhost #49
• Algo tester #52
• Failpoint tests #54

Any other vectors we should plumb ? These are the tests we run internally w/o downstream deps / internet access e.g. pure TLS or with bare minimal application part if any so it can be used in CI

Also hunting vectors we can just simply plumb without creating new things - worst case they can be upstreamed as provider validation suite if something needs to be created fresh

See if we can use a transcript like this: https://tls13.xargs.org/