RFC 7112 on Implications of Oversized IPv6 Header Chains

rfc-editor@rfc-editor.org Wed, 29 January 2014 17:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 09F591A037E; Wed, 29 Jan 2014 09:30:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Qb5UaXCHauMc; Wed, 29 Jan 2014 09:30:49 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id A80601A036A; Wed, 29 Jan 2014 09:30:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D475C7FC17B; Wed, 29 Jan 2014 09:30:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7112 on Implications of Oversized IPv6 Header Chains
From: rfc-editor@rfc-editor.org
Message-Id: <20140129173044.D475C7FC17B@rfc-editor.org>
Date: Wed, 29 Jan 2014 09:30:44 -0800
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 17:30:51 -0000

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

        RFC 7112

        Title:      Implications of Oversized IPv6 Header 
        Author:     F. Gont, V. Manral,
                    R. Bonica
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2014
        Mailbox:    fgont@si6networks.com, 
        Pages:      8
        Characters: 15897
        Updates:    RFC 2460

        I-D Tag:    draft-ietf-6man-oversized-header-chain-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7112.txt

The IPv6 specification allows IPv6 Header Chains of an arbitrary
size.  The specification also allows options that can, in turn,
extend each of the headers.  In those scenarios in which the IPv6
Header Chain or options are unusually long and packets are
fragmented, or scenarios in which the fragment size is very small,
the First Fragment of a packet may fail to include the entire IPv6
Header Chain.  This document discusses the interoperability and
security problems of such traffic, and updates RFC 2460 such that the
First Fragment of a packet is required to contain the entire IPv6
Header Chain.

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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