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

[Stephen Nadas]

Ok. I assume this should be for FT? Or just something to get started?
Steve

-Original Message-
From: rfc-edi...@rfc-editor.org [rfc-edi...@rfc-editor.org]
Received: Tuesday, 13 Aug 2013, 18:18
To: ietf-annou...@ietf.org [ietf-annou...@ietf.org]; rfc-d...@rfc-editor.org 
[rfc-d...@rfc-editor.org]
CC: drafts-update-...@iana.org [drafts-update-...@iana.org]; i...@ietf.org 
[i...@ietf.org]; rfc-edi...@rfc-editor.org [rfc-edi...@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:fg...@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-edi...@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

Re: fragmentation?

[Rahmat M. Samik-Ibrahim]

Hello:

> If you have not seen Dave Clark's RFC on reassembly, you have
> missed something.  Do you need an RFC #? It was one of the famous
> "Dave Clark 5" RFCs, somewhere in the later 800s as I remember.

0815 IP datagram reassembly algorithms. D.D. Clark. Jul-01-1982.
 (Format: TXT=14575 bytes) (Status: UNKNOWN)

See also http://www.ietf.org/rfc/rfc0815.txt


Gong Xi Fa Cai, 
Hong Bao Na Lai 
(=a prosperous millennium :-),

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Da da da ich lieb dich nicht du liebst mich nicht aha -- TRIO82 -

Re: fragmentation?

[Bob Braden]

  *> From [EMAIL PROTECTED] Wed Feb  2 19:38:12 2000
  *> Date: Wed, 2 Feb 2000 22:38:10 -0500 (EST)
  *> From: Hari Bapiraju Gadi <[EMAIL PROTECTED]>
  *> To: Bob Braden <[EMAIL PROTECTED]>
  *> cc: [EMAIL PROTECTED]
  *> Subject: Re: fragmentation?
  *> In-Reply-To: <[EMAIL PROTECTED]>
  *> MIME-Version: 1.0
  *> X-Lines: 19
  *> 
  *> Dear Mr.Braden,
  *> I meant both fragmentation as well as reassembly.
  *> I was looking at linux implementation, its good enough.
  *> 
  *> But I wanted to make sure that I was not missing anything.

If you have not seen Dave Clark's RFC on reassembly, you have
missed something.  Do you need an RFC #? It was one of the famous
"Dave Clark 5" RFCs, somewhere in the later 800s as I remember.

Bob

Re: fragmentation?

[Hari Bapiraju Gadi]

Dear Mr.Braden,
I meant both fragmentation as well as reassembly.
I was looking at linux implementation, its good enough.

But I wanted to make sure that I was not missing anything.

Thanks for your reply,
Hari B.Gadi.

On Thu, 3 Feb 2000,
Bob
Braden wrote:

> 
> Fragmentation is trivial; it is reassembly that is tricky.
> 
> Bob Braden
> 

fragmentation?

[Hari Bapiraju Gadi]

Hello,

Apart from RFC 791 and RFC 815, are there any RFC's talking about
fragmentaion algorithms.Does anyone know good resources about fragmention
and their implementation code.

Thanks,

Hari B.Gadi