LoRaWAN Authentication in RADIUS
draft-garcia-radext-radius-lorawan-02

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          D. Garcia
Internet-Draft                                                  R. Marin
Intended status: Experimental                       University of Murcia
Expires: May 4, 2017                                        A. Kandasamy
                                                                A. Pelov
                                                                  Acklio
                                                        October 31, 2016

                    LoRaWAN Authentication in RADIUS
                 draft-garcia-radext-radius-lorawan-02

Abstract

   This document describes a proposal for adding LoRaWAN support in
   RADIUS.  The purpose is to integrate the LoRaWAN network join
   procedure with an Authentication, Authorization and Accounting (AAA)
   infrastructure based on RADIUS.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Garcia, et al.             Expires May 4, 2017                  [Page 1]
Internet-Draft               LoRaWAN-RADIUS                 October 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  LoRaWAN support in RADIUS . . . . . . . . . . . . . . . . . .   4
   3.  LoRaWAN Overview  . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  LoRaWAN join procedure Key Material . . . . . . . . . . .   4
     3.3.  LoRaWAN joining procedure . . . . . . . . . . . . . . . .   5
     3.4.  LoRaWAN Key Derivation  . . . . . . . . . . . . . . . . .   6
   4.  Integration Overview  . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Mapping LoRaWAN Entities to AAA Infrastructure  . . . . .   7
     4.2.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Protocol Exchange . . . . . . . . . . . . . . . . . . . .   7
       4.3.1.  Join-Request Attribute  . . . . . . . . . . . . . . .   8
       4.3.2.  Join-Answer Attribute . . . . . . . . . . . . . . . .   9
       4.3.3.  AppSKey Attribute . . . . . . . . . . . . . . . . . .  10
       4.3.4.  NwkSKey Attribute . . . . . . . . . . . . . . . . . .  11
       4.3.5.  Table of Attribute  . . . . . . . . . . . . . . . . .  11
   5.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Proof of concept implementation . . . . . . . . . . . . . . .  13
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   Low Power Wide Area Network (LP-WAN) groups several radio
   technologies that allow communications with nodes far from the
   central communication endpoint (base station) in the range of
   kilometers depending on the specifics of the technology and the
   scenario.  They are fairly recent and the protocols to manage those
   infrastructures are in continuous development.  In some cases they
   may not consider aspects such as key management or directly tackle
Show full document text