IETF Logo Mail Archive

[hackathon] FW: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Wed, 16 August 2017 19:14 UTC

Return-Path: <eckelcu@cisco.com>
X-Original-To: hackathon@ietfa.amsl.com
Delivered-To: hackathon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D470D1326CB for <hackathon@ietfa.amsl.com>; Wed, 16 Aug 2017 12:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 UAmlnyYQpFv5 for <hackathon@ietfa.amsl.com>; Wed, 16 Aug 2017 12:14:01 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 835441326AE for <hackathon@ietf.org>; Wed, 16 Aug 2017 12:14:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3368; q=dns/txt; s=iport; t=1502910841; x=1504120441; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=PqqTsyWKitp3znofM1uQkkL8nGBjYdBnht3HRagIUgc=; b=J+/G+pq8OX08FXsH6wDH4/lVAm/UE/wxtiPZHynrkSOOov3y0lM9jtcH Al/JLHBhEIM583z3hi3hsJKWDrgSOVPZjvfETwBtC3gf8WQulT4hsV5nX h0bCWe/5jniR/wBtoZlsVR3pskWMWi9gZUYGGhmIYFcADV75IaWDZFUIu 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CaAADZmJRZ/5NdJa1dGQEBAQEBAQEBAQEBBwEBAQEBg1pkgRUHjguQEIFulhmCEiELhRsCGoQsPxgBAgEBAQEBAQFrHQuFGAEBAQEDASIROgMIDAQCAQgRAwECAQICJgICAiYKFQYBAQUDAgQOBYowEKpzgiaLXAEBAQEBAQEBAQEBAQEBAQEBAQEBAR2BC4IdggKDLgErgnyFGYJtMIIxBaBFAodShm2GAYJpj3OWGgEfOIEKdxVJEgGHB3YBAYhRgQ8BAQE
X-IronPort-AV: E=Sophos;i="5.41,384,1498521600"; d="scan'208";a="281717843"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Aug 2017 19:14:00 +0000
Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v7GJE0qA031011 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 16 Aug 2017 19:14:00 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 16 Aug 2017 14:14:00 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Wed, 16 Aug 2017 14:13:59 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "hackathon@ietf.org" <hackathon@ietf.org>
CC: Lee Howard <lee@asgard.org>
Thread-Topic: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
Thread-Index: AQHS/s72kLMVBj7jjUiP+v4GRBo4o6JqGRkAgAAK1QCAAQWqAIAAExMAgABBOwCAAeqHAIAAT3EAgACtt4CAAGiKgIAABDcAgAAD94CAAAGcgIAAGigAgAA6vQCAFUgbAIADIoEA///ROAA=
Date: Wed, 16 Aug 2017 19:13:59 +0000
Message-ID: <2E97652C-E61D-425E-A06E-4B99549DF34B@cisco.com>
References: <m2y3r7gmb9.wl-randy@psg.com> <20170730231102.1014.qmail@ary.lan> <m2y3r5w991.wl-randy@psg.com> <21320.1501510627@obiwan.sandelman.ca> <c2b6c568-f9c1-049f-78ef-89cb2c7c44b1@gmail.com> <6857AD5A-632E-4264-B76F-FFEC760E46A4@fugue.com> <alpine.OSX.2.01.1707311349320.2496@rabdullah.local> <6C3D3B7C-9732-4BD2-97F6-F03A00CB6781@fugue.com> <3A586681-AAEC-4395-B386-450C0AE7950F@vpnc.org> <m2r2wwt4vx.wl-randy@psg.com> <F4D3D8A8-D536-4054-838D-320B3A7EA4FD@istaff.org> <D5B9D471.8118C%lee@asgard.org>
In-Reply-To: <D5B9D471.8118C%lee@asgard.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.22.0.170515
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.179.12]
Content-Type: text/plain; charset="utf-8"
Content-ID: <245898C9697EC1459C73BE0827D96167@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/x9NXmG7ttXHeMgoy_TUQnFdb0mI>
Subject: [hackathon] FW: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-BeenThere: hackathon@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hackathon>, <mailto:hackathon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon/>
List-Post: <mailto:hackathon@ietf.org>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hackathon>, <mailto:hackathon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Aug 2017 19:14:04 -0000

Forwarding to the hackathon list. Sounds like a great project, Lee. Thanks for championing it.

-----Original Message-----
From: ietf <ietf-bounces@ietf.org> on behalf of Lee Howard <lee@asgard.org>
Date: Wednesday, August 16, 2017 at 8:01 AM
To: John Curran <jcurran@istaff.org>, Randy Bush <randy@psg.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RESENDING - Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

    
    
    On 8/14/17, 11:09 AM, "ietf on behalf of John Curran"
    <ietf-bounces@ietf.org on behalf of jcurran@istaff.org> wrote:
    
    >On 31 Jul 2017, at 8:10 PM, Randy Bush <randy@psg.com> wrote:
    >> ...
    >>
    >To that end, would it be possible for those behind the "IPv6-only Wi-Fi
    >for IETF”
    >draft to partner with the NOC at the upcoming meeting to help debug
    >issues that 
    >are reported on “ietf-nat64* and publish the results?  The IETF does have
    >a wide
    >variety of users, which is really helpful in finding edge cases with
    >protocols that
    >might have issues and otherwise go undiscovered.  If it were may clear
    >(e.g. during
    >the opening) that there is a goal to put the “ietf-nat64” network through
    >its paces
    >and that there would be a post-mortem I-D as a result, I suspect quite a
    >few folks
    >would at least give that setup a try for a while, with the goal of
    >finding and reporting
    >breakage.
    
    
    As promised, I have proposed an "IPv4-IPv6 Transition Technology Interop”
    for the IETF100 Hackathon:
    Description at: 
    https://www.ietf.org/registration/MeetingWiki/wiki/100hackathon
    Discussion/planning list:
    http://lists.retevia.net/listinfo.cgi/v6-interop-retevia.net
    Hackathon registration and mailing list at
    https://www.ietf.org/hackathon/100-hackathon.html
    
    I have two versions of NAT64 planned (A10, VPP). I would like to compare
    to at least 464xlat (probably with CLAT on gateway, not device) to address
    some of the comments in the thread. I’d also like to compare other
    transition technologies, such as DS-Lite and MAP-T/MAP-E, though these are
    probably more interesting to the rest of the Internet than to the narrow
    question of what the IETF should do. All of that, of course, is subject to
    people wanting to do it, and proper planning ahead of time.
    
    
    Lee

v2.23.0 | Report a Bug | By Email