An IPv4 Flowlabel Option
draft-dreibholz-ipv4-flowlabel-26

Document Type Active Internet-Draft (individual)
Last updated 2017-08-06
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)
Network Working Group                                       T. Dreibholz
Internet-Draft                                Simula Research Laboratory
Intended status: Standards Track                         August 06, 2017
Expires: February 7, 2018

                        An IPv4 Flowlabel Option
                 draft-dreibholz-ipv4-flowlabel-26.txt

Abstract

   This draft defines an IPv4 option containing a flowlabel that is
   compatible to IPv6.  It is required for simplified usage of IntServ
   and interoperability with IPv6.

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 February 7, 2018.

Copyright Notice

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

Dreibholz               Expires February 7, 2018                [Page 1]
Internet-Draft          An IPv4 Flowlabel Option             August 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   2
     1.3.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  A Flow Label Option for IPv4  . . . . . . . . . . . . . . . .   3
     2.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  The Flow Label Field of IPv6  . . . . . . . . . . . .   3
       2.1.2.  The Limitations of IntServ via IPv4 . . . . . . . . .   4
     2.2.  Definition of the Flow Label Option . . . . . . . . . . .   5
   3.  Translation between IPv6 and IPv4 . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

1.1.  Terminology

   This document uses the following terms:

   o  IntServ (Integrated Services): Reservation of network resources
      (bandwidth) on a per-flow basis.  See [RFC1633], [RFC2205],
      [RFC2208], [RFC2209], [RFC2210], [RFC2211] and [RFC2212] for
      details.

   o  Flow: An IntServ reservation between two endpoints.

   o  Flow Label: The Flow Label field of the IPv6 header and the IPv4
      option header defined in this draft.  It is used for marking a
      packet to use a specific IntServ reservation.  See [RFC6437],
      [RFC6436] for detailed descriptions.

1.2.  Abbreviations

   o  RSVP: ReSource Reservation Protocol

   o  SCTP: Stream Control Transmission Protocol

   o  TCP: Transmission Control Protocol

   o  QoS: Quality of Service

Dreibholz               Expires February 7, 2018                [Page 2]
Internet-Draft          An IPv4 Flowlabel Option             August 2017

   o  UDP: User Datagram Protocol

1.3.  Conventions

   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 [RFC2119].

2.  A Flow Label Option for IPv4

2.1.  Motivation

   This section describes the motivation to add a flow label option to
   the IPv4 protocol.

2.1.1.  The Flow Label Field of IPv6

   The Flow Label field (see [RFC6436] and [RFC6437]) of the IPv6 header
   (see [RFC2460]) is a 20-bit number.  All packets from the same source
   address having the same flow label MUST contain the same destination
   address.  Therefore, the flow label combined with the source address
Show full document text