Subject: [BEHAVE] [Technical Errata Reported] RFC6145 (3061)

From: RFC Errata System <[email-masked]>
Date: Fri, 23 Dec 2011 03:19:47 -0800 (PST)

The following errata report has been submitted for RFC6145,
"IP/ICMP Translation Algorithm".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6145&eid=3061

--------------------------------------
Type: Technical
Reported by: Gandhar Gokhale <[email-masked]>

Section: 5.1.1

Original Text
-------------
Fragment Offset:  Copied from the Fragment Offset field of the IPv6 Fragment Header.

Corrected Text
--------------
Fragment Offset:  If the Next Header field of the Fragment Header is not an extension header (except ESP) then Fragment Offset MUST be copied from the Fragment Offset field of the IPv6 Fragment Header. If the Next Header field of the Fragment Header is an extension header (except ESP) then the packet SHOULD be dropped and logged.

Notes
-----
If the fragmentable part (as described in RFC 2460) of the original unfragmented IPv6 packet had extension headers then the translator can not calculate the offset of the IPv4 fragment for non-initial fragments. If extension headers are present in the fragmentable part then the fragment offset value of the IPv6 header includes length of the extension headers also. Since translator strips of the IPv6 extension headers the fragment offset value set by the sender of IPv6 fragments can not match that received by the IPv4 receiver and the reassembly will fail. For non-initial fragments the translator does not have the knowledge of this delta when there is no state maintained.

The legth issue stated in erratum 2 is not in itself sufficient to advocate packet drop. However, the offset issue is sufficient to advocate packet drop as the reassembly is bound to fail. Therefore I'm putting a SHOULD in both cases.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6145 (draft-ietf-behave-v6v4-xlate-23)
--------------------------------------
Title               : IP/ICMP Translation Algorithm
Publication Date    : April 2011
Author(s)           : X. Li, C. Bao, F. Baker
Category            : PROPOSED STANDARD
Source              : Behavior Engineering for Hindrance Avoidance
Area                : Transport
Stream              : IETF
Verifying Party     : IESG