Intended status: Standards Track A.Eromenko September 2016

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 Protocol Five Fields - Fragmented Datagram Protocol", 
Alexey Eromenko, 2016-09-29, 
expiration date: 2017-03-29

Intended status: Standards Track
                                                          September 2016

                      Fragmented Datagram Protocol
                 for Internet Protocol "Five Fields" (IP-FF)
                          Specification draft


A heavy-weight version of the UDP protocol, intended to provide simple
 fragmentation mechanism with Internet Protocol "Five Fields", along 
 with a stronger checksum at a cost of somewhat higher overhead.

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

   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
   ( 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 Fragmented Datagram  Protocol  (FDP)  is  defined  to  make  
datagram   mode  communication possible in  the computing environment,
  where fragmented transmission and reception are needed.
FDP conceptually is a heavy-weight UDP if you will.

                   Fragmented Datagram Header Format

    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|                                                               |
   +                       CRC64c Checksum                         +
  8|                                                               |
 12|M|       Fragment Offset       |                               |
   |F|                             |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
 16|                       Fragment Identifier                     |
   |                                                               |
   +                          data octets ...                      .
   |                                                               .


   CRC64c Checksum (64-bit)  -- 64-bit checksum. See CRC64 Checksum.

   M flag               1 = more fragments; 0 = last fragment.

   Fragment Offset      15-bit unsigned integer.  The offset, in 8-byte
                        units, of the data following this header,
                        relative to the start of the datagram.

   Fragment Identifier  48-bit identifier is needed to distinguish
                        fragments from different datagrams.

   FDP segment must only be assembled when the six-tuple matches:
   1. Source and Destination IP address
   2. Source and Destination ports / Flow
   3. Protocol
   4. Same Fragment Identifier

   *NOTE: Fragmentation is incompatible with very big Jumbograms. 
   (IP packets sized > 256 KiB)

CRC64 Checksum

   Consists of parts of the IP header, the FDP header, 
   and the data,  padded  with zero bytes  at the end (if  necessary)
   to  make  a multiple of two bytes.
   This checksum procedure is similar to what is used in TCP.64.

   If the computed  checksum  is zero,  it is transmitted  as all ones.
   An all zero  transmitted checksum  value means that the transmitter
   generated  no checksum  (for debugging or for higher level protocols
   that don't care or for ILNP purposes).

   Design note:
Show full document text