RE: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
Stephen Nadas <stephen.nadas@ericsson.com> Tue, 13 August 2013 22:28 UTC
Return-Path: <stephen.nadas@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D09F411E80D2; Tue, 13 Aug 2013 15:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cIe4-Kv+ZyJZ; Tue, 13 Aug 2013 15:28:11 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 8228621E816E; Tue, 13 Aug 2013 15:28:08 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-81-520ab2f716b9
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 13.E5.31362.7F2BA025; Wed, 14 Aug 2013 00:28:07 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Tue, 13 Aug 2013 18:28:06 -0400
From: Stephen Nadas <stephen.nadas@ericsson.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>, "rfc-dist@rfc-editor.org" <rfc-dist@rfc-editor.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
Thread-Topic: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
Thread-Index: AQHOmHMLv+csr4kx2UygNsGxX3IOGpmTt9wF
Date: Tue, 13 Aug 2013 22:28:05 +0000
Message-ID: <0BDF8C6F58AEFA45A013C71E4ADEB4AF02F2046A@eusaamb101.ericsson.se>
References: <20130813221321.AEA1AB1E003@rfc-editor.org>
In-Reply-To: <20130813221321.AEA1AB1E003@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_0BDF8C6F58AEFA45A013C71E4ADEB4AF02F2046Aeusaamb101erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPlO73TVxBBvc61Sxu/Whkt7h3Zjqb xbON81ksXp59z2SxYuJRNoum/V/ZHNg8euQ9liz5yeTR0HaMNYA5issmJTUnsyy1SN8ugStj /rmb7AW9jhXnWm8yNjC2WnQxcnJICJhI9K/qZIewxSQu3FvP1sXIxSEkcJRRov/iZ2YIZzmj xJHuG4wgVWwCBhL/e5awgNgiAv2MEn03uEGKmAVmMkrM+/6QDSQhLJAs8W33KkaIohSJjUcO QjUYSSzr2c4EYrMIqEr0Hp3EDGLzCvhKbL99GcwWEjCXOLXlJFgvp4CFxJfDG1lBbEag876f WgPWyywgLnHryXwmiLMFJJbsOc8MYYtKvHz8jxWiJl9i/62PjBDzBSVOznzCMoFRZBaS9llI ymYhKYOI60ncmDqFDcLWlli28DUzhK0rMePfIRZk8QWM7KsYOUqLU8ty040MNzEC4+2YBJvj DsYFnywPMUpzsCiJ827QOxMoJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgXHpbPfz0cfDqw4e 0j4icf7L7qoAjw3brlwVXzMnVCFu57SjbWGXXryLZmVgq1Jdcm7Cd8+Lt3Jlleoufq/L4T9f aBT9b/O7aZfjratKNRcJvSzj/MSqezXu9tFmwWvmYRP38Z/i47pUa/r4wJqCjHVKsQZrTpvc XmBzw8Z4h/mnCQ63uwPPKf1VYinOSDTUYi4qTgQA9jWvgoUCAAA=
X-Mailman-Approved-At: Tue, 13 Aug 2013 23:26:46 -0700
Cc: "drafts-update-ref@iana.org" <drafts-update-ref@iana.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 13 Aug 2013 22:28:19 -0000
Ok. I assume this should be for FT? Or just something to get started? Steve -----Original Message----- From: rfc-editor@rfc-editor.org [rfc-editor@rfc-editor.org] Received: Tuesday, 13 Aug 2013, 18:18 To: ietf-announce@ietf.org [ietf-announce@ietf.org]; rfc-dist@rfc-editor.org [rfc-dist@rfc-editor.org] CC: drafts-update-ref@iana.org [drafts-update-ref@iana.org]; ipv6@ietf.org [ipv6@ietf.org]; rfc-editor@rfc-editor.org [rfc-editor@rfc-editor.org] Subject: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery 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 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/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
- RFC 6980 on Security Implications of IPv6 Fragmen… rfc-editor
- RE: RFC 6980 on Security Implications of IPv6 Fra… Stephen Nadas