IETF Logo Mail Archive

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

Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com> Thu, 18 May 2017 16:06 UTC

Return-Path: <juancarlos.zuniga@sigfox.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 06F431294AB for <lp-wan@ietfa.amsl.com>; Thu, 18 May 2017 09:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.69
X-Spam-Level:
X-Spam-Status: No, score=-4.69 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sigfoxgroup.onmicrosoft.com
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 s_oAe1-fuSe8 for <lp-wan@ietfa.amsl.com>; Thu, 18 May 2017 09:06:30 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10126.outbound.protection.outlook.com [40.107.1.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36668129548 for <lp-wan@ietf.org>; Thu, 18 May 2017 09:01:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigfoxgroup.onmicrosoft.com; s=selector1-sigfox-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nBeJ5JbdJfKuLOLoXP28gnuEIcQY1YLBdxhKB0zvwEU=; b=WWyczxi1DQGRvOoZ8vu7RfNW/P2kxxodr9Ys/kiao0PU4euynIO4uCiCd5dEIhueTkYmB8VcrlTvPZUUTvNVi6jZy6ctwDMWP2KQGpalbSPy/ieByggRrePKYgn9mMovpEUX+mfYn7c1XTZei+8+Kw8eIneehOkxzsVBoAm2N0Q=
Received: from DB6PR08MB2679.eurprd08.prod.outlook.com (10.175.235.12) by DB6PR08MB2680.eurprd08.prod.outlook.com (10.175.235.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.14; Thu, 18 May 2017 16:01:20 +0000
Received: from DB6PR08MB2679.eurprd08.prod.outlook.com ([fe80::3c08:54b8:1c7c:498a]) by DB6PR08MB2679.eurprd08.prod.outlook.com ([fe80::3c08:54b8:1c7c:498a%13]) with mapi id 15.01.1101.011; Thu, 18 May 2017 16:01:20 +0000
From: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>
To: Arun <arun@acklio.com>, "lp-wan@ietf.org" <lp-wan@ietf.org>
Thread-Topic: [lp-wan] overview issue#2: AAA server term...
Thread-Index: AQHSz6sAUOs+OLzI+0ux6AoVKl9EYKH6NjKAgAAH/eA=
Date: Thu, 18 May 2017 16:01:20 +0000
Message-ID: <DB6PR08MB26799EC47E945CF45AFCDBE689E40@DB6PR08MB2679.eurprd08.prod.outlook.com>
References: <6a4c386b-4b23-569f-c32a-09d546e7e681@cs.tcd.ie> <1fec4a42-3477-d8c1-ce6d-d2d8cd4b568c@acklio.com>
In-Reply-To: <1fec4a42-3477-d8c1-ce6d-d2d8cd4b568c@acklio.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: acklio.com; dkim=none (message not signed) header.d=none;acklio.com; dmarc=none action=none header.from=sigfox.com;
x-originating-ip: [104.163.146.252]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR08MB2680; 7:309oaLAMaSPE+3j6zn2r0MuJNYYZApTIlfsQwCSYlpUzT75TWVWwN9ykYTP9hgkdTY74XJ5nRC4S8lPoS3eg1tupLvmAKXYNxTA+1JSdACvpcRTQxAjqMxQfFcLu+fzPbNBrukZav7HnEXORQ/h+p2rTQhDtA3RAtQjTeOI80BBpMRuBZoj2oM9EMcODMF7WnOVzzzK5IzARH71u8znCu1GexNgEvAS6MhXBGNbVSiyT5pIGkS+bsSHK/aEuj9bAWdLNUZ3KNiHt2UhGA6GSOoYoC8UZoIqEYKCdZKBGrpKqYSkAq8e1G3YR9TgiPC1YLDoSaR6d97maXIW9ABP3WQ==
x-ms-traffictypediagnostic: DB6PR08MB2680:
x-ms-office365-filtering-correlation-id: 529bd57b-d211-4533-65a9-08d49e07200d
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:DB6PR08MB2680;
x-microsoft-antispam-prvs: <DB6PR08MB2680B748F67F7C676CF76DC289E40@DB6PR08MB2680.eurprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(20161123558100)(20161123555025)(20161123560025)(6072148); SRVR:DB6PR08MB2680; BCL:0; PCL:0; RULEID:; SRVR:DB6PR08MB2680;
x-forefront-prvs: 0311124FA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400002)(39450400003)(39410400002)(39400400002)(377454003)(24454002)(7696004)(2906002)(561944003)(7736002)(3280700002)(7906003)(74316002)(50986999)(38730400002)(54356999)(2501003)(5250100002)(189998001)(478600001)(966005)(2900100001)(66066001)(99286003)(9686003)(8676002)(55016002)(54896002)(6306002)(33656002)(9326002)(8936002)(236005)(25786009)(53546009)(6506006)(606005)(5660300001)(6246003)(86362001)(53936002)(6436002)(3846002)(3660700001)(6116002)(102836003)(81166006)(2950100002)(76176999)(790700001)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR08MB2680; H:DB6PR08MB2679.eurprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB6PR08MB26799EC47E945CF45AFCDBE689E40DB6PR08MB2679eurp_"
MIME-Version: 1.0
X-OriginatorOrg: sigfox.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2017 16:01:20.3139 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fcbc8bb1-061e-4b94-9f70-3ad917b0c8d3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR08MB2680
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/zEAbLlWIGXN-_Kt3XAnmaZbNJjo>
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 16:06:32 -0000

Hi,

I tend to agree with Stephen in that assuming a RADIUS or Diameter server is not generic enough. Even though a solution like the one proposed in draft-garcia-radext-radius-lorawan might be suitable for certain technologies like LoRaWAN, there are other protocols like Sigfox which don't have a joining procedure or an authentication message exchange (i.e. every message is individually authenticated). Therefore, Stephen's proposal to use LBES instead of AAA sounds like a good generic solution.

Best,

Juan Carlos


From: lp-wan [mailto:lp-wan-bounces@ietf.org] On Behalf Of Arun
Sent: May 18, 2017 11:24 AM
To: lp-wan@ietf.org
Subject: Re: [lp-wan] overview issue#2: AAA server term...

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<mailto:lp-wan@ietf.org>

https://www.ietf.org/mailman/listinfo/lp-wan

v2.23.0 | Report a Bug | By Email