Draft: draft-ietf-quic-manageability

Commentary: AFAIK Microsoft 's SMB - over - QUIC also uses 443 . 
 Not sure we explicitly need to add that ... ? 
 It does underscore the point that HTTP/3 ! = 443 , and 443 ! = HTTP/3 . I think it 's useful to add . 
 The assumption that an application can be identified in the network based on the port number is less true today due to encapsulation , mechanisms for dynamic port assignments , and NATs . NATs do n't hide the destination port which traditionally identifies the application , so it feels wrong to add it to this list . It is true more and more applications use port 443 ( and HTTPS ) but we do n't see traditional applications ( eg IMAP , SMTP ) move to port 443 either . The mechanisms for dynamic port assignments themselves also seem to be on their way out . Is there anything but NFS still using portmap / rpc dynamic ports ( is it still using that even , since people hardcoded it to 2049 years ago anyway ) 
 There 's an example in that makes this true enough for QUIC that I 'd like to say something about it : UDP 443 does n't mean QUIC , and it does n't even mean HTTP/3 over QUIC , and HTTP/3 over QUIC does n't imply UDP 443 because ... well , of HTTP semantics ( but I do think  is right here -- " appearing in a URL " is probably the most widely used form of dynamic port assignment today ) . 
 I 've sent a reply to  by email and waiting for a response now . 
 For the record this is my mail reply : " [  ] There is actually an example : Microsoft 's SMB - over - QUIC uses 443 . I believe for QUIC more and more applications will just use h3 as a transport and simply go with 443 . However , do you think any changes to the text are needed ? If so , can you be more concrete ? " 
 RFC6335 also says this I removed NAT as we only talk about dest port here and another reference to RFC6335 in PR
Paragraph (version A):
At the time of writing, two application bindings for QUIC have been
published or adopted by the IETF: HTTP/3 QUIC-HTTP and DNS over
Dedicated QUIC Connections I-D.ietf-dprive-dnsoquic.  These are both
known at the time of writing to have active Internet deployments, so
an assumption that all QUIC traffic is HTTP/3 is not valid.  HTTP/3
uses UDP port 443 by convention but various methods can be used to
specify alternate port numbers.  Simple assumptions about whether a
given flow is using QUIC based upon a UDP port number may therefore
not hold; see also Section 5 of RFC7605.
Paragraph (version B):
At the time of writing, two application bindings for QUIC have been
published or adopted by the IETF: HTTP/3 QUIC-HTTP and DNS over
Dedicated QUIC Connections I-D.ietf-dprive-dnsoquic.  These are both
known at the time of writing to have active Internet deployments, so
an assumption that all QUIC traffic is HTTP/3 is not valid.  HTTP/3
uses UDP port 443 by convention but various methods can be used to
specify alternate port numbers.  Other applications (e.g.,
Microsoft's SMB over QUIC) also use UDP port 443 by default.
Therefore, simple assumptions about whether a given flow is using
QUIC, or indeed which application it might be using QUIC, based
solely upon a UDP port number may not hold; see also Section 5 of
RFC7605.