datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

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

Document type: Active Internet-Draft (conex WG)
Document stream: IETF
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, xml, 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: Standards Track                           M. Kuehlewind
Expires: August 18, 2014                     IKR University of Stuttgart
                                                               C. Ucendo
                                                              Telefonica
                                                       February 14, 2014

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

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 August 18, 2014.

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 August 18, 2014                [Page 1]
Internet-Draft          ConEx Destination Option           February 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 . . . . . . . . . . . . . .   2
   3.  Requirements for the coding of ConEx in IPv6  . . . . . . . .   2
   4.  ConEx Destination Option (CDO)  . . . . . . . . . . . . . . .   3
   5.  Implementation in the fast path of ConEx-aware routers  . . .   5
   6.  Compatibility with use of IPsec . . . . . . . . . . . . . . .   6
   7.  DDoS mitigation by using preferential drop  . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   ConEx [CAM] 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.

   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.

2.  Conventions used in this document

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

3.  Requirements for the coding of ConEx in IPv6

   R-1: The marking mechanism needs to be visible to all ConEx-capable
   nodes on the path.

   R-2: The mechanism needs to be able to traverse nodes that do not
   understand the markings.  This is required to ensure that ConEx can
   be incrementally deployed over the Internet.

   R-3: The presence of the marking mechanism should not significantly
   alter the processing of the packet.  This is required to ensure that

Krishnan, et al.         Expires August 18, 2014                [Page 2]

[include full document text]