IETF Logo Mail Archive

Re: IETF network incremental plan

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 17 November 2016 02:34 UTC

Return-Path: <mcr@sandelman.ca>
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 73730129478 for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2016 18:34:53 -0800 (PST)
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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 loedFiZqWwoW for <ietf@ietfa.amsl.com>; Wed, 16 Nov 2016 18:34:50 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C83FA129623 for <ietf@ietf.org>; Wed, 16 Nov 2016 18:34:47 -0800 (PST)
Received: from dooku.sandelman.ca (s2001067c037001280a1196fffe0181e0.v6.meeting.ietf.org [IPv6:2001:67c:370:128:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id 79AE01F8EF; Thu, 17 Nov 2016 02:34:46 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id D6A8E28A4; Thu, 17 Nov 2016 11:34:42 +0900 (KST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: IETF network incremental plan
In-reply-to: <0C5BCD32-2D2A-42B9-8DEA-A1E1A527A8BB@consulintel.es>
References: <0C5BCD32-2D2A-42B9-8DEA-A1E1A527A8BB@consulintel.es>
Comments: In-reply-to JORDI PALET MARTINEZ <jordi.palet@consulintel.es> message dated "Wed, 16 Nov 2016 19:26:44 +0900."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Thu, 17 Nov 2016 11:34:42 +0900
Message-ID: <20140.1479350082@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YA641ROzX-45NRRrl5rZDWvozYc>
Cc: jordi.palet@consulintel.es
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 17 Nov 2016 02:34:55 -0000

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
    > Any of you will take the risk to disable IPv4 in your home network? Or
    > even in the corporate network?

A bug in my CeroWRT 3800 home router results in our wifi regularly having NAT44
broken, but IPv6 continues to work. (There is no NAT64).  It often takes my
wife days to notice: she complains "twitter looks weird", as the twitter CDN
is not v6 capable, so the CSS doesn't load.

{I have a Turris waiting at home, I didn't want to install it before
travelling}



-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.26.15 | Report a Bug | By Email | System Status