idnits 2.17.1 draft-ietf-pilc-slow-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 48 4 RFC 3150 6 Title: End-to-end Performance Implications of Slow Links 7 Author(s): S. Dawkins, G. Montenegro, M. Kojo, V. Magret 8 Status: Best Current Practice 9 Date: July 2001 10 Mailbox: spencer.dawkins@fnc.fujitsu.com, gab@sun.com, 11 kojo@cs.helsinki.fi, vincent.magret@alcatel.com 12 Pages: 17 13 Characters: 39942 14 SeeAlso: BCP 48 16 I-D Tag: draft-ietf-pilc-slow-07.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3150.txt 20 This document makes performance-related recommendations for users of 21 network paths that traverse "very low bit-rate" links. 23 "Very low bit-rate" implies "slower than we would like". This 24 recommendation may be useful in any network where hosts can saturate 25 available bandwidth, but the design space for this recommendation 26 explicitly includes connections that traverse 56 Kb/second modem 27 links or 4.8 Kb/second wireless access links - both of which are 28 widely deployed. 30 This document discusses general-purpose mechanisms. Where 31 application-specific mechanisms can outperform the relevant 32 general-purpose mechanism, we point this out and explain why. 34 This document has some recommendations in common with RFC 2689, 35 "Providing integrated services over low-bitrate links", especially 36 in areas like header compression. This document focuses more on 37 traditional data applications for which "best-effort delivery" is 38 appropriate. 40 This document is a product of the Performance Implications of Link 41 Characteristics Working Group of the IETF. 43 This document specifies an Internet Best Current Practices for the 44 Internet Community, and requests discussion and suggestions for 45 improvements. Distribution of this memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.