idnits 2.17.1 draft-ietf-pilc-link-arq-issues-04.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 62 4 RFC 3366 6 Title: Advice to link designers on link Automatic Repeat 7 reQuest (ARQ) 8 Author(s): G. Fairhurst, L. Wood 9 Status: Best Current Practice 10 Date: August 2002 11 Mailbox: gorry@erg.abdn.ac.uk, lwood@cisco.com 12 Pages: 27 13 Characters: 66097 14 SeeAlso: BCP 62 16 I-D Tag: draft-ietf-pilc-link-arq-issues-04.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3366.txt 20 This document provides advice to the designers of digital 21 communication equipment and link-layer protocols employing 22 link-layer Automatic Repeat reQuest (ARQ) techniques. This document 23 presumes that the designers wish to support Internet protocols, but 24 may be unfamiliar with the architecture of the Internet and with the 25 implications of their design choices for the performance and 26 efficiency of Internet traffic carried over their links. 28 ARQ is described in a general way that includes its use over a wide 29 range of underlying physical media, including cellular wireless, 30 wireless LANs, RF links, and other types of channel. This document 31 also describes issues relevant to supporting IP traffic over 32 physical-layer channels where performance varies, and where link ARQ 33 is likely to be used. 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.