Ok. I assume this should be for FT? Or just something to get started?
Steve
-----Original Message-----
From: rfc-editor(_at_)rfc-editor(_dot_)org
[rfc-editor(_at_)rfc-editor(_dot_)org]
Received: Tuesday, 13 Aug 2013, 18:18
To: ietf-announce(_at_)ietf(_dot_)org [ietf-announce(_at_)ietf(_dot_)org];
rfc-dist(_at_)rfc-editor(_dot_)org [rfc-dist(_at_)rfc-editor(_dot_)org]
CC: drafts-update-ref(_at_)iana(_dot_)org
[drafts-update-ref(_at_)iana(_dot_)org]; ipv6(_at_)ietf(_dot_)org
[ipv6(_at_)ietf(_dot_)org]; rfc-editor(_at_)rfc-editor(_dot_)org
[rfc-editor(_at_)rfc-editor(_dot_)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(_at_)si6networks(_dot_)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(_at_)rfc-editor(_dot_)org.
Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC