Subject: [QUIC] Fwd: Last Call: <draft-ietf-tsvwg-rfc5405bis-13.txt> (UDP Usage Guidelines) to Best Current Practice

From: Mark Nottingham <[email-masked]>
Date: Tue, 31 May 2016 12:54:35 +1000

Apologies if I missed discussion about this. 

If this is to be a BCP, is it safe to assume that a) it will apply to QUIC if chartered, and b) that folks here are comfortable with its requirements?

Cheers,

> Begin forwarded message:
> 
> From: The IESG <[email-masked]>
> Subject: Last Call: <draft-ietf-tsvwg-rfc5405bis-13.txt> (UDP Usage Guidelines) to Best Current Practice
> Date: 18 May 2016 at 10:17:06 AM AEST
> To: "IETF-Announce" <[email-masked]>
> Cc: [email-masked], [email-masked], [email-masked]
> Reply-To: [email-masked]
> Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/ahGfkYGwGGV_F0XanpqWTyZTwFA>
> 
> 
> The IESG has received a request from the Transport Area Working Group WG
> (tsvwg) to consider the following document:
> - 'UDP Usage Guidelines'
>  <draft-ietf-tsvwg-rfc5405bis-13.txt> as Best Current Practice
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> [email-masked] mailing lists by 2016-05-31. Exceptionally, comments may be
> sent to [email-masked] instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   The User Datagram Protocol (UDP) provides a minimal message-passing
>   transport that has no inherent congestion control mechanisms.  This
>   document provides guidelines on the use of UDP for the designers of
>   applications, tunnels and other protocols that use UDP.  Congestion
>   control guidelines are a primary focus, but the document also
>   provides guidance on other topics, including message sizes,
>   reliability, checksums, middlebox traversal, the use of ECN, DSCPs,
>   and ports.
> 
>   Because congestion control is critical to the stable operation of the
>   Internet, applications and other protocols that choose to use UDP as
>   an Internet transport must employ mechanisms to prevent congestion
>   collapse and to establish some degree of fairness with concurrent
>   traffic.  They may also need to implement additional mechanisms,
>   depending on how they use UDP.
> 
>   Some guidance is also applicable to the design of other protocols
>   (e.g., protocols layered directly on IP or via IP-based tunnels),
>   especially when these protocols do not themselves provide congestion
>   control.
> 
>   This document obsoletes RFC5405 and adds guidelines for multicast UDP
>   usage.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 

--
Mark Nottingham   https://www.mnot.net/