idnits 2.17.1 draft-ietf-pilc-pep-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 RFC 3135 5 Title: Performance Enhancing Proxies Intended to Mitigate 6 Link-Related Degradations 7 Author(s): J. Border, M. Kojo, J. Griner, G. Montenegro, 8 Z. Shelby 9 Status: Informational 10 Date: June 2001 11 Mailbox: border@hns.com, kojo@cs.helsinki.fi, 12 jgriner@grc.nasa.gov, gab@sun.com, 13 zach.shelby@ee.oulu.fi 14 Pages: 45 15 Characters: 114825 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-pilc-pep-07.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3135.txt 22 This document is a survey of Performance Enhancing Proxies (PEPs) 23 often employed to improve degraded TCP performance caused by 24 characteristics of specific link environments, for example, in 25 satellite, wireless WAN, and wireless LAN environments. Different 26 types of Performance Enhancing Proxies are described as well as the 27 mechanisms used to improve performance. Emphasis is put on proxies 28 operating with TCP. In addition, motivations for their development 29 and use are described along with some of the consequences of using 30 them, especially in the context of the Internet. 32 This document is a product of the Performance Implications of Link 33 Characteristics Working Group of the IETF. 35 This memo provides information for the Internet community. It does 36 not specify an Internet standard of any kind. Distribution of this 37 memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.