Forward: RFC 5722 on Handling of Overlapping IPv6 Fragments

RFC Editor <rfc-editor@rfc-editor.org> Wed, 24 February 2010 00:20 UTC

Return-Path: <rfc-ed@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F31328C3CF for <ietf-announce@core3.amsl.com>; Tue, 23 Feb 2010 16:20:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.249, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id viK-yyM0va9l for <ietf-announce@core3.amsl.com>; Tue, 23 Feb 2010 16:20:01 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 8DC7528C3D2 for <ietf-announce@ietf.org>; Tue, 23 Feb 2010 16:19:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 6000) id 6A236130001; Tue, 23 Feb 2010 16:22:03 -0800 (PST)
Date: Tue, 23 Feb 2010 16:22:03 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: Forward: RFC 5722 on Handling of Overlapping IPv6 Fragments
Message-ID: <20100224002203.GD22574@rfc-editor.org>
References: <20091223184547.E200138E026@bosco.isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20091223184547.E200138E026@bosco.isi.edu>
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 00:20:02 -0000

Greetings All,

Please note that we are resending this RFC announcement because were
notified that it did not appear in the ietf-announce archives. 	Please
note that the date of publication is December 2009.

Please let us know if you have any questions.

Thank you.

RFC Editor/sg


On Wed, Dec 23, 2009 at 10:45:47AM -0800, RFC Editor wrote:
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>         
>         RFC 5722
> 
>         Title:      Handling of Overlapping IPv6 Fragments 
>         Author:     S. Krishnan
>         Status:     Standards Track
>         Date:       December 2009
>         Mailbox:    suresh.krishnan@ericsson.com
>         Pages:      6
>         Characters: 11838
>         Updates:    RFC2460
> 
>         I-D Tag:    draft-ietf-6man-overlap-fragment-03.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc5722.txt
> 
> The fragmentation and reassembly algorithm specified in the base IPv6
> specification allows fragments to overlap.  This document
> demonstrates the security issues associated with allowing overlapping 
> fragments and updates the IPv6 specification to explicitly forbid 
> overlapping fragments.  [STANDARDS TRACK]
> 
> This document is a product of the IPv6 Maintenance Working Group of the IETF.
> 
> This is now a Proposed Standard Protocol.
> 
> 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
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> 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
> USC/Information Sciences Institute
>