|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.websec-1 can use Congestion Control Principles discussed in [22] to improve performance.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=2914
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[BS00] Balakrishnan H. and S. Seshan, "The Congestion Manager",/
Work in Progress./
/
[DMKM00] Dawkins, S., Montenegro, G., Kojo, M. and V. Magret,/
"End-to-end Performance Implications of Slow Links",/
Work in Progress./
/
[FF99] Floyd, S. and K. Fall, "Promoting the Use of End-to-End/
Congestion Control in the Internet", IEEE/ACM/
Transactions on Networking, August 1999. URL/
http://www.aciri.org/floyd/end2end-paper.html/
/
[HPF00] Handley, M., Padhye, J. and S. Floyd, "TCP Congestion/
Window Validation", RFC 2861, June 2000./
/
[Jacobson88] V. Jacobson, Congestion Avoidance and Control, ACM/
SIGCOMM '88, August 1988./
/
[RFC793] Postel, J., "Transmission Control Protocol", STD 7, RFC/
793, September 1981./
/
[RFC896] Nagle, J., "Congestion Control in IP/TCP", RFC 896,/
January 1984./
/
[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts --/
Communication Layers", STD 3, RFC 1122, October 1989./
[RFC1323] Jacobson, V., Braden, R. and D. Borman, "TCP Extensions/
for High Performance", RFC 1323, May 1992./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2212] Shenker, S., Partridge, C. and R. Guerin, "Specification/
of Guaranteed Quality of Service", RFC 2212, September/
1997./
/
[RFC2309] Braden, R., Clark, D., Crowcroft, J., Davie, B.,/
Deering, S., Estrin, D., Floyd, S., Jacobson, V.,/
Minshall, G., Partridge, C., Peterson, L., Ramakrishnan,/
K.K., Shenker, S., Wroclawski, J., and L. Zhang,/
"Recommendations on Queue Management and Congestion/
Avoidance in the Internet", RFC 2309, April 1998./
/
[RFC2357] Mankin, A., Romanow, A., Bradner, S. and V. Paxson,/
"IETF Criteria for Evaluating Reliable Multicast/
Transport and Application Protocols", RFC 2357, June/
1998./
/
[RFC2414] Allman, M., Floyd, S. and C. Partridge, "Increasing/
TCP's Initial Window", RFC 2414, September 1998./
/
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z./
and W. Weiss, "An Architecture for Differentiated/
Services", RFC 2475, December 1998./
/
[RFC2481] Ramakrishnan K. and S. Floyd, "A Proposal to add/
Explicit Congestion Notification (ECN) to IP", RFC 2481,/
January 1999./
/
[RFC2525] Paxson, V., Allman, M., Dawson, S., Fenner, W., Griner,/
J., Heavens, I., Lahey, K., Semke, J. and B. Volz,/
"Known TCP Implementation Problems", RFC 2525, March/
1999./
/
[RFC2581] Allman, M., Paxson, V. and W. Stevens, "TCP Congestion/
Control", RFC 2581, April 1999./
/
[RFC2582] Floyd, S. and T. Henderson, "The NewReno Modification to/
TCP's Fast Recovery Algorithm", RFC 2582, April 1999./
/
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,/
Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext/
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999./
[SCWA99] S. Savage, N. Cardwell, D. Wetherall, and T. Anderson,/
TCP Congestion Control with a Misbehaving Receiver, ACM/
Computer Communications Review, October 1999./
/
[TCPB98] Hari Balakrishnan, Venkata N. Padmanabhan, Srinivasan/
Seshan, Mark Stemm, and Randy H. Katz, TCP Behavior of a/
Busy Internet Server: Analysis and Improvements, IEEE/
Infocom, March 1998. Available from:/
"http://www.cs.berkeley.edu/~hari/papers/infocom98.ps.gz"./
/
[TCPF98] Dong Lin and H.T. Kung, TCP Fast Recovery Strategies:/
Analysis and Improvements, IEEE Infocom, March 1998./
Available from:/
"http://www.eecs.harvard.edu/networking/papers/infocom-/
tcp-final-198.pdf"./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
