RE: IPv4 Outage Planned for IETF 71 Plenary

"Hallam-Baker, Phillip" <pbaker@verisign.com> Fri, 21 December 2007 15:37 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 1J5jwh-0008FQ-If; Fri, 21 Dec 2007 10:37:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J5jwg-0008FL-9n for ietf@ietf.org; Fri, 21 Dec 2007 10:37:54 -0500
Received: from colibri.verisign.com ([65.205.251.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J5jwe-0001Iv-KK for ietf@ietf.org; Fri, 21 Dec 2007 10:37:54 -0500
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id lBLFVY8i012532; Fri, 21 Dec 2007 07:31:35 -0800
Received: from MOU1WNEXMB09.vcorp.ad.vrsn.com ([10.25.15.197]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 21 Dec 2007 15:37:51 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 21 Dec 2007 07:37:51 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <2788466ED3E31C418E9ACC5C31661557084FB8@mou1wnexmb09.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IPv4 Outage Planned for IETF 71 Plenary
Thread-Index: AchDrsRIvEcuRLPPSjOLAk6RYG0UUwAN1bih
References: <E1J3IFS-0002yV-CG@ietf.org> <476ACD26.8050503@stpeter.im> <20071221085028.GA19743@nic.fr>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Peter Saint-Andre <stpeter@stpeter.im>
X-OriginalArrivalTime: 21 Dec 2007 15:37:51.0847 (UTC) FILETIME=[728DEF70:01C843E7]
X-Spam-Score: -2.2 (--)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: 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>
Content-Type: multipart/mixed; boundary="===============1270619443=="
Errors-To: ietf-bounces@ietf.org

Hah!
 
Over here in Boston metropolitan area the much bigger concern is which provider can give you a reliable connection with acceptable speed. 
 
Since this thread started I have been forced to reboot my WiFi and cable box eight times as the Comcast connection goes down and causes the box to sulk. 
 
Part of this is due to the abysmal quality of the DHCP client and server code and the abysmal quality control on domestic WiFi routers which seem to all be designed to flake just over a year after they are deployed. I have tried every brand you can imagine and I have a large box full of ones that have gone off.
 
But the root cause here is the broadband connection flaking. I would switch to Verizon but reports suggest that it is no better.
 
 
Telling me that support for IPv6 should be a factor in making a choice between the two available providers is like telling one of the unfortunate occupants of East Germany that they should get a Ferrari instead of a Trabant.

________________________________

From: Stephane Bortzmeyer [mailto:bortzmeyer@nic.fr]
Sent: Fri 21/12/2007 3:50 AM
To: Peter Saint-Andre
Cc: ietf@ietf.org
Subject: Re: IPv4 Outage Planned for IETF 71 Plenary



On Thu, Dec 20, 2007 at 01:14:30PM -0700,
 Peter Saint-Andre <stpeter@stpeter.im> wrote
 a message of 279 lines which said:

> This thread prompted me to ask one of my hosting providers about
> IPv6 support. I received the following long but entertaining reply,

It seems a good opportunity to consider a switch to another provider,
one less entertaining but more knowledgeable :-) One spending more
time on his network and less on showing the whole world his ignorance.

> Type a few out, and then check them for typos.

Among the many dummy things he mentions, this one is probably the best
:-) May be someone should tell him there are name resolution services
(and they existed even before the DNS)?

> The first thing I tried was to see if I could get some IPv6 transit.  I
> decided to ask Sprint about IPv6.

This one is a bad example :-)

http://networxcontract.sprint.com/downloads/Sprint%20IPv6%20whitepaper_September%202007.pdf
http://www.internetnews.com/infra/article.php/3717426

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


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