[Roll] FW: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 03 October 2013 08:50 UTC

From: Adrian Farrel <adrian@olddog.co.uk>
To: roll@ietf.org
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
In-Reply-To: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
Date: Thu, 03 Oct 2013 09:48:32 +0100
Message-ID: <031201cec015$579f31a0$06dd94e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQH0d2L6ZdDWbm+Vxt1g3seAlz4BR5mXO69w
Content-Language: en-gb
Subject: [Roll] FW: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Precedence: list
Reply-To: adrian@olddog.co.uk, Routing Over Low power and Lossy networks <roll@ietf.org>

I think that Some of you in ROLL should look at this document (which is in IETF
last call) just to make sure that there is no conflict with RPL.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 02 October 2013 19:55
> To: IETF-Announce
> Cc: ipv6@ietf.org
> Subject: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
(Implications
> of Oversized IPv6 Header Chains) to Proposed Standard
> 
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Implications of Oversized IPv6 Header Chains'
>   <draft-ietf-6man-oversized-header-chain-08.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-10-16. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    The IPv6 specification allows IPv6 header chains of an arbitrary
>    size.  The specification also allows options which 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.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.

[Roll] FW: Last Call: <draft-ietf-6man-oversized-… Adrian Farrel