idnits 2.17.1 draft-ietf-pilc-2.5g3g-12.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 71 4 RFC 3481 6 Title: TCP over Second (2.5G) and Third (3G) Generation 7 Wireless Networks 8 Author(s): H. Inamura, Ed., G. Montenegro, Ed., R. Ludwig, 9 A. Gurtov, F. Khafizov 10 Status: Best Current Practice 11 Date: February 2003 12 Mailbox: inamura@mml.yrp.nttdocomo.co.jp, gab@sun.com, 13 Reiner.Ludwig@Ericsson.com, 14 andrei.gurtov@sonera.com, 15 faridk@nortelnetworks.com 16 Pages: 26 17 Characters: 61528 18 Updates/Obsoletes/SeeAlso: None 20 I-D Tag: draft-ietf-pilc-2.5g3g-12.txt 22 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3481.txt 24 This document describes a profile for optimizing TCP to adapt so that 25 it handles paths including second (2.5G) and third (3G) generation 26 wireless networks. It describes the relevant characteristics of 2.5G 27 and 3G networks, and specific features of example deployments of such 28 networks. It then recommends TCP algorithm choices for nodes known 29 to be starting or ending on such paths, and it also discusses open 30 issues. The configuration options recommended in this document are 31 commonly found in modern TCP stacks, and are widely available 32 standards-track mechanisms that the community considers safe for use 33 on the general Internet. 35 This document is a product of the Performance Implications of Link 36 Characteristics Working Group of the IETF. 38 This document specifies an Internet Best Current Practices for the 39 Internet Community, and requests discussion and suggestions for 40 improvements. Distribution of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.