Re: [lp-wan] overview issue#2: AAA server term...

Arun <arun@acklio.com> Thu, 18 May 2017 15:29 UTC

Return-Path: <arun@acklio.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F93129B4D for <lp-wan@ietfa.amsl.com>; Thu, 18 May 2017 08:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.802
X-Spam-Level:
X-Spam-Status: No, score=0.802 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MvZuiMKxeuKk for <lp-wan@ietfa.amsl.com>; Thu, 18 May 2017 08:29:45 -0700 (PDT)
Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [IPv6:2001:4b98:c:538::199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39147128B4E for <lp-wan@ietf.org>; Thu, 18 May 2017 08:24:18 -0700 (PDT)
Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by relay9-d.mail.gandi.net (Postfix) with ESMTPS id 60D124074A for <lp-wan@ietf.org>; Thu, 18 May 2017 17:24:16 +0200 (CEST)
Received: from mfilter17-d.gandi.net (mfilter17-d.gandi.net [217.70.178.145]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id DEDA2FB8FB for <lp-wan@ietf.org>; Thu, 18 May 2017 17:24:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter17-d.gandi.net
Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter17-d.gandi.net (mfilter17-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id U63bi75ngg5N for <lp-wan@ietf.org>; Thu, 18 May 2017 17:24:15 +0200 (CEST)
X-Originating-IP: 192.44.77.204
Received: from [192.168.1.157] (nat-asr-incub-b204.rennes.enst-bretagne.fr [192.44.77.204]) (Authenticated sender: arun@acklio.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 30289FB8CE for <lp-wan@ietf.org>; Thu, 18 May 2017 17:24:14 +0200 (CEST)
To: lp-wan@ietf.org
References: <6a4c386b-4b23-569f-c32a-09d546e7e681@cs.tcd.ie>
From: Arun <arun@acklio.com>
Message-ID: <1fec4a42-3477-d8c1-ce6d-d2d8cd4b568c@acklio.com>
Date: Thu, 18 May 2017 17:23:57 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <6a4c386b-4b23-569f-c32a-09d546e7e681@cs.tcd.ie>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="e1QQ1R6ExOOoTdItm4WAO2rHPGV62AnWU"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/1iyuYXFU8EF3xqgvlbfVELN6eSY>
Subject: Re: [lp-wan] overview issue#2: AAA server term...
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 May 2017 15:29:47 -0000

Hi Stephen,
There is a draft, draft-garcia-radext-radius-lorawan, that explains the
use of AAA server in lpwa technologies like lora.
The idea is to use standardized solutions like AAA for authenticating
end devices in such technologies.
IMHO, AAA term in a way is good to push for the use of standard entities
in the architecture.

regards,
Arun

On 18/05/2017 09:41, Stephen Farrell wrote:
> Hiya,
>
> (Crap: I mucked up the subject line by also calling this "issue#1"
> when I first sent this, maybe that's why nobody responded - so
> trying now with a correct subject line and with a suggested
> resolution in case nobody else cares... :-)
>
> In [1] we define the term "AAA server." I don't think that's a good
> term to use, as it may be read to assume that we'll end up with a
> RADIUS or Diameter based solution and a typical AAA server like that
> is just not the same as a LoRaWAN NS/JS. (There might be a RADIUS or
> Diameter server behind such a beast, but it's not the same thing.)
> I think (less sure though) that the "AAA server" is also not so good
> for the other technologies too.
>
> What'd the WG like to do here?
>
> If nobody answers, in the next revision I'll use the term "LPWAN
> back-end server" ("LBES") instead of "AAA server." That's also not
> great but at least doesn't have the potential to create new confusion.
>
> Cheers,
> S.
>
> [1] https://tools.ietf.org/html/draft-ietf-lpwan-overview-02#section-3
>
>
>
>
>
> _______________________________________________
> lp-wan mailing list
> lp-wan@ietf.org
> https://www.ietf.org/mailman/listinfo/lp-wan