[v6ops] Discussion: IPv4 as a Service

Fred Baker <fred@cisco.com> Wed, 25 March 2015 23:48 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 3079C1A87F1 for <v6ops@ietfa.amsl.com>; Wed, 25 Mar 2015 16:48:56 -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 LAuGGoL9Wuxz for <v6ops@ietfa.amsl.com>; Wed, 25 Mar 2015 16:48:54 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 934761A6F7B for <v6ops@ietf.org>; Wed, 25 Mar 2015 16:48:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2010; q=dns/txt; s=iport; t=1427327334; x=1428536934; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=IoZP7ieBg00fqZMgMEQ79WAEMO6lzNWg/o7tNi3JYbY=; b=O/23mcYdyVbrJSlgFRDbjA1j2HTj3Bta03MzuGXt6dHsf9nksAiL58Ea DLepjrWw9AVsTiobBgVKo7xy9PwsqcZnRSV1Pkzzl0EWhYOl2miCcVUc1 mZ2kxY1NXkRwBgqJ4PNnd0qWbcP/wF6XyV+dpS2RVfIogsO6cH/A+1Dva o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DnBACkSBNV/5FdJa1cgwNSWsNDgVGFc4FdOBQBAQEBAQEBfIRVNAuBPieIGw3KIAEBAQEBAQEBAQEBAQEBAQEBAQEBARMEkBaDHoEWBYULhgeIXE+Ff4EbgzCCOIlfg0cihAwgMQGCQgEBAQ
X-IronPort-AV: E=Sophos;i="5.11,468,1422921600"; d="scan'208";a="135348472"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-8.cisco.com with ESMTP; 25 Mar 2015 23:48:53 +0000
Received: from [10.89.11.3] ([10.89.11.3]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t2PNmqEg027240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Mar 2015 23:48:53 GMT
From: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 25 Mar 2015 18:48:51 -0500
Message-Id: <D2204E54-FD09-40E1-A3BE-A662C4546E0D@cisco.com>
To: IPv6 Ops WG <v6ops@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/aL238t2K9Tu8pv_chsCIWpQV6-4>
Cc: v6ops-ads@tools.ietf.org, V6ops Chairs <v6ops-chairs@tools.ietf.org>, softwire-chairs@tools.ietf.org, sunset4-ads@tools.ietf.org, sunset4-chairs@tools.ietf.org
Subject: [v6ops] Discussion: IPv4 as a Service
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: Wed, 25 Mar 2015 23:48:56 -0000

Lee and I opened a discussion in the v6ops meeting today on a topic that I believe that the IETF, in cooperation with the *NOGs, needs to address. My slide is at https://www.ietf.org/proceedings/92/slides/slides-92-v6ops-9.pptx. Sunset4 and softwire chairs, please feel free to forward this to your mailing lists.

In short, we are starting to see the deployment of IPv6-only networks. In most cases, these are existing IPv4 networks that have become dual stack, and are somewhere in the process of shutting IPv4 down. These include Facebook, which (regardless of whether you view it as an enterprise or a content network) has been public about the fact, several mobile networks that treat IPv6-capable telephones as an IPv6-only network and use 464xlat as an operational methodology dealing with that, and some research networks, notably CERNET2, which has been running IPv6-only for ten years now. We also see green-field networks, such as Reliance JIO Infocomm Ltd; Suprita Sah presented on that topic today.

I am of the opinion, and there seemed to be agreement in the room, that the Internet community would be well served if we collected deployment experience with these technologies, and the considered advice of deploying operators. We have tried to guide the deployment of IPv6, and gathered experience and mitigations for that. Now, as IPv4 begins to fade, we need to take a leadership role in that.

I have opened a document on Google Docs, and given folks the ability to view it. That is at https://docs.google.com/document/d/1ifDEkoypW43lgZJqh2paUDcMAwoUWdz6psyEb456c3A. I have included an initial list of relevant technologies, and an initial list of the questions that we would want discussed in experience documents. I guarantee that there is an important question not asked, and while I hope otherwise, there may be some technology I have overlooked. So I invite discussion to flesh out that initial phase.