Intended status: Standards Track A.Eromenko September 2016
draft-eromenko-ipff-tcp64-04

Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
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-DRAFT
"TCP 64-bit extension: Modern Variation",
Alexey Eromenko, 2016-09-29, 
<draft-eromenko-ipff-tcp64-04.txt>
expiration date: 2017-03-29

Intended status: Standards Track
                                                              A.Eromenko
                                                          September 2016

                  TCP 64-bit extension: "Modern Variation"
                ===========================================
                    for Internet Protocol - Five Fields

Abstract

   This document attempts to modernize TCP protocol for new reality,
   faster bandwidth, encryption-optimization and optional checksums,
   which is required for Identity-Locator Network Protocol (ILNP) 
   compatibility.
   This extension is backwards compatible with the original TCP 
   specification during session establishment, but not compatible 
   during the rest of the session nor with deployed middleboxes.

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."

Copyright Notice

   Copyright (c) 2015 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.

Table of Contents

   Introduction
   1. TCP Header: "Classic variation"
   2. TCP Header: "Modern variation" a.k.a TCP.64
   2.1. TCP Header: "Modern variation without CRC"
   3. Initiating a TCP.64 Session "Modern Variation"
   4. TCP.64 "Modern Variation" establishment options
   4.1. TCP.64 Session option: Modern Maximum Segment Size
   4.2. TCP.64 Session option: Modern window scaling
   4.3. TCP.64 Session option: Checksum ignored
   Authors' Contacts

Introduction

   TCP in IP-FF comes in several variations, of flavors.
   The questions is:
   Our operating systems and processors are 64-bit.
   Why not make TCP 64-bit also ?
   Well, I decided to define what TCP 64-bit should look like.

   The session begins with the good-old, time-tested 
   "Classic variation", which looks familiar. 
   Just Port fields have moved to the "IP" layer.
   ...and only during SYN/ACK, it MAY be moved to a different variation.

1. TCP Header: "Classic variation"

    0                   1                   2                   3   
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  4|                        Sequence Number                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  8|                    Acknowledgment Number                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 12|  Data |     |N|C|E|U|A|P|R|S|F|                               |
   | Offset|     |S|W|C|R|C|S|S|Y|I|            Window             |
   |       |     | |R|E|G|K|H|T|N|N|                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 16|           Checksum            |         Urgent Pointer        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Options                    |    Padding    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             data                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(bytes)

   Few differences between original TCP and TCP/IPFF "classic":

   a. Ports have moved to IPFF layer.

   b. Checksum needs to be computed using the new pseudo-header,
      according to [IPFF] specification.
      But using the old checksum algorithm (not CRC); This is to allow
      TCP/IPFF to function fairly fast on old processors.
Show full document text