QUIC Design Documentand Specification Rationale（三）（即时翻译，会有多处错误）

注：请转载后注明出处

GOALS

We’d like to develop a transport that supports the following goals:

【我们希望开发出一种传输方式支持如下几个目标】

1.Widespread deployability in today’s internet (i.e., makes it through middleboxes;

runs on common user client machines without kernel changes, or elevated

privileges)

【1.在当下的英特网中广泛的可部署的能力（例如，轻易穿透中间设备（如防火墙），能在普遍的用户机器运行，但不需要内核额外的支持或者较高的优先级）】

2.Reduced headofline blocking due to packet loss (losing one packet will not

generally impair other multiplexed streams)

【2.减少由于丢包导致的线头阻塞（http://en.wikipedia.org/wiki/Head-of-line_blocking），丢失一个包通常不会导致其他多路复用的码流出现问题】

3.Low latency (minimal roundtrip costs, both during setup/resumption, and in

response to packet loss)

a.Significantly reduced connection startup latency (Commonly zero RTT

connection, cryptographic hello, and initial request(s))

b.Attempt to use Forward Error Correcting (FEC) codes to reduce

retransmission latency after packet loss.

【3.低延时（最小的往返时延消耗，以及在链接的建立/恢复，和对丢包的恢复）a。大大地链接启动的时延的降低（通常是0 RTT链接，加密的“hello”和初始化请求）b。尝试使用“前向纠错”机制来降低丢包后的重传的延时】

4.Improved support for mobile, in terms of latency and efficiency (as opposed to TCP

connections which are torn down during radio shutdowns)

【4.在延时和效率方面，提升对移动终端的支持（相反，在无线电通信关闭时被关闭的TCP链接）】

5.Congestion avoidance support comparable to, and friendly to, TCP (unified across

multiplexed streams)

a.Individual stream flow control, to prevent a stream with a fast source and slow

sink from flooding memory at receiver end, and allow backpressure to

appear at the send end.

【5.拥塞避免算法的支持可以媲美的上TCP（一致地通过多路复用流）a。单独的码流控制，用于阻止某条流拥有快速发送的速度，和慢速的接收终端，和允许背压能体现在发送的节点上】

6.Privacy assurances comparable to TLS (without requiring inorder transport or

inorder decryption)

【6. 与TSL相比较的隐私保证（不需要命令必须顺序的传输和顺序的解密）】

7.Reliable and safe resource requirements scaling, both serverside and clientside

(including reasonable buffer management and aids to avoid facilitating DoS

magnification attacks)

【7.可靠的、安全的资源需求的缩减增多，在服务器端和客户端（包括一些缓冲区管理原因和帮助避免DOS攻击的）】

8.Reduced bandwidth consumption and increased channel status responsiveness

(via unified signaling of channel status across all multiplexed streams)

【8.更低的带宽消耗和增强的通道状态反馈（通过统一的通道状态信号来关联到所有的多路复用的码流）】

9.Reduced packetcount, if not in conflict with other goals.

【9.在不于其他目标冲突的前提下，更少的数据包数】

10.Support reliable transport for multiplexed streams (can simulate TCP on the

multiplexed streams)

【10.支持多路复用下流的可靠的传输（可以模拟基于多路复用的码流的TCP）】

11.Efficient demuxmux properties for proxies, if not in conflict with other goals.

【11.在不于其他目标冲突的前提下，针对代理设备的高效的解复用，封装】

12.Reuse, or evolve, existing protocols at any point where it is plausible to do so,

without sacrificing our stated goals (e.g., consider uTP(Ledbat), DCCP, TCP

minion)

【12.在不牺牲我们的既定目标的前提下，在任何时间点时重用、或发展，已有的协议貌似都是合理的。】

注：请转载后注明出处