Re: [v6ops] IPv4 trajectory

"Fred Baker (fred)" <fred@cisco.com> Tue, 31 March 2015 18:12 UTC

Return-Path: <fred@cisco.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 098AB1A885D for <v6ops@ietfa.amsl.com>; Tue, 31 Mar 2015 11:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level:
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 In4QrEijTy28 for <v6ops@ietfa.amsl.com>; Tue, 31 Mar 2015 11:12:10 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C96C1A6EDE for <v6ops@ietf.org>; Tue, 31 Mar 2015 11:12:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2699; q=dns/txt; s=iport; t=1427825530; x=1429035130; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HcARF/e1V4g6Qi3njHSeHLCOJGR7uVtLRdBbD45deF4=; b=QRrVQzSr5EOxO3KkAdteRfzv3vf5LCmIOCPCMDnIZoxpUwuyFKHZCDbT L03/tlm1lYUqcSY9c4x7gjGW1L5OAdU4qDoZH5AmO01Stqm6i/6OmVXmM aIBvE3GhiSBizQv/EE/WFwSBP1BMX9mqJbbemKEIHUyMBIc3BwNuaLlaZ U=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BkBQAf4hpV/5JdJa1cgwaBLgWDD8hfAoFETAEBAQEBAX2EFAEBAQMBI1YFCwIBCBgqAgIyJQIEDgUOEIgJCLUCmREBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiymEeAeCaC+BFgWQYoFsgTKEV4IAgS6TDSKDbm+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.11,502,1422921600"; d="asc'?scan'208";a="137007164"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-1.cisco.com with ESMTP; 31 Mar 2015 18:12:09 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t2VIC9pt026534 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Mar 2015 18:12:09 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.67]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0195.001; Tue, 31 Mar 2015 13:12:09 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Ackermann, Michael" <MAckermann@bcbsm.com>
Thread-Topic: IPv4 trajectory
Thread-Index: AQHQa94zOP355mCtYUCyFmxhLNVm0A==
Date: Tue, 31 Mar 2015 18:12:08 +0000
Message-ID: <4B46B05C-FDC6-48BE-9965-84A4F4E49805@cisco.com>
References: <63C03012-C7DD-497E-A1EF-019711E95FD0@cisco.com> <4FC37E442D05A748896589E468752CAA0CD95876@PWN401EA160.ent.corp.bcbsm.com>
In-Reply-To: <4FC37E442D05A748896589E468752CAA0CD95876@PWN401EA160.ent.corp.bcbsm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.117]
Content-Type: multipart/signed; boundary="Apple-Mail=_FA444A16-81EC-4FD5-BDE7-FA532C84F482"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/LNGZ36Ox9riUxcTC8XsmZrnMGJ8>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] IPv4 trajectory
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, 31 Mar 2015 18:12:12 -0000

> On Mar 31, 2015, at 8:08 AM, Ackermann, Michael <MAckermann@bcbsm.com> wrote:
> 
> *  To get from step 5 to 6, there will be a lot of internal IPv4 addresses that seemingly have NO REASON TO CONVERT to IPv6.    I would like to reverse this thinking in  the manifold corporate networks I hear it from,  but have not come up with anything very convincing   yet.

To be perfectly honest, I don’t expect those to ever convert. Sooner or later, their equipment will be replaced, and when it is, the person installing it will be faced with the question of what communication technology to use. I expect those choices to be what makes the step.

The comment about “and along with it, biSync and X.25” was not an idle one. We’re still waiting for the last bisync terminal to die, and X.25 has a constituency in the telephone world.

The other thing I notice, though, is that we don’t have people jumping through hoops to keep those things going. As long as they cause less trouble than they contribute value, value wins. The day the value gasps for breath, so will they.

I’m not even especially concerned about getting from step 4 to step 5. I suspect that economics will get applications to the native network; the only question is “when”. If A works better than B and is less cost to maintain, A will eventually win out.

My only real concern is getting from some variant of step 2b or 3 to 4. At least in part, my reason for describing “step 4” experiences is to point out that there are those who are going there, and to provide “no BS” analyses of that.