Re: [v6ops] Operational Consensus on deployment

Mark Andrews <marka@isc.org> Mon, 04 August 2014 23:12 UTC

Return-Path: <marka@isc.org>
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 93B011A03E9 for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 16:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 973pcFwxBFCT for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 16:11:56 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE8931A03D2 for <v6ops@ietf.org>; Mon, 4 Aug 2014 16:11:55 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id 3320A3493BA; Mon, 4 Aug 2014 23:11:54 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id ED0CD160067; Mon, 4 Aug 2014 23:22:02 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id BEC9B160066; Mon, 4 Aug 2014 23:22:02 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id AAAEF1B7AB9F; Tue, 5 Aug 2014 09:11:51 +1000 (EST)
To: "Fred Baker (fred)" <fred@cisco.com>
From: Mark Andrews <marka@isc.org>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <28BBAD81-F9FE-43EB-BF49-E5B85C2AB218@cisco.com>
In-reply-to: Your message of "Mon, 04 Aug 2014 21:03:42 +0000." <28BBAD81-F9FE-43EB-BF49-E5B85C2AB218@cisco.com>
Date: Tue, 05 Aug 2014 09:11:51 +1000
Message-Id: <20140804231151.AAAEF1B7AB9F@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/HfnBEKI-eBNle5EPZw0chBp63vM
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: Mon, 04 Aug 2014 23:12:04 -0000

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.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org