Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 01 August 2017 10:39 UTC

Return-Path: <prvs=13860e1204=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA8E13209E for <ietf@ietfa.amsl.com>; Tue, 1 Aug 2017 03:39:47 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 b3rSzXW8376E for <ietf@ietfa.amsl.com>; Tue, 1 Aug 2017 03:39:45 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E7B3132064 for <ietf@ietf.org>; Tue, 1 Aug 2017 03:39:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1501583983; x=1502188783; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=2U+gj3EXqBVadyXnKuL92WKA0 58nFCJN5ebnhkvq5sA=; b=Xz6xRS4QlcJagguSgHKgJhWlBB6CjxFQD5tpN5yki gHRF503VlLE1NbWYRMSaoL3piCa+NMTZWYQaG4zlEFiqCH5rEXci38BHW30Opvb1 5+cRHaN/ihD+ww1ys0OFA2Tk/posbSpha34qa28St3T6kUhX2r5JIY4Ciioy3Z86 g0=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=J6TbUx8fFN/NqQKR+MdCA2ag3zNQjnWMExcefo+Kmhpu3TYK6NNmWPvJiQJX RJlFU0PUeqmNmja3WFNIbAcgma6w7cu4yNfxnzoL1M79wZQRY9FcvUoGE A383LcbxwVTg8VFDhUOrCK/aJixj0RHvsP9pdnzZCMyCpMS6oGQg2o=;
X-MDAV-Processed: mail.consulintel.es, Tue, 01 Aug 2017 12:39:43 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 01 Aug 2017 12:39:42 +0200
Received: from [10.10.10.133] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005491961.msg for <ietf@ietf.org>; Tue, 01 Aug 2017 12:39:42 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170801:md50005491961::GL9QtalyQU+WxBRb:00001fqT
X-Return-Path: prvs=13860e1204=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.1.170721
Date: Tue, 01 Aug 2017 12:39:40 +0200
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ietf@ietf.org
Message-ID: <2322AE99-0425-4811-93D1-3EAD78488A08@consulintel.es>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <E3AEEAB4-FBFF-4824-8B6C-4FD9B3BA4722@consulintel.es> <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
In-Reply-To: <m1dcUV1-0000FGC@stereo.hq.phicoh.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qJ84Tofwic-c3cH_47CNXykgVqg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Aug 2017 10:39:47 -0000

Just small clarifications in-line.

Saludos,
Jordi
 

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Responder a: <pch-ietf-6@u-1.phicoh.com>
Fecha: martes, 1 de agosto de 2017, 12:34
Para: <ietf@ietf.org>
CC: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Asunto: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

    >Is precisely what CLAT (464XLAT) is resolving.
    
    So we have a standard way of delivering IPv4 over wifi. It actually works.
    It is used by billions of people every day without even thinking about it.
    By all measures a great success.
    
    We also have a way of delivering IPv6 over wifi. In typical IETF fashion 
    we try to break that as much as possible. But it can be made to work.
    
    So obviously this is way too boring. We have both IPv4 and IPv6 that work.
    We need to do something, anything.
    
    So NAT64 enters the stage. At first NAT64 was used to solve a problem in
    the mobile networks where you cannot have dual stack for reasons only telco's 
    understand.

[Jordi] Because we don’t have any more IPv4 public addresses, and we know that for some time, we will need to access still some old “IPv6-only” resources? Sharing IPv4 addresses by means of NAT64 is one solution to that.
    
    But now we can use that same technology to spice up the wifi landscape a bit
    more.
    
    First we confusingly call it 'IPv6-only'. There is nothing IPv6-only about
    NAT64. It is a technology specifically designed to provide access to the
    IPv4 world.
    
    Then, because of the fancy name 'IPv6-only' we claim it is the future. No
    need to justify why modifying all hosts and making the whole system more
    complex would be a reasonable future.

[Jordi] Agree, see: https://tools.ietf.org/html/draft-palet-ietf-v6ops-ipv6-only-00
    
    We have something that works today. We have plenty of experience delivering
    what works today. No need to push overly complex technologies that offer
    nothing more than a fancy name. That's not engineering, that's a hobby.
    
[Jordi] We need to move to IPv6-only “all”, there is an intermediate step, for “some” (crystal ball) years, which is IPv6-only-WAN, but dual-stack in the LAN. NAT64+CLAT provides it seamless across both wireline, WiFi and cellular networks.
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.