Re: [Secauth] Closing SecAuth list

Paul Lambert <paul@nymbus.net> Tue, 13 January 2015 21:47 UTC

Return-Path: <paul@nymbus.net>
X-Original-To: secauth@ietfa.amsl.com
Delivered-To: secauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E841AC3E2 for <secauth@ietfa.amsl.com>; Tue, 13 Jan 2015 13:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 gJJrI1Qc0e3K for <secauth@ietfa.amsl.com>; Tue, 13 Jan 2015 13:47:41 -0800 (PST)
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C42BE1A8BB2 for <secauth@ietf.org>; Tue, 13 Jan 2015 13:47:41 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id uz6so4935203obc.5 for <secauth@ietf.org>; Tue, 13 Jan 2015 13:47:41 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Z8vXWSNs/6ooj+t2TxepZb0ohKDhFRlkoRd04ZCaBUo=; b=aqcleX1mpe+fFNh9oYm18yVQuwScDY7eYdTJIYFju17C2wcBsZq1B0g6QWbU+bcidu hEKry3Mhs7agEIqHtuzA5a3t9lkcREn9QFjwZt1qGTw1NMkouDEwteNaaagrMu03Dvik H+mZggm7wEh1Lnx30I3mKEb7fOJJ+cb7nig3+DgP3+H0DMOD5jg21zOW6r8a1C7pE34t 2tIa+dQazTb8XwrW27shPAni17nviqJZnoZZiPPsihDnEgFzoGr+yn3fAmJ+M6WxlSGA wcqRSngFIBRiJO5n4IH8MQqX+mJx9yK4NmP/8GyAPL/tISA2fg+UYOkuhLCDmgi9nq84 Vfow==
X-Gm-Message-State: ALoCoQku3fkov5Rrkitmba13Twjx6TBkg/TrCH6sIyfDw7XnIc0eLEkVbXYfsyFXeLxiNVXep2KY
X-Received: by 10.202.81.133 with SMTP id f127mr342545oib.112.1421185661201; Tue, 13 Jan 2015 13:47:41 -0800 (PST)
Received: from ?IPv6:2602:304:b25c:1a70:cc3a:a636:14db:903? ([2602:304:b25c:1a70:cc3a:a636:14db:903]) by mx.google.com with ESMTPSA id fi4sm11193059obb.16.2015.01.13.13.47.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 13 Jan 2015 13:47:40 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Paul Lambert <paul@nymbus.net>
In-Reply-To: <35E57B9D-DC0E-46DF-B7E0-752069D0B79B@deployingradius.com>
Date: Tue, 13 Jan 2015 13:47:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD32C24C-E98F-4996-ADCE-E472D77CE432@nymbus.net>
References: <CAHbuEH45CtkRsPvjYXU-tRE6PBbufDztAJ=SGOwgGSp76DvjWQ@mail.gmail.com> <DUB119-DS5A9C15A543028B641DEC8B1400@phx.gbl> <CAHbuEH6Qi5yRXVCS8T=Baz7_p0CHhq6qKk5kBVUy6-mSnDyB8Q@mail.gmail.com> <54B544DB.9040002@gmail.com> <CAHbuEH7mdiZeeasXRd8PFygZO-pm1UC=BVDyfk+8pvNxipCHzg@mail.gmail.com> <35E57B9D-DC0E-46DF-B7E0-752069D0B79B@deployingradius.com>
To: Alan DeKok <aland@deployingradius.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: <http://mailarchive.ietf.org/arch/msg/secauth/RKmjBSv_RL8nasnxpsh3TSZ6eAk>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "secauth@ietf.org" <secauth@ietf.org>
Subject: Re: [Secauth] Closing SecAuth list
X-BeenThere: secauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Omni-purpose Network-layer based Secure Authentication and Authorization non-working group discussion list <secauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secauth>, <mailto:secauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secauth/>
List-Post: <mailto:secauth@ietf.org>
List-Help: <mailto:secauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secauth>, <mailto:secauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2015 21:47:44 -0000

> On Jan 13, 2015, at 8:41 AM, Alan DeKok <aland@deployingradius.com> wrote:
> 
> On Jan 13, 2015, at 11:30 AM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> wrote:
>> This is only one of the three problems being discussed and there isn't
>> enough to go forward on yet.  I'm asking that those interested go back
>> and collect thoughts to devise feasible options.  If this is the
>> problem selected, I would also need to see support from those who can
>> make the change (organizations running the wifi hotspots).  I don't
>> see the motivation for them to switch from using a captive portal,
>> especially since they charge for use of the infrastructure they
>> host/provide.
> 
>  I’ve worked with hotspots && providers for a long time.  Many have ads on their captive portal.  That being said, they make their money off of traffic, not landing pages.  They don’t care *how* people log in.  The WiFi alliance has worked on ways for people to automatically log in to hotspots.
Yes.  I helped on some of the Passport 2 certificate details, testing and deployment.

Much work in industry avoids the IETF because of focus mismatch.  The IETF clearly ‘owns’ solutions changing IETF protocols, but it is a less productive forum for industry specific solutions.

However, good solutions for authentication/identity should not be industry specific.
> 
>  But I don’t understand how secauth helps them.  The problem statements are unclear.  The solutions are vast and vague.

Some of the topics on this list have been interesting … but as noted it’s hard to contribute if the target output is unclear.


> 
>> I understand this is an issue for users, but also see
>> that the problem is bigger and involves providers of the service (who
>> have not been participating in the discussion).
> 
>  It will be hard to get hotspot providers to get involved in the IETF.  They’re working with the WiFi alliance, and even then very few of them are involved.
> 
>  This is a larger problem with the IETF.  Getting *production* people involved is hard.
> 
>> Is it worth it for those interested to get together on a single
>> problem and come back with a more clearly defined scope?  If so, it
>> would be great to see that happen and to see some of the concerns
>> addressed by getting involvement/support of service providers.
If done, perhaps a new list could be created with a 
new clearly focused topic.


Paul
> 
>  I agree.
> 
>  Alan DeKok.
> 
> _______________________________________________
> Secauth mailing list
> Secauth@ietf.org
> https://www.ietf.org/mailman/listinfo/secauth