Re: [quicwg/base-drafts] QUIC header format/demultiplexing (#426)

[janaiyengar <[e-mail]>]

@csperkins: I appreciate the need to mux with STUN packets. RFC 5389 says however: "In some usages, STUN must be multiplexed with other protocols (e.g., [MMUSIC-ICE], [SIP-OUTBOUND]).  In these usages, there must be a way to inspect a packet and determine if it is a STUN packet or not. STUN provides three fields in the STUN header with fixed values that can be used for this purpose.  If this is not sufficient, then STUN packets can also contain a FINGERPRINT value, which can further be used to distinguish the packets." Isn't this FINGERPRINT to be used for exactly this sort of use case where it conflicts with other packet types? Why doesn't demuxing on the FINGERPRINT work?

Separately, I'm not convinced that we need to mux with other protocols. If we agree on the need to mux QUIC packet types with STUN, then we lose only 4 packet types... but we seem to have put aside a lot more than that in #956. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/426#issuecomment-349676110