[BEHAVE] [Technical Errata Reported] RFC6145 (3061)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 23 December 2011 11:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0AB21F8B2B for <behave@ietfa.amsl.com>; Fri, 23 Dec 2011 03:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.388
X-Spam-Level:
X-Spam-Status: No, score=-102.388 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 lS3breR3UBF5 for <behave@ietfa.amsl.com>; Fri, 23 Dec 2011 03:21:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A65F321F8B0F for <behave@ietf.org>; Fri, 23 Dec 2011 03:21:18 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9759872E008; Fri, 23 Dec 2011 03:19:47 -0800 (PST)
To: xing@cernet.edu.cn, congxiao@cernet.edu.cn, fred@cisco.com, ietfdbh@comcast.net, wes@mti-systems.com, dthaler@microsoft.com, dwing@cisco.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20111223111948.9759872E008@rfc-editor.org>
Date: Fri, 23 Dec 2011 03:19:47 -0800
Cc: gandhar.gokhale@lsi.com, behave@ietf.org, rfc-editor@rfc-editor.org
Subject: [BEHAVE] [Technical Errata Reported] RFC6145 (3061)
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Dec 2011 11:21:19 -0000
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 <gandhar.gokhale@lsi.com> 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
- [BEHAVE] [Technical Errata Reported] RFC6145 (306… RFC Errata System
- Re: [BEHAVE] [Technical Errata Reported] RFC6145 … Gokhale, Gandhar
- Re: [BEHAVE] [Technical Errata Reported] RFC6145 … Alice Hagens
- Re: [BEHAVE] [Technical Errata Reported] RFC6145 … Gokhale, Gandhar