IPv4 Extension Headers and Flow Label
draft-herbert-ipv4-eh-00

Document Type Active Internet-Draft (individual)
Last updated 2019-04-08
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                                                T. Herbert
Intended Status: Proposed Standard                            Quantonium
Expires: October 2019                                                   
                                                                        
                                                           April 8, 2019

                 IPv4 Extension Headers and Flow Label 
                        draft-herbert-ipv4-eh-00

Abstract

   This specification defines extension headers for IPv4 and a
   definition of an IPv4 flow label. The goal is to provide a uniform
   and feasible method of extensibility that is shared between IPv4 and
   IPv6.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

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

T. Herbert              Expires October 9, 2019                 [Page 1]
INTERNET DRAFT          draft-herbert-ipv4-eh-00           April 8, 2019

   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

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1 Motivation . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.2 IPv4 extension headers . . . . . . . . . . . . . . . . . . .  4
     1.3 The IPv4 flow label  . . . . . . . . . . . . . . . . . . . .  5
   2  IPv4 extension headers  . . . . . . . . . . . . . . . . . . . .  5
     2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . .  6
       2.1.1 General requirements . . . . . . . . . . . . . . . . . .  6
       2.1.2 Fragmentation and reassembly requirements  . . . . . . .  7
     2.2 Interaction with standard IPv4 mechanisms  . . . . . . . . .  7
       2.2.1 IPv4 options and IPv4 extension headers  . . . . . . . .  8
       2.2.2 IPv4 fragmentation and IPv4 extension headers  . . . . .  8
       2.2.3 Atomic datagram recommendation . . . . . . . . . . . . .  8
   3  The IPv4 flow label . . . . . . . . . . . . . . . . . . . . . .  9
     3.1 Sender requirements  . . . . . . . . . . . . . . . . . . . .  9
     3.2 Receiver requirements  . . . . . . . . . . . . . . . . . . .  9
   4  Deployability . . . . . . . . . . . . . . . . . . . . . . . . . 10
   5  Security Considerations . . . . . . . . . . . . . . . . . . . . 10
   6  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 11
   7  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1  Normative References  . . . . . . . . . . . . . . . . . . . 11
     7.2  Informative References  . . . . . . . . . . . . . . . . . . 12
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13

 

T. Herbert              Expires October 9, 2019                 [Page 2]
INTERNET DRAFT          draft-herbert-ipv4-eh-00           April 8, 2019

1  Introduction

   This specification defines extension headers for IPv4 as well as an
   IPv4 flow label. The motivation is to provide an extensible mechanism
   in IPv4 that is unified with IPv6 and thus facilitates leveraging
   common protocol and implementation for extensibility between the two
   versions of the Internet Protocol.

   The extension headers defined for IPv6 in [RFC8200], specifically
   Hop-by-Hop Options, Destination Options, Routing Header, and Fragment
   Header are permitted for use with IPv4 (note that Authentication
   Header and Encapsulating Security Payload are already usable with
   IPv4). Additionally, No Next Header (protocol number 59) is defined
Show full document text