IETF Logo Mail Archive

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

Stephen Bensley <sbens@microsoft.com> Mon, 23 March 2015 14:29 UTC

Return-Path: <sbens@microsoft.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 DD9DF1A8ADB for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2015 07:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 nwsTZG2pDz_Q for <ipv6@ietfa.amsl.com>; Mon, 23 Mar 2015 07:29:50 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0111.outbound.protection.outlook.com [207.46.100.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49D2D1A8AD9 for <ipv6@ietf.org>; Mon, 23 Mar 2015 07:29:50 -0700 (PDT)
Received: from BN1PR03MB023.namprd03.prod.outlook.com (10.255.224.41) by BN1PR03MB021.namprd03.prod.outlook.com (10.255.224.39) with Microsoft SMTP Server (TLS) id 15.1.125.14; Mon, 23 Mar 2015 14:29:49 +0000
Received: from BN1PR03MB023.namprd03.prod.outlook.com ([169.254.15.199]) by BN1PR03MB023.namprd03.prod.outlook.com ([169.254.15.199]) with mapi id 15.01.0125.002; Mon, 23 Mar 2015 14:29:49 +0000
From: Stephen Bensley <sbens@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Fragment ID generation in Windows (Re: draft-ietf-6man-predictable-fragment-id-04.txt)
Thread-Topic: Fragment ID generation in Windows (Re: draft-ietf-6man-predictable-fragment-id-04.txt)
Thread-Index: AdBibV2chvlKISP+Tjuryn+YE+RJegCOm8SAADN86lA=
Date: Mon, 23 Mar 2015 14:29:48 +0000
Message-ID: <BN1PR03MB02311E502A2A6E8122EB88AA80D0@BN1PR03MB023.namprd03.prod.outlook.com>
References: <BN1PR03MB023F8922776167C7B1C5B9DA8010@BN1PR03MB023.namprd03.prod.outlook.com> <550EC9B9.6020105@si6networks.com>
In-Reply-To: <550EC9B9.6020105@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e0:ee43::2]
authentication-results: si6networks.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN1PR03MB021;
x-microsoft-antispam-prvs: <BN1PR03MB021DD93D649810CA02642A5A80D0@BN1PR03MB021.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(41574002)(13464003)(479174004)(377454003)(24454002)(51704005)(252514010)(230783001)(86362001)(86612001)(2501003)(33656002)(99286002)(122556002)(76576001)(46102003)(40100003)(74316001)(77156002)(2950100001)(2900100001)(76176999)(50986999)(107886001)(102836002)(2656002)(92566002)(87936001)(62966003)(54356999)(19580395003)(19580405001)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR03MB021; H:BN1PR03MB023.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BN1PR03MB021; BCL:0; PCL:0; RULEID:; SRVR:BN1PR03MB021;
x-forefront-prvs: 05245CA661
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Mar 2015 14:29:48.8919 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR03MB021
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Hg6v--BLsMhuDGJg4F-Clus4uzg>
X-Mailman-Approved-At: Mon, 23 Mar 2015 07:51:14 -0700
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: Mon, 23 Mar 2015 14:29:55 -0000

It was implemented in the very first release of Windows 8.

-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com] 
Sent: Sunday, March 22, 2015 6:55 AM
To: Stephen Bensley; ipv6@ietf.org
Subject: Re: Fragment ID generation in Windows (Re: draft-ietf-6man-predictable-fragment-id-04.txt)

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

v2.23.0 | Report a Bug | By Email