Re: rfc2460bis and Frag ID generation
Fernando Gont <fgont@si6networks.com> Thu, 04 February 2016 20:16 UTC
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3199E1AD074 for <ipv6@ietfa.amsl.com>; Thu, 4 Feb 2016 12:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PaqvM8uisRhn for <ipv6@ietfa.amsl.com>; Thu, 4 Feb 2016 12:16:50 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 469F01AD05F for <6man@ietf.org>; Thu, 4 Feb 2016 12:16:50 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id E74E6206AC2; Thu, 4 Feb 2016 21:16:46 +0100 (CET)
Subject: Re: rfc2460bis and Frag ID generation
To: Bob Hinden <bob.hinden@gmail.com>
References: <56B39FB8.4090604@si6networks.com> <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com> <56B3A990.9070000@si6networks.com> <2E3B4659-E282-4AF5-810D-EB951E1A3F13@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B3B1A0.4060503@si6networks.com>
Date: Thu, 04 Feb 2016 17:16:32 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2E3B4659-E282-4AF5-810D-EB951E1A3F13@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PvyeakCtULmLiWAnIh1L6BVja4Y>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 04 Feb 2016 20:16:54 -0000
On 02/04/2016 05:05 PM, Bob Hinden wrote: > Fernanco, > >> On Feb 4, 2016, at 11:42 AM, Fernando Gont <fgont@si6networks.com> wrote: >> >> On 02/04/2016 04:24 PM, Bob Hinden wrote: >> [....] >>>> >>>> Thoughts? >>> >>> I looked at this earlier and also thought the 32-bit wrap around >>> counter text was dated. I am OK with something similar to what you >>> proposed. My read of the current text is that it is describes the >>> 32-bit wrap around counter as an example, as opposed the only way to >>> do it, so an update like this would be OK. >>> >>> Other comments? >> >> BTW, please let me know if the current version will not be revised in >> less than, say, 1 week, and I could do a full review…. > > Not sure, other than this possible change, I don’t have anything else queued up. I meant... if the I-D is going to be stable for a few days, I can do a complete review. Otherwise I'd wait for the next rev, so that I review the updated doc... Cheers, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- rfc2460bis and Frag ID generation Fernando Gont
- Re: rfc2460bis and Frag ID generation Fernando Gont
- Re: rfc2460bis and Frag ID generation Bob Hinden
- Re: rfc2460bis and Frag ID generation Fernando Gont
- Re: rfc2460bis and Frag ID generation Fernando Gont
- Re: rfc2460bis and Frag ID generation Bob Hinden
- Re: rfc2460bis and Frag ID generation Bob Hinden
- Re: rfc2460bis and Frag ID generation Fernando Gont