IETF Logo Mail Archive

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

Alan DeKok <aland@deployingradius.com> Wed, 03 December 2014 22:17 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 7C0A31ACDBB for <secauth@ietfa.amsl.com>; Wed, 3 Dec 2014 14:17:49 -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 erV8Sq4H4WmG for <secauth@ietfa.amsl.com>; Wed, 3 Dec 2014 14:17:48 -0800 (PST)
Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF1C1A6FF9 for <secauth@ietf.org>; Wed, 3 Dec 2014 14:17:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 6409B224042D; Wed, 3 Dec 2014 23:17:42 +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 GmWezUjL7Pxy; Wed, 3 Dec 2014 23:17:42 +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 7CB8B224013A; Wed, 3 Dec 2014 23:17:41 +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: <00b601d00f45$83033550$89099ff0$@rozanak.com>
Date: Wed, 03 Dec 2014 17:17:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7A0D556-0808-42BE-915C-4827FB4218DD@deployingradius.com>
References: <814D0BFB77D95844A01CA29B44CBF8A7A7D2F1@lhreml513-mbb.china.huawei.com> <13B39BFF-50D1-4892-A159-9F8F75BC5C6B@deployingradius.com> <BC5E7A40-8A54-4FEA-9C97-66F194080D74@um.es> <1C6C4744-6FAC-493F-BE48-B0E7821F8A20@deployingradius.com> <00b601d00f45$83033550$89099ff0$@rozanak.com>
To: Hosnieh Rafiee <ietf@rozanak.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/secauth/_ODgV4imOyaj3N5Zhd63HqsKgPc
Cc: 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 22:17:49 -0000

On Dec 3, 2014, at 5:07 PM, Hosnieh Rafiee <ietf@rozanak.com> wrote:

> What if the new network infrastructure changes the role of these companies?

  It likely will change the role.  But… most of them have been around for decades.  They are likely to stay, if only to service legacy equipment.

> Even the role of many hardware companies might change... and they are aware
> of this fact... 
> How can you find a role for them in the new infrastructure with SDN/NFV
> players? 

  I don’t know.  That isn’t really my concern.  If they want to be part of new systems, they will have to figure out how to do that themselves.

> What is the motivation for hotels to support cross domain authentication?

  I have no idea.  I was referencing your slides.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email