search

ietf-wg-masque / draft-ietf-masque-quic-proxy

Other
12 stars 7 forks source link

Add hacky interop parser. #31

Closed chris-wood closed 3 years ago

chris-wood commented 3 years ago

This spits out:

├── interop
│   └── tests
│       ├── connect-udp.mjs
│       ├── draft-pauly-masque-quic-proxy.mjs
│       └── index.mjs

With contents:

export default
{
    "description": "TBD", 
    "tests": [
        {
            "kind": "must", 
            "name": "Client sends `Client-Connection-Id` in first `CONNECT-UDP` request", 
            "id": "connect-udp-quic-client-cid"
        }
    ], 
    "name": "QUIC-Aware Proxying Using CONNECT-UDP", 
    "id": "draft-pauly-masque-quic-proxy.mjs"
}
DavidSchinazi commented 3 years ago

This all seems fine, but why is it in the repository for this individual draft? Shouldn't we have an official MASQUE WG repo that can hold things like this for CONNECT-UDP interop results?

chris-wood commented 3 years ago

This all seems fine, but why is it in the repository for this individual draft? Shouldn't we have an official MASQUE WG repo that can hold things like this for CONNECT-UDP interop results?

Maybe, though it seems simpler to manage interop requirements and results right alongside the document source. This change extracts requirements from the document source and turns them into test targets. Implementations then submit PRs indicating their conformance against those targets.

I expect the actual mechanics here to change as we get experience and feedback on how good, bad, ugly this is.