IETF Logo Mail Archive

Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 17 July 2017 06:32 UTC

Return-Path: <prvs=13714351ed=jordi.palet@consulintel.es>
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 B4BF9130154 for <v6ops@ietfa.amsl.com>; Sun, 16 Jul 2017 23:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] 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 K3ZyM-giqwRV for <v6ops@ietfa.amsl.com>; Sun, 16 Jul 2017 23:32:14 -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 E788612ECF0 for <v6ops@ietf.org>; Sun, 16 Jul 2017 23:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1500273131; x=1500877931; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=nogJYKFMBFj2aAXVZee0yWXUd mCZa19BxSbm/wRHCI8=; b=PgTG4tys8cVymn1YvsGin1N+9RmV2yaHIP1J+zgON D82B0VsbS3W1D4gY4oqhEx2ozmElXsQDVeRfrITaRQVajlNoqAvILZEfaNgllExl vYE5qEFv/rtS8KYE1SdzIelCFjNoms7MTQTuEQn6W05Aev9GlhTuSoZsXvLGA014 30=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=edsEf+qXfnin3dAasmOByiz1bBs7t6peTrsNj8NRwucGINwjniHnTZKbqmH9 gidcWBWjBSjz7LdVQ9YqHpoYH1k/xOA7yBHHqnEloPYcs8ZVm9fSFTXFN r364W7uWt9KzVEbMeoVoWhgsbbbF6lJbumHySCmtolwK1yxplPvyIk=;
X-MDAV-Processed: mail.consulintel.es, Mon, 17 Jul 2017 08:32:11 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 17 Jul 2017 08:32:10 +0200
Received: from [31.133.186.43] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005478028.msg for <v6ops@ietf.org>; Mon, 17 Jul 2017 08:32:09 +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:170717:md50005478028::1KntRwpPCUAWle9S:00001CcS
X-MDRemoteIP: 31.133.186.43
X-Return-Path: prvs=13714351ed=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Mon, 17 Jul 2017 08:32:06 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
CC: Alissa Cooper <alissa@cooperw.in>, Suresh Krishnan <suresh.krishnan@gmail.com>, Jim Martin <jim@daedelus.com>, Randy Bush <randy@psg.com>, Russ Housley <housley@vigilsec.com>
Message-ID: <A5D0385C-F755-4B44-86D8-6E618E77193F@consulintel.es>
Thread-Topic: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
References: <7643C1DC-76A3-4652-9BB1-D0D42801F37E@consulintel.es> <CAEqgTWYOe=jWp=zVZNLx6DjKjNpPTYaq2jmjryudrGZHKZNq6g@mail.gmail.com>
In-Reply-To: <CAEqgTWYOe=jWp=zVZNLx6DjKjNpPTYaq2jmjryudrGZHKZNq6g@mail.gmail.com>
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/v6ops/0CA08MYwh_mY4Q71PPeDcBT9TrE>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
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: Mon, 17 Jul 2017 06:32:16 -0000

NAT64 has been tested already in many networks, it just works but ONLY if your app isn’t using literals or old libraries, etc. So the only “new” thing we can learn from this experiment is what apps break because that. The way I’m suggesting (464XLAT) has been also tested in many networks, and actually is globally deployed in almost every cellular network that provides IPv6. The results we can get using this instead of only NAT64, is that those apps that break will be automatically logged.

If we just do NAT64, do you expect the users that have a break to “report” manually what is broken for them. May be 10% will do. With CLAT, we collect automatically 100%.

Which one do you think is more advantageous?

Also, note that the IETF network has always been described as a non-place for experiments.

Regards,
Jordi
 

-----Mensaje original-----
De: Noah <noah@neo.co.tz>
Responder a: <noah@neo.co.tz>
Fecha: lunes, 17 de julio de 2017, 8:14
Para: <jordi.palet@consulintel.es>
CC: Alissa Cooper <alissa@cooperw.in>, Suresh Krishnan <suresh.krishnan@gmail.com>, <v6ops@ietf.org>, Jim Martin <jim@daedelus.com>, Randy Bush <randy@psg.com>, Russ Housley <housley@vigilsec.com>
Asunto: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

    
    
    On 17 Jul 2017 8:26 a.m., "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es> wrote:
    
    In my opinion such kind of experiment should be only done once we approve the document as RFC, note before, so by the next IETF meeting (hopefully).
    
    
    
    
    
    Hi Jordi
    
    Why not, this would be very interesting considering the times. 
    
    Perhaps we can try for 1 or 2 days for experiental purpose as need not to wait for final RFC and the outcome could also feed the current draft as is. Who knows.
    
    +1 for below option if possible.  
    
    -  IPv6 only per the I-D for one or more days this week?
    
    
    Cheers
    Noah
    
    
    
    



**********************************************
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.

v2.23.0 | Report a Bug | By Email