IETF Logo Mail Archive

Re: [Secauth] secauth use case - What is next?

Alan DeKok <aland@deployingradius.com> Wed, 03 December 2014 18:46 UTC

Return-Path: <aland@deployingradius.com>
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 1EAAF1A9084 for <secauth@ietfa.amsl.com>; Wed, 3 Dec 2014 10:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 cIGp9EhloFWK for <secauth@ietfa.amsl.com>; Wed, 3 Dec 2014 10:46:13 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id E655A1A907C for <secauth@ietf.org>; Wed, 3 Dec 2014 10:45:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 50400224046C; Wed, 3 Dec 2014 19:45:55 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NsXw-U9euJOf; Wed, 3 Dec 2014 19:45:47 +0100 (CET)
Received: from [192.168.20.59] (69-196-165-104.dsl.teksavvy.com [69.196.165.104]) by power.freeradius.org (Postfix) with ESMTPSA id C99B52240467; Wed, 3 Dec 2014 19:45:46 +0100 (CET)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <13B39BFF-50D1-4892-A159-9F8F75BC5C6B@deployingradius.com>
Date: Wed, 03 Dec 2014 13:45:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FCEDB477-8123-4E7C-BF83-9F6E0E3ABEB3@deployingradius.com>
References: <814D0BFB77D95844A01CA29B44CBF8A7A7D2F1@lhreml513-mbb.china.huawei.com> <13B39BFF-50D1-4892-A159-9F8F75BC5C6B@deployingradius.com>
To: Hosnieh Rafiee <hosnieh.rafiee@huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/Bq_uxGzGUKgjMwgHszxfJElPSkA
Cc: "secauth@ietf.org" <secauth@ietf.org>
Subject: Re: [Secauth] secauth use case - What is next?
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: Wed, 03 Dec 2014 18:46:14 -0000

On Dec 3, 2014, at 1:44 PM, Alan DeKok <aland@deployingradius.com> wrote:
> I have no idea what that means.  RADIUS is *widely* used on cross-domain authentication.  I can say without exaggeration that outside of 3G, it’s the *only* protocol used for cross-domain authentication.

  Make that “network access” cross-domain authentication.

  If you have network access, things like OAuth are widely used, and are more appropriate.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email