RFC 4782:Quick-Start for TCP and IP
RFC-Ref

deployment


Click on the red underlined text to get to the source

... Section 9 gives an evaluation of the costs and benefits of Quick- Start, and Section 10 discusses implementation and deployment issues. The appendices discuss related work, Quick-Start design decisions, ...


... Experimental to Proposed Standard, and will affect the degree of deployment of Quick-Start while in Experimental mode. ...


... routers, particularly in the beginning of Quick-Start's deployment in the Internet. This would mean some extra delay for the end hosts ...


... Implementation and Deployment Issues ...
... This section discusses some of the implementation issues with Quick- Start. This section also discusses some of the key deployment issues, such as the chicken-and-egg deployment problems of mechanisms that have to be deployed in both routers ...
... Start. This section also discusses some of the key deployment issues, such as the chicken-and-egg deployment problems of mechanisms that have to be deployed in both routers and end nodes ...
... routers and end nodes in order to work, and the problems posed by the wide deployment of middleboxes today that block the use of known or unknown IP Options. ...
... Possible Deployment Scenarios ...
... network paths and the security issues discussed in Section 11, the most realistic initial deployment of Quick-Start would most likely take place in intranets ...
... Quick-Start is not currently intended for ubiquitous deployment in the global Internet. In particular, Quick-Start ...
... Start would potentially be useful. These are the environments that might consider an initial deployment of Quick-Start in the routers ...
... In such an environment, Quick-Start would be of benefit to users, and there would be a clear incentive for the deployment of Quick- Start in routers ...
... A Comparison with the Deployment Problems of ECN ...
... Given the glacially slow rate of deployment of ECN in the Internet to ...
... Internet to date [MAF05], it is disconcerting to note that some of the deployment problems of Quick-Start are even greater than those of ECN ...
... Quick-Start requires Quick-Start deployment on all of the routers along the end-to-end ...
... However, in spite of these issues, there is some hope for the deployment of Quick-Start, at least in protected corners of the Internet ...


... approach of optimistic sending. (1) Incremental deployment: One question would be the potential complications of incremental deployment ...
... deployment: One question would be the potential complications of incremental deployment, where some of the routers along the path might not understand the packet information describing the initial window. ...


... AntiECN, but as powerful or more powerful in terms of the specific issue of allowing larger initial windows. Also, (we think) it is more amenable to incremental deployment in the current Internet. ...
... alternately, as a negative step of unnecessarily delaying more fundamental changes. Without answering this question, we would note that our own approach tends to favor the incremental deployment of relatively simple mechanisms, as long as the simple mechanisms are not short-term hacks, but mechanisms that lead the overall ...



Google
Web
RFC-Ref