Draft: draft-ietf-quic-manageability

Commentary: as well 
 There are some outdated references those I goes will go away with further revisions . However , there are duplicate references those I believe need to be fixed manually . -- Duplicate reference : draft - ietf - quic - applicability , mentioned in ' QUIC - APPLICABILITY ' , was also mentioned in ' I - D.ietf - quic - applicability ' . -- Duplicate reference : RFC8899 , mentioned in ' RFC8899 ' , was also mentioned in ' DPLPMTUD ' . 
 I noticed that there are references to QUIC I - Ds . Applicability even references both -34 and RFC9000 : smile :
Paragraph (version A):
RFC4787 describes possible packet filtering behaviors that relate to
NATs but is often also used is other scenarios where packet filtering
is desired.  Though the guidance there holds, a particularly unwise
behavior admits a handful of UDP packets and then makes a decision to
whether or not filter later packets in the same connection.  QUIC
applications are encouraged to fail over to TCP if early packets do
not arrive at their destination I-D.ietf-quic-applicability, as QUIC
is based on UDP and there are known blocks of UDP traffic (see sec-
udp-1312).  Admitting a few packets allows the QUIC endpoint to
determine that the path accepts QUIC.  Sudden drops afterwards will
result in slow and costly timeouts before abandoning the connection.
Paragraph (version B):
RFC4787 describes possible packet filtering behaviors that relate to
NATs but is often also used is other scenarios where packet filtering
is desired.  Though the guidance there holds, a particularly unwise
behavior admits a handful of UDP packets and then makes a decision to
whether or not filter later packets in the same connection.  QUIC
applications are encouraged to fail over to TCP if early packets do
not arrive at their destination QUIC-APPLICABILITY, as QUIC is based
on UDP and there are known blocks of UDP traffic (see sec-udp-1312).
Admitting a few packets allows the QUIC endpoint to determine that
the path accepts QUIC.  Sudden drops afterwards will result in slow
and costly timeouts before abandoning the connection.
Paragraph (version A):
Note that some source ports are assumed to be reflection attack
vectors by some servers; see Section 8.1 of I-D.ietf-quic-
applicability.  As a result, NAT binding to these source ports can
result in that traffic being blocked.
Paragraph (version B):
Note that some source ports are assumed to be reflection attack
vectors by some servers; see Section 8.1 of QUIC-APPLICABILITY.  As a
result, NAT binding to these source ports can result in that traffic
being blocked.
Paragraph (version A):
Endpoints can cache PMTU information, in the IP-layer cache.  This
short-term consistency between the PMTU for flows can help avoid an
endpoint using a PMTU that is inefficient.  The IP cache can also
influence the PMTU value of other IP flows that use the same path
RFC8899, including IP packets carrying protocols other than QUIC.
The representation of an IP path is implementation-specific RFC8201.
Paragraph (version B):
Endpoints can cache PMTU information, in the IP-layer cache.  This
short-term consistency between the PMTU for flows can help avoid an
endpoint using a PMTU that is inefficient.  The IP cache can also
influence the PMTU value of other IP flows that use the same path
DPLPMTUD, including IP packets carrying protocols other than QUIC.
The representation of an IP path is implementation-specific RFC8201.