Re: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient

"Heatley, Nick" <nick.heatley@ee.co.uk> Wed, 22 April 2015 12:03 UTC

Return-Path: <nick.heatley@ee.co.uk>
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 F313F1B34F4 for <v6ops@ietfa.amsl.com>; Wed, 22 Apr 2015 05:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 oKftfDC4xM6D for <v6ops@ietfa.amsl.com>; Wed, 22 Apr 2015 05:03:18 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.145]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55EE61AC3A6 for <v6ops@ietf.org>; Wed, 22 Apr 2015 05:03:18 -0700 (PDT)
Received: from [85.158.136.3] by server-9.bemta-5.messagelabs.com id 90/5F-19899-40E87355; Wed, 22 Apr 2015 12:03:16 +0000
X-Env-Sender: nick.heatley@ee.co.uk
X-Msg-Ref: server-10.tower-123.messagelabs.com!1429704168!40703998!1
X-Originating-IP: [149.254.241.76]
X-StarScan-Received:
X-StarScan-Version: 6.13.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6911 invoked from network); 22 Apr 2015 12:02:48 -0000
Received: from unknown (HELO smtpml01.ee.co.uk) (149.254.241.76) by server-10.tower-123.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Apr 2015 12:02:48 -0000
Received: from EEUKWV0941.EEAD.EEINT.CO.UK (Not Verified[10.246.209.218]) by smtpml01.ee.co.uk with MailMarshal (v7, 2, 3, 6978) id <B55378de40000>; Wed, 22 Apr 2015 13:02:44 +0100
Received: from UK30S005EXS02.EEAD.EEINT.CO.UK (Not Verified[10.246.208.14]) by EEUKWV0941.EEAD.EEINT.CO.UK with MailMarshal (v7, 2, 3, 6978) id <B55378de70004>; Wed, 22 Apr 2015 13:02:47 +0100
Received: from UK30S005EXS06.EEAD.EEINT.CO.UK ([fe80::314c:b96c:4a9a:8a79]) by UK30S005EXS02.EEAD.EEINT.CO.UK ([2002:62c:2a4f::62c:2a4f]) with mapi id 14.03.0195.001; Wed, 22 Apr 2015 13:02:47 +0100
From: "Heatley, Nick" <nick.heatley@ee.co.uk>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, IPv6 Ops WG <v6ops@ietf.org>
Thread-Topic: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient
Thread-Index: AQHQYtCVneMUqIFM3UWKOHw0TbKROp0lUOcAgAA3nwCAA2c/gIABUuaAgAFbCwCAABVpgIAAAIqAgAAPA4CAAAtsAIAAbkKAgAGv2wCAABSlgIAA/X4AgAAHmQCAAFthgIAL+9OAgAADYgCAAtG/AIAB4f6AgAD7QgCAAMs5AIAF7pkAgAOeT4CADJ5Bd4AA3PKggAAAeoCAADxNoA==
Date: Wed, 22 Apr 2015 12:02:47 +0000
Message-ID: <6536E263028723489CCD5B6821D4B21303E8CBAB@UK30S005EXS06.EEAD.EEINT.CO.UK>
References: <CAD6AjGT-hG-uvRQvRosrZtfrf0Nb8ne9jy=tD9oh=5zNM42Xsg@mail.gmail.com> <CAD6AjGTcKgK8W+VB1H5EQpHaYiKVYXqOz_2RS-w_CiTf9kL2CQ@mail.gmail.com> <CADhXe530+OVZrFZVaYh1-zoRDvJhUd0rf4sx6a2nO8SvKmm6zg@mail.gmail.com> <CAPi140PQ+TF0rED_bQPeS=Fj415qt0-zE2RdGnEL34PAzHyx6Q@mail.gmail.com> <CAD6AjGTjXAeMF6pw5MO2Jrf9B8LJ48D3m1YTVkdBe=_OHjtroQ@mail.gmail.com> <CADhXe51TCqU2eMP4LS3DooZxQDAPD95OVJDXbiU7qvuvKCMq+w@mail.gmail.com> <CAKD1Yr2=zc57+pOA9TFs+0azw0ZR1g67+08T=9eZPHjGXBvgFQ@mail.gmail.com> <CADhXe53T_30pj7xxwNs=mWEnd=do6oiq3KgN=U-gHLrLF-gG7Q@mail.gmail.com> <D1441574.4C168%wesley.george@twcable.com> <CAD6AjGQrzoBJrqQfKO0N8Ji=oJ-ZP6Sn88sXf=opJ6bYVmTDZg@mail.gmail.com> <552102B0.6070904@cernet.edu.cn> <35D97B17-8E83-43CF-ABEF-122572F1321A@eircom.net> <552369C8.5000801@cernet.edu.cn> <CADhXe51BDuPhc8wdKGmRiBfSnrz7PMtqYXaoDO+5cwLx_xW2tw@mail.gmail.com> <55290E26.8080500@cernet.edu.cn> <CADhXe50zz9EtNtifMh+tN9XT-jKCTJB=vsQ6uG515iddOo7f2Q@mail.gmail.com> <5536776A.9060204@cernet.edu.cn> <C ADhXe52HpC1eGtnEw7+yWtOO2-ZEisGe_2Bz9Sz1=JHQQCPhEw@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303E8C63A@UK30S005EXS06.EEAD.EEINT.CO.UK> <67A2A6E4-0603-4E84-8534-EA6C706C6D5D@lists.zabbadoz.net>
In-Reply-To: <67A2A6E4-0603-4E84-8534-EA6C706C6D5D@lists.zabbadoz.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.246.208.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/kTgGAlI4aSMfK-YJ8bU7mpd6iHU>
Subject: Re: [v6ops] The need for local-ipv4 socket transition solutions -- NAT64/DNS64 remains insufficient
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, 22 Apr 2015 12:03:22 -0000

-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Bjoern A. Zeeb
Sent: 22 April 2015 10:15

See, the thing I like about this thread is, that everybody is trying to point their fingers to someone else in order to fix something elsewhere but not with themselves or where the &^%$#$%^&*() problem occurs.   Anyone saying “you cannot get rid of IPv4 literals” to the extend that it doesn’t bother anyone anymore is mislead.  You just have not tried hard enough (probably because you are distracted seeking solutions elsewhere).

If everyone complaining here, would work towards getting rid of them rather than discussing who’s problem it is to put a workaround in place, we’d probably be half-way done.  We have people crawling the web, people having users and test networks, people who seem to be able to write enough emails on the topic that they could even direct it to the right people.

I could even be more adventurous and say:  give them a 90 day notice, publish it (that’s the important part, so that yur users hear about it as well), and if they don’t get back to you that they’ll fix it (timely) break them.  Isn’t that what people do with major security bugs?  I’d be surprised if major shopping sites and news papers wouldn’t react, once their sales and page views go down by a few % over night, but you need to let them and their users know upfront.


[Heatley, Nick] Agree that at some point the finger pointing needs to stop.
My criteria though is not about "fixing at source", it is about being least disruptive or disturbing to customers.
The problem with the source of IPv4 literals is that it includes small businesses, mom & pop companies, as well as majors.
I am certainly not interested in sending out any "the sky is falling down" notices to customers, it is more likely they will just shift providers; and I don't want an "no IPv4 literal" flag day.
The problem has to reside with those on the side of providing the service, not punting it to the customers or users.


NOTICE AND DISCLAIMER
This e-mail (including any attachments) is intended for the above-named person(s).  If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose.  
 
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. 

EE Limited
Registered in England and Wales
Company Registered Number: 02382161
Registered Office Address: Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9BW.