IETF Logo Mail Archive

RE: IPv4 outage at next IETF in Chicago

Michel Py <michel@arneill-py.sacramento.ca.us> Wed, 25 January 2017 03:11 UTC

Return-Path: <michel@arneill-py.sacramento.ca.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DCCA129636 for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 19:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.101
X-Spam-Level:
X-Spam-Status: No, score=-5.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 vC0s-co83foD for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 19:11:14 -0800 (PST)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [50.1.8.254]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4725129630 for <ietf@ietf.org>; Tue, 24 Jan 2017 19:11:13 -0800 (PST)
Received: from newserver.arneill-py.local ([fe80::e9e0:5b4:170e:c286]) by newserver.arneill-py.local ([fe80::e9e0:5b4:170e:c286%11]) with mapi id 14.03.0319.002; Tue, 24 Jan 2017 19:11:09 -0800
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: Christian Huitema <huitema@huitema.net>
Subject: RE: IPv4 outage at next IETF in Chicago
Thread-Topic: IPv4 outage at next IETF in Chicago
Thread-Index: AQG+jtYc44BqMJsJkp1R9/WxzQmWpALHtyGeoVoAj/CAABSEMA==
Date: Wed, 25 Jan 2017 03:11:08 +0000
Message-ID: <F04ED1585899D842B482E7ADCA581B8459489B47@newserver.arneill-py.local>
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <20170124235626.042F960836B0@rock.dv.isc.org> <158901d276b3$387d6050$a97820f0$@huitema.net>
In-Reply-To: <158901d276b3$387d6050$a97820f0$@huitema.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [96.81.169.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wxVF1VOxNgwPT4oRlNYeEPz_P5I>
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jan 2017 03:11:15 -0000

> Christian Huitema wrote :
> The blog explains that Microsoft IT wants to move their network to IPv6 only.

And I'm sure there is another quite helpful blog that explains why Microsoft IT wants to move to a Windows 10 only environment too.

Michel.

v2.23.0 | Report a Bug | By Email