Transmission Control Protocol Specification
draft-eddy-rfc793bis-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-10-20
Replaced by draft-ietf-tcpm-rfc793bis
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                  W. Eddy
Internet-Draft                                               MTI Systems
Obsoletes: 793 (if approved)                                A. Oppermann
Intended status: Standards Track
Expires: April 24, 2014                                 October 21, 2013

              Transmission Control Protocol Specification
                        draft-eddy-rfc793bis-00

Abstract

   This document specifies the Internet's Transmission Control Protocol
   (TCP).  TCP is an important transport layer protocol in the Internet
   stack, and has continuously evolved over decades of use and growth of
   the Internet.  In this time, a number of changes have been made to
   TCP as it was specified in RFC 793, though these are only documented
   in a piecemeal fashion.  This document collects and brings those
   changes together with the protocol specification from RFC 793.  This
   document obsoletes RFC 793 and several other RFCs (TODO: list actual
   RFCs).

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [1].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 24, 2014.

Copyright Notice

Eddy & Oppermann         Expires April 24, 2014                 [Page 1]
Internet-Draft              TCP Specification               October 2013

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Purpose and Scope . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Functional Specification  . . . . . . . . . . . . . . . . . .   3
     3.1.  Segment Format  . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  State Machine . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Event Processing  . . . . . . . . . . . . . . . . . . . .   4
   4.  Changes from RFC 793  . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Purpose and Scope

   In 1983, RFC 793 [2] was released, documenting the Transmission
   Control Protocol (TCP), and replacing earlier specifications for TCP
   that had been published in the past.

Eddy & Oppermann         Expires April 24, 2014                 [Page 2]
Internet-Draft              TCP Specification               October 2013

   Since that time, TCP has been implemented many times, and has been
   used as a transport protocol for numerous applications on the
Show full document text