RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery

rfc-editor@rfc-editor.org Tue, 13 August 2013 22:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6E28521E8167; Tue, 13 Aug 2013 15:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.4
X-Spam-Status: No, score=-100.4 tagged_above=-999 required=5 tests=[AWL=1.600, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 6TTMTf+p1x82; Tue, 13 Aug 2013 15:17:38 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id DED5821E8051; Tue, 13 Aug 2013 15:17:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AEA1AB1E003; Tue, 13 Aug 2013 15:13:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
From: rfc-editor@rfc-editor.org
Message-Id: <20130813221321.AEA1AB1E003@rfc-editor.org>
Date: Tue, 13 Aug 2013 15:13:21 -0700
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 13 Aug 2013 22:17:39 -0000

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

        RFC 6980

        Title:      Security Implications of IPv6 Fragmentation 
                    with IPv6 Neighbor Discovery 
        Author:     F. Gont
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2013
        Mailbox:    fgont@si6networks.com
        Pages:      10
        Characters: 20850
        Updates:    RFC 3971, RFC 4861

        I-D Tag:    draft-ietf-6man-nd-extension-headers-05.txt

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

This document analyzes the security implications of employing IPv6
fragmentation with Neighbor Discovery (ND) messages.  It updates RFC
4861 such that use of the IPv6 Fragmentation Header is forbidden in
all Neighbor Discovery messages, thus allowing for simple and
effective countermeasures for Neighbor Discovery attacks.  Finally,
it discusses the security implications of using IPv6 fragmentation
with SEcure Neighbor Discovery (SEND) and formally updates RFC 3971
to provide advice regarding how the aforementioned security
implications can be mitigated.

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