Re: [v6ops] Operational Consensus on deployment

Owen DeLong <owen@delong.com> Tue, 05 August 2014 02:09 UTC

Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF94C1A0B07 for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 19:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.992
X-Spam-Level:
X-Spam-Status: No, score=-0.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] 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 NwgAGogXAS_I for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 19:09:06 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id A4C6A1A0AFB for <v6ops@ietf.org>; Mon, 4 Aug 2014 19:09:05 -0700 (PDT)
Received: from [192.168.1.62] (ip72-199-16-177.sd.sd.cox.net [72.199.16.177]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id s7527PIF006559 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 4 Aug 2014 19:07:27 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com s7527PIF006559
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1407204447; bh=RtAlDfvyGFPQlL/WzQGNTb4eEek=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=ymqg1lIjrc5xWqTBpso64sFBLGQwj68bWDtrtph7FshyuzbqhvZoouXak5GtFjd8i 7eeM5EOE6yjmpsZvnMaLlaBF36rc70RR0OU0K/TkF8/iegFDz7mt1FQJUblsbXckor 94YHrDjd4ZHeZBsfwCQasIjoG3DpsTcOiyMelKio=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20140804231151.AAAEF1B7AB9F@rock.dv.isc.org>
Date: Mon, 04 Aug 2014 19:07:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <730B6260-C217-4927-AB68-9EBEDFDE9326@delong.com>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <28BBAD81-F9FE-43EB-BF49-E5B85C2AB218@cisco.com> <20140804231151.AAAEF1B7AB9F@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1878.6)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Mon, 04 Aug 2014 19:07:27 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/RHzlQJm-VLiYzzDPl8plye3m09I
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Operational Consensus on deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Aug 2014 02:09:07 -0000

On Aug 4, 2014, at 4:11 PM, Mark Andrews <marka@isc.org> wrote:

> 
> In message <28BBAD81-F9FE-43EB-BF49-E5B85C2AB218@cisco.com>, "Fred Baker (fred)
> " writes:
>> 
>> The alternative is where Microsoft Azure finds itself now. They are out
>> of IPv4 address space and do not have a publicly announced IPv6 service.
>> To fill the gap, they are moving address space from Brazil to the US.
>> Now, lest someone think I'm slamming them, I have little doubt that they
>> have a long term plan; it's just not in evidence at the moment. But where
>> they stand, if they don't have a plan, they're screwed. They are only the
>> most public of a long list of companies with that problem...
> 
> Azure would still need the IPv4 addresses because the rest of the
> world as a whole has not moved to IPv6 yet.  While datacenters may
> be able to move to IPv6 only internally there is still a external
> need for IPv4 addresses.  IPv6 only gives some IPv4 address saving
> but not that much on the server side.  We are still a long way from
> turning off IPv4 servers.

We may be a long way from turning the existing ones off.

The address situation seems to suggest we may not be all that far from not turning on very many more new ones, however.

Owen