Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6

Ted Lemon <Ted.Lemon@nominum.com> Fri, 27 February 2015 16:24 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860381ACDBA for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 08:24:42 -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 Bws6qdq8-ZPA for <dhcwg@ietfa.amsl.com>; Fri, 27 Feb 2015 08:24:39 -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 353FF1ACDBC for <dhcwg@ietf.org>; Fri, 27 Feb 2015 08:24:37 -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 1E53BDA01DB for <dhcwg@ietf.org>; Fri, 27 Feb 2015 16:24:37 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (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 EB6F253E0AC; Fri, 27 Feb 2015 08:24:36 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 27 Feb 2015 08:24:36 -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: <m2vbinz79d.wl-Niall.oReilly@ucd.ie>
Date: Fri, 27 Feb 2015 11:24:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <A8B2E576-0498-4352-8A2F-AC8D7812E344@nominum.com>
References: <201502211924.t1LJOZd9062437@givry.fdupont.fr> <91CF04C8-616A-4223-BB1F-B41941E176D0@nominum.com> <CAJE_bqcq-Q2+FiewZxp9VbP5+5c2ynFZrX3zhcfrPt+V8DDdDw@mail.gmail.com> <DC180CDE-E2B8-4D2F-8B92-A65BCCD43CBD@nominum.com> <CAJE_bqcn5gB35fOKDhpKG_3_hk7vahr7BZL28hGo4Q1HpTCTdw@mail.gmail.com> <470A8FD2-F4C7-4A3C-A971-E9AFD0EF1F2E@nominum.com> <CAJE_bqf6_C=e65uNHMDqB3v1H-vtfN8+q3Lb11nGHFEx6Y=XvQ@mail.gmail.com> <CDF58485-F7A9-4109-920D-3D498ED7CC3F@nominum.com> <CAJE_bqe1V9uA1GrHGpn=O7UqZXQm2nBqN8gMGB9YLqMJC0rwcA@mail.gmail.com> <C0E43F78-ADFB-4416-866C-13697F8C4C9E@nominum.com> <m2vbinz79d.wl-Niall.oReilly@ucd.ie>
To: Niall O'Reilly <niall.oreilly@ucd.ie>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/pB92idq3hl0VMnNySEb_6fE7qBU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>, 神明達哉 <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 16:24:42 -0000

On Feb 27, 2015, at 10:47 AM, Niall O'Reilly <niall.oreilly@ucd.ie> wrote:
>  So, TOFU?

Depends on what you are trying to do.   If you just want to make sure that client A doesn't swipe client B's resources, TOFU is all you need.   If you want to do some kind of RADIUS transaction, as we talked about previously, there's probably some sort of captive portal registration process.