Re: [v6ops] LISP support for draft-ietf-v6ops-rfc7084-bis-00

Fred Baker <fredbaker.ietf@gmail.com> Wed, 12 April 2017 18:24 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D006B12EB31 for <v6ops@ietfa.amsl.com>; Wed, 12 Apr 2017 11:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ZeIktmpPX8uE for <v6ops@ietfa.amsl.com>; Wed, 12 Apr 2017 11:24:45 -0700 (PDT)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBEE312EB28 for <v6ops@ietf.org>; Wed, 12 Apr 2017 11:24:44 -0700 (PDT)
Received: by mail-pg0-x234.google.com with SMTP id g2so18439027pge.3 for <v6ops@ietf.org>; Wed, 12 Apr 2017 11:24:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Q+HqBitcKurj3SOYBndETvW2g0sc7qJ764XhH1QXaZc=; b=iHOupFrUU53CRTx0JsJUdehnDb7kTWq4ft6spATHi0q434QpsBM26NPXScyyMxUFRY BocF6EtaVwSLWOV2suGCBOGjOGDE6b79zam/JNSUkqI2xt5DafYl2BnPw6gSDZnFUZUa YvfGkzh7TuQHxKYuAfbD/TGZKHCQ3qFCeV5gjnHs3dmI6p0efvGPJBs1NuK8OXdDmBqR GzcdVuzdP57hYjhF6xDdZGeKFvYf9sgw/kRmVgbqObW8SA7dplVIPnH4KFvrHzfBREuA 1ijOHyJkEOAKjbTUGR6sM7GtIsGt9uqIXUCLHH2ADv7vkv4L0jEqvmZ1FwkVu6fETimT UQ3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Q+HqBitcKurj3SOYBndETvW2g0sc7qJ764XhH1QXaZc=; b=k4R5aNs4wNqn16IU+sHBMXxivecnI7z4l6OZnfIrY3uFI3vA1lp/RIQNAsBJC+HPrG 1Ia1ER+wHG0Wa3xf93DOA8uyz9ilqAAp94HZC54Szta4ZJveJGA5YxJL93EN+RAN90AL MzhFWKGXcRLbQr8vvrnGHznCb0nxkyLvokmRztiHrNvsYTCwKoAVRODLG84JzQBYjAEB YIoovud0O7KAKEtXao7K0224/RgPAUjaJ5zQ5X0+Um53+DQt3P7bo+EYRTMDLOrXnXBr ix0xZum7KoVPvM+yqMEpboP9xvvvzsg/40biS8n8odn1WwOhvW8KYU7XFEFKDCUe/7It K5iA==
X-Gm-Message-State: AFeK/H3hGdEYjwzDGDtFXOAx5n325hWC3Ml4ZzslgPOQOo9oHBYJV/PWGfTM0o5NW5ihmw==
X-Received: by 10.99.175.7 with SMTP id w7mr69484825pge.170.1492021484408; Wed, 12 Apr 2017 11:24:44 -0700 (PDT)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id b77sm3970301pfe.39.2017.04.12.11.24.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 11:24:43 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <6DA0D96E-247C-4A95-906B-AD6EB3275938@consulintel.es>
Date: Wed, 12 Apr 2017 11:24:41 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EB3C46D-7F2A-4BE1-A30C-C816D6026184@gmail.com>
References: <D8F5C737-B01A-4EC8-9175-C4921C0CD69F@consulintel.es> <392D675B-73C4-40D3-81A8-A06907F5581D@employees.org> <3BBFC922-85BD-49B5-B39E-227F191BD48C@consulintel.es> <729244A1-E7AB-4BA0-8B39-A6122D2C32DB@employees.org> <787AE7BB302AE849A7480A190F8B933009E4C3B8@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <2D09D61DDFA73D4C884805CC7865E6114DB194A8@GAALPA1MSGUSRBF.ITServices.sbc.com> <E8AB2CCD-B563-446F-BA96-D18F735F72B6@gmail.com> <6DA0D96E-247C-4A95-906B-AD6EB3275938@consulintel.es>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kFt7WrKAq2hH7WaAbnQZuxQqnPs>
Subject: Re: [v6ops] LISP support for draft-ietf-v6ops-rfc7084-bis-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 12 Apr 2017 18:24:47 -0000

> On Apr 12, 2017, at 10:44 AM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> 
> [Jordi] I disagree here. Adding the actual transition mechanism (all them) in the v-01 of the document (submitted today) means 0,15% of extra flash memory 

no hats

Perhaps true. It also means that the vendor (open source is a vendor, from this perspective) allocates human resources, which cost money, to write and maintain the software. The software has some probability of bugs per volume of code, which means that there is a quantifiable security risk. Now, any business calculates its costs and potential upside benefits, and figures out how to make money (even open source developers do, believe me). Asking them to spend money with little real opportunity to gain saddles them with a cost and a risk with little upside. It's not the volume and price of the flash; it's the support costs.

If the vendor is looking at 7084 for guidance and saying there is no market for a given technology, it's because the operators in this working group collectively said there was no market in their networks. In the end it isn't about an RFC, it's about a market. No market, no money, no product. It's that simple.

If I'm hearing anything in this discussion, it's that the end game isn't found in having all of the transition technologies in product. It's to be found in native deployment that doesn't need the transition technologies.

You might find these two links interesting. One is from the IPv4 Market Group, and makes prognostications on the value of an IPv4 address; the other is a public presentation by Swisscom about the traffic measurements in its network. In both cases, they are asking when they expect IPv6 usage, whether in traffic or in users, to exceed IPv4, and as a result when the need for dual stack deployment starts to wind down. Both, by different avenues, pick 2019 as the turning point, and Swisscom suggests that by 2024 it might not have enough IPv4 traffic in its network to justify having IPv4 enabled - even in an overlay.

The issue of transition mechanisms has to do with networks being predominantly IPv4 and having to reach them using IPv6. Both are saying that there is a light at the end of that particular tunnel, and it's not an oncoming train.

http://ipv4marketgroup.com/q42016-update/
http://www.ipv6conference.ch/wp-content/uploads/2015/06/B10-Swisscom-Status_Roadmap_and_Outlook_IPv6.pdf