Re: [dhcwg] [IETF] Re: We can change the world in a 1000 ways (IPv4 over IPv6)

Warren Kumari <warren@kumari.net> Tue, 12 November 2013 19:53 UTC

Return-Path: <warren@kumari.net>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 171B721F9EED; Tue, 12 Nov 2013 11:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKHz+8b2CJdF; Tue, 12 Nov 2013 11:53:20 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED7D21F9CC5; Tue, 12 Nov 2013 11:53:19 -0800 (PST)
Received: from [192.168.1.153] (unknown [66.84.81.108]) by vimes.kumari.net (Postfix) with ESMTPSA id E01721B40380; Tue, 12 Nov 2013 14:53:18 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_FCA83C4E-B70D-49AC-B262-9C3B0C5E1F50"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <24212.1384279979@sandelman.ca>
Date: Tue, 12 Nov 2013 14:53:14 -0500
Message-Id: <130642B1-E080-4B09-AD1F-9CE96F5DA252@kumari.net>
References: <5ABB4DF8-95F0-4B07-8D20-6A00B7631E11@employees.org> <30650.1384272400@sandelman.ca> <C99405BD-C52D-41D8-AC68-2C9A6A036603@nominum.com> <24212.1384279979@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1510)
X-Mailman-Approved-At: Tue, 12 Nov 2013 12:15:30 -0800
Cc: Softwires <softwires@ietf.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Warren Kumari <warren@kumari.net>, Ted Lemon <Ted.Lemon@nominum.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: [dhcwg] [IETF] Re: We can change the world in a 1000 ways (IPv4 over IPv6)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 19:53:26 -0000

On Nov 12, 2013, at 1:12 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

> 
> Ted Lemon <Ted.Lemon@nominum.com> wrote:
>>> It would be nice to convene a summit of operators (at RIPE or NANOG)
>>> and describe the various mechanisms and rather than ask them which one
>>> they like, 
>>> ask them which one they would *NEVER* consider.  That might reduce the
>>> field by half...
> 
>> I don't think that's practical—they might all vote for a protocol that
>> they wind up not wanting to deploy.   The models that are under
> 
> That's why I wouldn't ask them to pick a winner, but rather to pick the loser.
> 
>> consideration actually have running code and some operational
>> experience behind them.   So asking operators to decide based on a
>> feature list or something of that sort is not a good idea.   What we
>> really want is for operators who have realistic intentions of deploying
>> this stuff to weigh in.   And they are doing so, in the working group,
>> so we don't really need to go to RIPE or NANOG to get this feedback. 
> 
> a) I'm not convinced the operators we have are very representative of the
>   whole.

It is not, but a number of the operators who do participate *try* and represent the industry, and not just their employer.

A well known issue is the lack of operator involvement in the IETF. 
In general operators are focused on solving issues *today* - much of the work in the IETF is viewed as much further out  and / or detached from the operational real world.
A number of things have reinforced this view, especially some of the v6 zealotry and unwillingness to listen to what the operators actually want (see the DHCP discussions and extension / fragment discussions). Just because it works fine in IPv4 is *not* actually a good reason to change it in IPv6...


Very rough stats:
NANOG has ~690 attendees (Phoenix), RIPE has ~570 (Dublin), APRICOT ~725 (Singapore), lacnic20 and ~291 and MENOG ~95. I was not easily able to find the attendee list for other NOGS (like PacNOG, Afrinic, etc.)

There are around 1100 organizations represented (the list formats were not identical, some folk spell their organization names differently, do you count Globenet and Globenet/Brasil as one organization or two?)


>  (But those that show up at a NOG might not be either. sadly)

Yup. But it *is* much more representative...

> 
> b) I'm more interested in reasons operators who are not deploying anything,
>   have for not wanting to.
> 
> I'll bet if we had a single IPv4 over IPv6 solution which had a clear
> operating cost savings over Dual-Stack, and also over IPv4-only+CGN, that
> we'd be at universal deployment of IPv6 already.
> 
> I don't really understand why we have so many mechanisms... Perhaps we could
> have an IAB plenary presentation on it... or maybe someone could do an ISOC
> video like Kathleen did for MILE.
> 
> -- 
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works 
> 
> 

-- 
Eagles soar but a weasel will never get sucked into a jet engine