Re: Predictable IP protocol values

Fernando Gont <fgont@si6networks.com> Sat, 28 April 2012 03:31 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF97221E8029 for <ipv6@ietfa.amsl.com>; Fri, 27 Apr 2012 20:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 r3Y1CpRbaMt2 for <ipv6@ietfa.amsl.com>; Fri, 27 Apr 2012 20:31:29 -0700 (PDT)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBB221E8027 for <ipv6@ietf.org>; Fri, 27 Apr 2012 20:31:28 -0700 (PDT)
Received: from [186.134.11.143] (helo=[192.168.123.103]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1SNyNU-0002Lm-Bb; Sat, 28 Apr 2012 05:31:20 +0200
Message-ID: <4F9B61E5.1020109@si6networks.com>
Date: Sat, 28 Apr 2012 00:20:05 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Ole_Tr=F8an?= <otroan@employees.org>
Subject: Re: Predictable IP protocol values
References: <401EA98A-C229-4ED3-8CBE-3C6CAE5D37B7@gmail.com> <4F87BBD6.8090809@si6networks.com> <5858DFD5-7A62-478E-8F13-B62CB02D3EE7@employees.org> <4F99B5C8.1010108@si6networks.com> <5E6FD71A-0A84-4B20-AF5A-16DCBCD7ED76@employees.org>
In-Reply-To: <5E6FD71A-0A84-4B20-AF5A-16DCBCD7ED76@employees.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Bob Hinden <bob.hinden@gmail.com>, "ipv6@ietf.org Mailing List" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Apr 2012 03:31:30 -0000

Hi, Ole,

On 04/27/2012 05:21 AM, Ole Trøan wrote:
> working group,
> 
> [changed subject]
> 
> in the context of http://tools.ietf.org/html/draft-gont-6man-predictable-fragment-id-02
> any opinion on how to proceed?
> 
> - document covering predictable values in IETF protocols in general

I don't think such a document could formally update in protocol that
should be using unpredictable IDs, since the contraints are different
for each protocol.


> - document predictable IP ID fields in both IPv4 and IPv6

This one *could* make sense, however, the constraints are somewhat
different, and procedurally-wise, it may be simpler to work on this I-D
here, than having an I-D that spans 6man and intarea wg(?).


> - fix the predictable fragment ID problem in IPv6

I'd obviously go with this one.


> - do nothing?

Hopefully not -- if we don't fix this, who would do it? -- Even vendors
have been responsive to this I-D, so one would expect that we do
something about it.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492