Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard

Masataka Ohta <> Mon, 13 August 2012 09:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 55B0321F86D5 for <>; Mon, 13 Aug 2012 02:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.049
X-Spam-Status: No, score=-0.049 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0xOB0CezJDw5 for <>; Mon, 13 Aug 2012 02:46:08 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id 7E62421F8712 for <>; Mon, 13 Aug 2012 02:46:08 -0700 (PDT)
Received: (qmail 1144 invoked from network); 13 Aug 2012 09:44:36 -0000
Received: from (HELO ? ( by with SMTP; 13 Aug 2012 09:44:36 -0000
Message-ID: <>
Date: Mon, 13 Aug 2012 18:45:29 +0900
From: Masataka Ohta <>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Joe Touch <>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 13 Aug 2012 09:46:09 -0000

Joe Touch wrote:

> Again, this doc is about updating the IPv4 ID specification in RFC791 -
> which has not yet been updated.

But, the way you update rfc791 requires updating rfc2460,
rfc2765 and their implementations, for which there is no

That is, though your draft claims to "more closely reflect
current practice" and "more closely match IPv6", the way you
update rfc791 does not "reflect current practice" nor "match

As your draft states:

   it is clear that
   existing systems violate the current specification

and rfc2026 states:

   4.1.3  Internet Standard
   A specification for which significant implementation and successful
   operational experience has been obtained may be elevated to the
   Internet Standard level.

there is no point to insist on the ID uniqueness requirement of
rfc791 as a requirement of an Internet Standard.

> The IPv6-IPv4 translation that creates IPv4 IDs is currently
> non-compliant with RFC791 and does not override RFC791. This document's
> update might make that translation easier,


Insisting on rfc791 makes the translation a lot harder than
just "closely reflect current practice" to loosen uniqueness
request of rfc791, which is what almost all (if not all) the
IPv4 and IPv6 implementations today are doing.

> If you disagree with that conclusion, please contact the INTAREA WG
> chairs directly.

As we are in IETF last call stage, I can see no point you
insist on the original conclusion of the WG, which
overlooked the complication caused by 6->4 translation.

						Masataka Ohta