marten-seemann / draft-seemann-quic-nat-traversal

Other
15 stars 4 forks source link

undefined "Request Id" in observed address frames? #29

Closed divagant-martian closed 5 days ago

divagant-martian commented 4 months ago

From reading the proposal I'm under the impression reporting is, let's say, opportunistic:

An endpoint that negotiated (see Section 3) this extension and offered to provide address observations to the peer MUST send an OBSERVED_ADDRESS frame on every new path. This also applies to the path used for the QUIC handshake.

Similar parts seem to follow this line of thought. Similarly, there is no frame to request a report in which a potential requester might set this request id. There is also no information about encoding or type. Was this removed at some point, or added missing other parts? Or am I misunderstanding something?