datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

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

Active Internet-Draft (conex WG)
Document Stream: IETF
Last updated: 2013-03-28
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: WG Document (conex)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

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: September 29, 2013                  IKR University of Stuttgart
                                                               C. Ucendo
                                                              Telefonica
                                                          March 28, 2013

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

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 September 29, 2013.

Copyright Notice

   Copyright (c) 2013 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 September 29, 2013               [Page 1]
Internet-Draft          ConEx Destination Option              March 2013

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions used in this document . . . . . . . . . . . . . . . 3
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Requirements for marking IPv6 packets . . . . . . . . . . . . . 4
   5.  ConEx Destination Option (CDO)  . . . . . . . . . . . . . . . . 4
   6.  Implementation in the fast path of ConEx-aware routers  . . . . 6
   7.  Compatibility with use of IPsec . . . . . . . . . . . . . . . . 7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   11. Normative References  . . . . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

Krishnan, et al.       Expires September 29, 2013               [Page 2]
Internet-Draft          ConEx Destination Option              March 2013

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.

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

   The ConEx working group came up with a list of requirements that had
   to be met by any marking mechanism.  It then considered several
   alternative mechanisms and evaluated their suitability for ConEx
   marking.  There were no mechanisms found that were completely
   suitable, but the only mechanism that came close to meeting the
   requirements was IPv6 destination options.  The analysis of the
   different alternatives can be found in [draft-krishnan-conex-ipv6].

Krishnan, et al.       Expires September 29, 2013               [Page 3]