datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

IPv6 Destination Option for ConEx
draft-ietf-conex-destopt-08

Document type: Active Internet-Draft (conex WG)
Document stream: IETF
Last updated: 2014-11-10
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

ConEx Working Group                                          S. Krishnan
Internet-Draft                                                  Ericsson
Intended status: Experimental                              M. Kuehlewind
Expires: May 14, 2015                                         ETH Zurich
                                                                C. Ralli
                                                              Telefonica
                                                       November 10, 2014

                   IPv6 Destination Option for ConEx
                      draft-ietf-conex-destopt-08

Abstract

   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 May 14, 2015.

Copyright Notice

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

Krishnan, et al.          Expires May 14, 2015                  [Page 1]
Internet-Draft          ConEx Destination Option           November 2014

   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  . . .   6
   6.  Tunnel Processing . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Compatibility with use of IPsec . . . . . . . . . . . . . . .   7
   8.  Mitigating flooding attacks by using preferential drop  . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     12.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   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.  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 [ID.conex-tcp-modifications]).

   This specification is experimental to allow the IETF to assess
   whether the decision to implement the ConEx signal as a destination
   option fulfills the requirements stated in this document, as well as
   to evaluate the proposed encoding of the ConEx signals as described
   in [I-D.ietf-ConEx-abstract-mech].

   The duration of this experiment is expected to be no less than two
   years from publication of this document as infrastructure is needed

[include full document text]