IETF Logo Mail Archive

Re: [OPSAWG] [dhcwg] AD sponsoring - draft-wkumari-dhc-capport-07

Ted Lemon <Ted.Lemon@nominum.com> Fri, 23 January 2015 13:08 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 035231A90B5; Fri, 23 Jan 2015 05:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 SLLmz9PkeRZ1; Fri, 23 Jan 2015 05:08:41 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 88B141A90AF; Fri, 23 Jan 2015 05:08:41 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 443CCDA0360; Fri, 23 Jan 2015 13:08:41 +0000 (UTC)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id E133953E080; Fri, 23 Jan 2015 05:08:40 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 23 Jan 2015 05:08:40 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <D7CD39F9-217E-4C06-ACAE-68AF7CA024B1@employees.org>
Date: Fri, 23 Jan 2015 08:08:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <FE855396-C6B1-448E-AC1A-EB33F084B208@nominum.com>
References: <54A9B162.1040407@bogus.com> <1C56356A-A644-4E6E-AACF-D50183F467A4@nominum.com> <D7CD39F9-217E-4C06-ACAE-68AF7CA024B1@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/a_5Gt1SDEF-HKn6pCNBFSFhivUQ>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Subject: Re: [OPSAWG] [dhcwg] AD sponsoring - draft-wkumari-dhc-capport-07
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 13:08:43 -0000

On Jan 23, 2015, at 5:23 AM, Ole Troan <otroan@employees.org> wrote:
> is this needed when you have 802.11u?

I've never actually seen an example of 802.11u in the wild.   Have you?   What I see in the wild are layer 3 solutions based on spoofing.   It would certainly be worth investigating this question, but I think even if 802.11u did see wide deployment in large WiFi network scenarios, this would still be useful for the coffee-shop scenario.

> does it conflict or should it be integrated with the prefix properties inhttp://tools.ietf.org/html/draft-lepape-6man-prefix-metadata-00

It seems orthogonal, but it sounds like you think it's not, so it might be worth you exploring that a bit more!

> what's this proposals relationship with MIF's PVDs?

I think it's orthogonal.   This doesn't really change what a hotspot network looks like--it just makes it possible to flag a network as a hotspot network without any skullduggery.

v2.23.0 | Report a Bug | By Email