Re: [v6ops] Discussion: IPv4 as a Service

"Fred Baker (fred)" <fred@cisco.com> Thu, 26 March 2015 21:00 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 AE2621B2EF9 for <v6ops@ietfa.amsl.com>; Thu, 26 Mar 2015 14:00:00 -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 FKZ0JAzP3c3p for <v6ops@ietfa.amsl.com>; Thu, 26 Mar 2015 13:59:59 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09EDF1A89E1 for <v6ops@ietf.org>; Thu, 26 Mar 2015 13:59:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3550; q=dns/txt; s=iport; t=1427403599; x=1428613199; h=from:to:cc:subject:date:message-id:references: in-reply-to:reply-to:mime-version; bh=PQ9Axuq8lbczSUa6qNpJmN/U/gDEQZlSUvOpejjVzWY=; b=b/CH1ZCeLYgRyXRySfrKL/1lF176I2TaFH61n/htUYNoJWjYfrtVfBLV VQwXSJwUs8dN1Dp8JiLuJLUXH17eUzEyBfaZzI8L2JojrqAjKm3IucW/F NPOwnzHsFEt+6YygLj6HBgDilpXV4ZpBFoDnIqe1s7wVZkagqiKIzL+5R s=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOBQD/cRRV/49dJa1cgwZSWgSDDrRGjVuFcwKBYUwBAQEBAQF9hBQBAQEDASNLCwULAgEIGCoCAjIlAgQOBQ4GiBMIDbFahlOTZQEBAQEBAQEBAQEBAQEBAQEBAQEBARMEiyiEeAeCaC+BFgWEUjmLRYFpgTIFT4QAggCBG4MwglqJQYNHIoNubwGBQ38BAQE
X-IronPort-AV: E=Sophos;i="5.11,474,1422921600"; d="asc'?scan'208";a="407334491"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-2.cisco.com with ESMTP; 26 Mar 2015 20:59:58 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t2QKxwd6015301 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 26 Mar 2015 20:59:58 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.149]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Thu, 26 Mar 2015 15:59:58 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: IPv6 Ops WG <v6ops@ietf.org>
Thread-Topic: Discussion: IPv4 as a Service
Thread-Index: AQHQaAfQjzft5CJX0ky6SJP3H9kyTQ==
Date: Thu, 26 Mar 2015 20:59:57 +0000
Message-ID: <8EF27210-0C56-4F6D-81FD-B27EE34ED444@cisco.com>
References: <D2204E54-FD09-40E1-A3BE-A662C4546E0D@cisco.com>
In-Reply-To: <D2204E54-FD09-40E1-A3BE-A662C4546E0D@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.89.12.130]
Content-Type: multipart/signed; boundary="Apple-Mail=_1B3680CA-B944-476E-A084-1CED1A062D7E"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/7JY41iVCH2NNxMSR2kjOzRCnwnc>
Cc: "v6ops-ads@tools.ietf.org" <v6ops-ads@tools.ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, "softwire-chairs@tools.ietf.org" <softwire-chairs@tools.ietf.org>, "sunset4-ads@tools.ietf.org" <sunset4-ads@tools.ietf.org>, "sunset4-chairs@tools.ietf.org" <sunset4-chairs@tools.ietf.org>
Subject: Re: [v6ops] Discussion: IPv4 as a Service
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IPv6 Ops WG <v6ops@ietf.org>
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: Thu, 26 Mar 2015 21:00:00 -0000

It came to my attention last night that the link I sent yesterday is read-only. This should allow you to comment (e.g., you can change the document, but it shows up under change control; Lee, Joel, and I are editors on it).

https://docs.google.com/document/d/1ifDEkoypW43lgZJqh2paUDcMAwoUWdz6psyEb456c3A/edit?usp=sharing

I’d appreciate any comments you have on this being edited into the file or in a reply to the list or to the chairs.

> On Mar 25, 2015, at 6:48 PM, Fred Baker <fred@cisco.com> wrote:
> 
> 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.