IPv6 Destination Option for Congestion Exposure (ConEx)
draft-ietf-conex-destopt-12

Document Type Active Internet-Draft (conex WG)
Last updated 2016-02-03 (latest revision 2016-01-17)
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Dirk Kutscher
Shepherd write-up Show (last changed 2015-05-08)
IESG IESG state RFC Ed Queue
Consensus Yes
Telechat date
Responsible AD Martin Stiemerling
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state AUTH48
ConEx Working Group                                          S. Krishnan
Internet-Draft                                                  Ericsson
Intended status: Experimental                              M. Kuehlewind
Expires: July 21, 2016                                        ETH Zurich
                                                              B. Briscoe
                                              Simula Research Laboratory
                                                                C. Ralli
                                                              Telefonica
                                                        January 18, 2016

        IPv6 Destination Option for Congestion Exposure (ConEx)
                      draft-ietf-conex-destopt-12

Abstract

   Congestion Exposure (ConEx) is a mechanism by which senders inform
   the network about the congestion encountered by packets earlier in
   the same flow.  This document specifies an IPv6 destination option
   that is capable of carrying ConEx markings in IPv6 datagrams.

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 July 21, 2016.

Copyright Notice

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

Krishnan, et al.          Expires July 21, 2016                 [Page 1]
Internet-Draft          ConEx Destination Option            January 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Requirements for the coding of ConEx in IPv6  . . . . . . . .   3
   4.  ConEx Destination Option (CDO)  . . . . . . . . . . . . . . .   4
   5.  Implementation in the fast path of ConEx-aware routers  . . .   7
   6.  Tunnel Processing . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Compatibility with use of IPsec . . . . . . . . . . . . . . .   8
   8.  Mitigating flooding attacks by using preferential drop  . . .   9
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     12.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Congestion Exposure (ConEx) [I-D.ietf-conex-abstract-mech] is a
   mechanism by which senders inform the network about the congestion
   encountered by packets earlier in the same flow.  This document
   specifies an IPv6 destination option [RFC2460] that can be used for
   performing ConEx markings in IPv6 datagrams.

   This document specifies the ConEx wire protocol in IPv6.  The ConEx
   information can be used by any network element on the path to e.g. do
   traffic management or egress policing.  Additionally this information
   will potentially be used by an audit function that checks the
   integrity of the sender's signaling.  Further each transport
   protocol, that supports ConEx signaling, will need to specify
   precisely when the transport sets ConEx markings (e.g. the behavior
   for TCP is specified in [I-D.ietf-conex-tcp-modifications]).

   This document specifies ConEx for IPv6 only.  Due to space
   limitations in the IPv4 header and the risk of options that might be
   stripped by middlebox in IPv4 the primary goal of the working goal
Show full document text