Re: Fragment ID generation in Windows (Re: draft-ietf-6man-predictable-fragment-id-04.txt)

Fernando Gont <fgont@si6networks.com> Sun, 22 March 2015 18:26 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 056AC1A004D for <ipv6@ietfa.amsl.com>; Sun, 22 Mar 2015 11:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.31
X-Spam-Level:
X-Spam-Status: No, score=-0.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 2iXosYYY_Uzo for <ipv6@ietfa.amsl.com>; Sun, 22 Mar 2015 11:26:17 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E751A001A for <ipv6@ietf.org>; Sun, 22 Mar 2015 11:26:16 -0700 (PDT)
Received: from ip65-46-187-134.z187-46-65.customer.algx.net ([65.46.187.134] helo=[192.168.198.174]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YZkZe-0007Fb-5J; Sun, 22 Mar 2015 19:26:12 +0100
Message-ID: <550EC9B9.6020105@si6networks.com>
Date: Sun, 22 Mar 2015 14:55:05 +0100
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Stephen Bensley <sbens@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: Fragment ID generation in Windows (Re: draft-ietf-6man-predictable-fragment-id-04.txt)
References: <BN1PR03MB023F8922776167C7B1C5B9DA8010@BN1PR03MB023.namprd03.prod.outlook.com>
In-Reply-To: <BN1PR03MB023F8922776167C7B1C5B9DA8010@BN1PR03MB023.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5PfCitQIk7gCvymOzvw3WApAi0w>
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: <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: Sun, 22 Mar 2015 18:26:19 -0000

Hi, Stephen,

Thanks so much for your feedback! Please find my comments inline...

On 03/19/2015 06:56 PM, Stephen Bensley wrote:
> 
> I work on the TCP/IP stack in Windows. In Windows 8, we implemented
> the algorithm described in section 4.3 of this draft. Appendix B
> should be updated accordingly.

Has this been implemented since the very first release of Windows 8? O
was this later implemented in some e.g. service pack?

Thanks!

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