IETF Logo Mail Archive

RE: IPv4 Outage Planned for IETF 71 Plenary

Christian Huitema <huitema@windows.microsoft.com> Sat, 15 December 2007 06:58 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Qys-0007L5-Fd; Sat, 15 Dec 2007 01:58:38 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3Qyr-0007Kz-Jc for ietf@ietf.org; Sat, 15 Dec 2007 01:58:37 -0500
Received: from mailb.microsoft.com ([131.107.115.215] helo=smtp.microsoft.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3Qyr-0001tR-5y for ietf@ietf.org; Sat, 15 Dec 2007 01:58:37 -0500
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.70.72) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.1.222.3; Fri, 14 Dec 2007 22:58:36 -0800
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com (157.54.70.14) by TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.70.72) with Microsoft SMTP Server id 8.1.222.3; Fri, 14 Dec 2007 22:58:36 -0800
Received: from NA-EXMSG-W602.wingroup.windeploy.ntdev.microsoft.com ([157.54.62.196]) by tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([::1]) with mapi; Fri, 14 Dec 2007 22:58:36 -0800
From: Christian Huitema <huitema@windows.microsoft.com>
To: Edward Lewis <Ed.Lewis@neustar.biz>, Paul Hoffman <paul.hoffman@vpnc.org>
Date: Fri, 14 Dec 2007 22:58:34 -0800
Thread-Topic: IPv4 Outage Planned for IETF 71 Plenary
Thread-Index: Acg+uPHb0wITPQkSQq+2NBfFRylH8gALkvTA
Message-ID: <AFE0AC8DCDE68842B94E8EC69D5F21D6330AD0F100@NA-EXMSG-W602.wingroup.windeploy.ntdev.microsoft.com>
References: <E1J3IFS-0002yV-CG@ietf.org> <20071214220518.GA14379@sources.org> <47631201.1070303@bogus.com> <p06240806c388d88dc9de@[165.227.249.204]> <a06240800c388daca0917@[192.168.1.101]>
In-Reply-To: <a06240800c388daca0917@[192.168.1.101]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: -108.0 (---------------------------------------------------)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IPv4 Outage Planned for IETF 71 Plenary
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

> >Maybe reports of "the DNS is broken when you do go to pure IPv6" are
> >more valuable than "you can only go to IPv6 if you jump through these
> >hoops that only advanced Internet users can do".
>
> Is the IETF afraid to eat it's own food?
> Or is it willing to do what's necessary (in the interim) to adjust to
> the new cuisine?

Our networking team at Microsoft did run an "IPv6 only" trial during the development of Windows Vista. Volunteers only. The volunteers would disable the IPv4 stacks on their PC, and then attempt to go on with their normal work, both for internal applications such as corporate mail, file servers, or intranet servers, and for external applications, mostly web based. It worked, but it had to rely on a set of transport proxies for those internal applications that were not yet IPv6 ready, and of course web proxies for internal access.

-- Christian Huitema




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email