RFC 3366: Advice to link designers on link Automatic Repeat reQuest (ARQ)

In plain English — editorial summary, not part of the RFC

This document provides advice to the designers of digital communication equipment and link-layer protocols employing link layer Automatic Repeat reQuest (ARQ) techniques. This document presumes that the designers wish to support Internet protocols, but may be unfamiliar with the architecture of the Internet and with the implications of their design choices on the performance and efficiency of Internet traffic carried over their links.

Document record

Document ID

RFC3366

Published

September 2002

Authors

G. Fairhurst; L. Wood

Status

BEST CURRENT PRACTICE

Stream

IETF

Area

tsv

Pages

27

Also known as

BCP62

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3366

Topics

• tcp/ip
• subnetworks

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4544Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)Obsoleted

  May 2006

• RFC 4545Definitions of Managed Objects for IP Storage User Identity AuthorizationCurrent

  May 2006

• RFC 5047DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)Updated

  October 2007

• RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent

  March 2003

• RFC 1918Address Allocation for Private InternetsUpdated

  February 1996

• RFC 5065Autonomous System Confederations for BGPUpdated

  August 2007

• RFC 5966DNS Transport over TCP - Implementation RequirementsObsoleted

  August 2010

• RFC 7766DNS Transport over TCP - Implementation RequirementsUpdated

  March 2016

Also filed under

• BEST CURRENT PRACTICE
• 2002
• IETF stream
• tsv area
• BCP 62