IETF Logo Mail Archive

Re: IPv4 outage at next IETF in Chicago

Franck Martin <franck@peachymango.org> Wed, 25 January 2017 19:07 UTC

Return-Path: <franck@peachymango.org>
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 D841D129AF5 for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 11:07:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=peachymango.org
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 z79pNuk3DfSN for <ietf@ietfa.amsl.com>; Wed, 25 Jan 2017 11:07:00 -0800 (PST)
Received: from zmcc-5-mx.zmailcloud.com (zmcc-5-mx.zmailcloud.com [192.198.93.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59BA4129AF6 for <ietf@ietf.org>; Wed, 25 Jan 2017 11:07:00 -0800 (PST)
Received: from zmcc-5-mta-1.zmailcloud.com (127.37.197.104.bc.googleusercontent.com [104.197.37.127]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zmcc-5-mx.zmailcloud.com (Postfix) with ESMTPS id 62474520276; Wed, 25 Jan 2017 14:06:59 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id 14631C23F3; Wed, 25 Jan 2017 13:06:59 -0600 (CST)
Received: from zmcc-5-mta-1.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-5-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 7KDkKsQSnejt; Wed, 25 Jan 2017 13:06:58 -0600 (CST)
Received: from localhost (localhost [127.0.0.1]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id 75BCAC23E9; Wed, 25 Jan 2017 13:06:58 -0600 (CST)
DKIM-Filter: OpenDKIM Filter v2.9.2 zmcc-5-mta-1.zmailcloud.com 75BCAC23E9
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peachymango.org; s=61F775A4-4A7F-11E4-A6BB-61E3068E35F6; t=1485371218; bh=yDMTmoYUKF0COXkEL2cG7RrMxqp48XZysWN8gLX+vyc=; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; b=hfLQS7CoFJH+j3jnAOCT4tcueEFGNQgLNXoOILpz1ptThCAMAY5K5lBqGfKoiodQB k47yH4fjhsJ9L4X+hmuR0eWzDyGS+VSBmsJPxNlQZNbXqvh44mbkhu+GKHEMGVkmIU xIt5z/koQVjatwCHiteJJThaG2EUk7GtAXWhhUm0=
X-Virus-Scanned: amavisd-new at zmcc-5-mta-1.zmailcloud.com
Received: from zmcc-5-mta-1.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-5-mta-1.zmailcloud.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZgAELVIDfTQZ; Wed, 25 Jan 2017 13:06:58 -0600 (CST)
Received: from zmcc-5-mailbox-1.zmailcloud.com (zmcc-5-mailbox-1.zmailcloud.com [10.240.0.12]) by zmcc-5-mta-1.zmailcloud.com (Postfix) with ESMTP id 49480C2414; Wed, 25 Jan 2017 13:06:58 -0600 (CST)
Date: Wed, 25 Jan 2017 13:06:58 -0600 (CST)
From: Franck Martin <franck@peachymango.org>
To: Matthew Pounsett <matt@conundrum.com>, paul.hoffman@vpnc.org
Message-ID: <1350087674.115436952.1485371218219.JavaMail.zimbra@peachymango.org>
In-Reply-To: <WM!572ad9a6ae19416c99bd6357d98a5df59a81b46a887701f7fe5b0c3faf7d157d9ed99107720fab7bcb2711df4ea4ce8c!@mailstronghold-3.zmailcloud.com>
References: <844840869.114000858.1485299485194.JavaMail.zimbra@peachymango.org> <20170124235626.042F960836B0@rock.dv.isc.org> <158901d276b3$387d6050$a97820f0$@huitema.net> <CAAiTEH_4WgdmMZQm5nbFbvweibkZ0DAo2feN91zftspD4EbWjg@mail.gmail.com> <WM!572ad9a6ae19416c99bd6357d98a5df59a81b46a887701f7fe5b0c3faf7d157d9ed99107720fab7bcb2711df4ea4ce8c!@mailstronghold-3.zmailcloud.com>
Subject: Re: IPv4 outage at next IETF in Chicago
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_115436951_669331747.1485371218219"
X-Mailer: Zimbra 8.6.0_GA_1194 (ZimbraWebClient - FF50 (Mac)/8.6.0_GA_1194)
Thread-Topic: IPv4 outage at next IETF in Chicago
Thread-Index: lp65yxDUqDig0Ro0HLTJeAsRfDbZWQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PgoSc7Eh9qW_VN3TXlO98y8M_Gw>
Cc: Christian Huitema <huitema@huitema.net>, IETF <ietf@ietf.org>
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: Wed, 25 Jan 2017 19:07:03 -0000

Besides all the passive aggressiveness of some responses, I like what Paul Hoffman proposed and I would be game to help run this... However I don't have control on the IETF network. How would I go about requesting an SSID for IPv6-only with NAT64/DNS64 is setup? 

I would take care of running a jabber channel, encourage people to switch and test, create some forms to collect experience and report back. 

I would even be willing to offer a real vintage LinkedIn IPv6 polo shirt as prize... ;)

v2.3.2 | Report a Bug | By Email