[conex] RFC 7837 on IPv6 Destination Option for Congestion Exposure (ConEx)

rfc-editor@rfc-editor.org Fri, 13 May 2016 17:43 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: conex@ietfa.amsl.com
Delivered-To: conex@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC3E812D658; Fri, 13 May 2016 10:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5anu_WlBWmwz; Fri, 13 May 2016 10:43:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50A1B12D64C; Fri, 13 May 2016 10:43:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B1855180004; Fri, 13 May 2016 10:42:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160513174249.B1855180004@rfc-editor.org>
Date: Fri, 13 May 2016 10:42:49 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/conex/UDG_mLMXdB3DnBILKotJHeh-3jU>
Cc: drafts-update-ref@iana.org, conex@ietf.org, rfc-editor@rfc-editor.org
Subject: [conex] RFC 7837 on IPv6 Destination Option for Congestion Exposure (ConEx)
X-BeenThere: conex@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Congestion Exposure working group discussion list <conex.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/conex>, <mailto:conex-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/conex/>
List-Post: <mailto:conex@ietf.org>
List-Help: <mailto:conex-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/conex>, <mailto:conex-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 17:43:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7837

        Title:      IPv6 Destination Option for Congestion 
                    Exposure (ConEx) 
        Author:     S. Krishnan, M. Kuehlewind,
                    B. Briscoe, C. Ralli
        Status:     Experimental
        Stream:     IETF
        Date:       May 2016
        Mailbox:    suresh.krishnan@ericsson.com, 
                    mirja.kuehlewind@tik.ee.ethz.ch, 
                    ietf@bobbriscoe.net,
                    ralli@tid.es
        Pages:      13
        Characters: 29708
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-conex-destopt-12.txt

        URL:        https://www.rfc-editor.org/info/rfc7837

        DOI:        http://dx.doi.org/10.17487/RFC7837

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.

This document is a product of the Congestion Exposure Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC