IETF Logo Mail Archive

Re: Security for the IETF wireless network

Tim Wicinski <tjw.ietf@gmail.com> Fri, 25 July 2014 12:53 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D92A81B2857; Fri, 25 Jul 2014 05:53: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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 cy6QDQdoaZZK; Fri, 25 Jul 2014 05:53:46 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D9EE1B2839; Fri, 25 Jul 2014 05:53:46 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id t60so4258585wes.20 for <multiple recipients>; Fri, 25 Jul 2014 05:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=EEPDwmSxjCBV2rOr+Fm5Di4cHhcRfGaM5hP/Fkf+Jiw=; b=LAa3vTg8pvlhDgGs1en957Qztngy9jU9QmvIhZUxKCLx/wevutwTVs2StlGff6YMR3 cJAhO2zXOml1PA3fV0x4dLX3QCyGKY06DphGjM02c37LTd4GUEyFBq7gPHDtdLd+ktnD MtSn/XGhJZPhbv9WFe72i7qpwHFqRQ+HsSCN80oc1+y0c8hoyuOS4BsnTeZwybCxfteW BWPeGhUKxdXxFXqb1ApsfIrgiTtJ4oEkcNqKOdBuqhQXBZ9ibcvL1EgmeMCzdXQkhMhy jJmuxQzEYFzbm+kpM9YZWMTSOvfNpvDEEmcXbSoHfRyHkbqlWJIfNBCeGxWTt046CELd gylA==
X-Received: by 10.194.249.98 with SMTP id yt2mr22033953wjc.66.1406292824810; Fri, 25 Jul 2014 05:53:44 -0700 (PDT)
Received: from dhcp-9311.meeting.ietf.org (dhcp-9311.meeting.ietf.org. [31.133.147.17]) by mx.google.com with ESMTPSA id wd7sm25054551wjc.36.2014.07.25.05.53.42 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Jul 2014 05:53:43 -0700 (PDT)
Message-ID: <53D25353.4080403@gmail.com>
Date: Fri, 25 Jul 2014 08:53:39 -0400
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Thunderbird/33.0a2
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>, "George, Wes" <wesley.george@twcable.com>, "ietf@ietf.org" <ietf@ietf.org>, IETF Chair <chair@ietf.org>
Subject: Re: Security for the IETF wireless network
References: <0FE63216-9BE8-450F-80FB-D1DB6166DFEF@ietf.org> <CFF7BBD1.28A2F%wesley.george@twcable.com> <53D24DE4.1030107@bogus.com>
In-Reply-To: <53D24DE4.1030107@bogus.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0Y9SfwbsAssvczRSE6y_iWnKHK8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 25 Jul 2014 12:53:48 -0000


On 7/25/14 8:30 AM, joel jaeggli wrote:
> On 7/25/14, 7:59 AM, George, Wes wrote:
>> Jari, while I support this idea, if I had to prioritize, I'd rather us
>> focus on consistently offering *any* secured WiFi option in the hotel
>> rooms.
>>
>> Here at the Fairmont, for example: ietf-hotel is the only SSID available,
>> and it's not secure. Yes, one could use wired, assuming one's widget has
>> an ethernet plug, but many now don't.
>
> If you have the luxury of a wired port, deploying your own ap will
> probably get you more deterministic service, and a secure air interface.
> prefix delegatation is probably  something we need to do.
>
> The amount of control we have over the hotels infrastruture varies, this
> time it's a meru controller and we were able to change the ssid and get
> it to bridge ipv6 which are both tiny miracles.
>

I have been carrying some type of access point in my luggage for the 
last decade. Currently it's an AirPort Express, but someone posted this 
earlier in the week and I was immediately intrigued:

http://www.ebay.com/itm/171085144197?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649

tim

v2.23.0 | Report a Bug | By Email