RADIUS Attribute Security
draft-aravind-radext-attribute-security-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-17
Stream (None)
Intended RFC status (None)
Formats plain text 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)
RADIUS EXTensions Working Group        Sanal Kumar Kariyezhath Sivaraman
INTERNET-DRAFT                                  Aravind Prasad Sridharan
Intended Status: Standards Track                                    DELL
Expires: August 21, 2017                               February 17, 2017

                       RADIUS Attribute Security
               draft-aravind-radext-attribute-security-00

Abstract

   This document specifies a simple method to provide security to RADIUS
   message attribute values.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 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
 

Sanal, et al.           Expires August 21, 2017                 [Page 1]
INTERNET DRAFT         RADIUS Attribute Security       February 17, 2017

   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2  Attribute Security in RADIUS messages . . . . . . . . . . . . .  3
     2.1  SEC-Message Attribute . . . . . . . . . . . . . . . . . . .  4
   3  Example Message Flow with Sample data . . . . . . . . . . . . .  5
     3.1  Client  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.2  Server  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   4  Recommendations . . . . . . . . . . . . . . . . . . . . . . . .  8
   5  Advantages  . . . . . . . . . . . . . . . . . . . . . . . . . .  8
   6  Security Considerations . . . . . . . . . . . . . . . . . . . .  8
   7  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  8
   8  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     8.1  Normative References  . . . . . . . . . . . . . . . . . . .  8
     8.2  Informative References  . . . . . . . . . . . . . . . . . .  8
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

1  Introduction

   The RADIUS protocol [RFC2865] is a widely deployed authentication and
   authorization protocol.  The supplementary RADIUS Accounting
   specification [RFC2866] provides accounting mechanisms, thus
   delivering a complete authentication, Authorization, and Accounting
   (AAA) solution.  However, the major drawback is the lack of security
   for the message contents such as sensitive attributes. 

   Although RADIUS over TLS addresses this issue, it involves
   significant cost and PKI deployment hassles. This draft proposal
   provides a mechanism to secure RADIUS message without any major
   change in the existing RADIUS server deployments.

   Here the proposal is to encrypt the attribute value with a key using
   a symmetric cipher. To have less change in the existing deployment
   and to have a simplified key management, this proposal leverages the
   shared secret as one of the factor in making the key that is required
   for encryption.   

 

Sanal, et al.           Expires August 21, 2017                 [Page 2]
INTERNET DRAFT         RADIUS Attribute Security       February 17, 2017

1.1  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].
Show full document text