DTLS as a Transport Layer for RADIUS
draft-ietf-radext-dtls-07

The information below is for an old version of the document
Document Type Active Internet-Draft (radext WG)
Last updated 2013-10-09
Replaces draft-dekok-radext-dtls
Stream IETF
Intended RFC status Experimental
Formats pdf htmlized bibtex
Reviews
Stream WG state In WG Last Call
Other - see Comment Log
Document shepherd Jouni Korhonen
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         Alan DeKok
INTERNET-DRAFT                                                FreeRADIUS
Category: Experimental
<draft-ietf-radext-dtls-07.txt>
Expires: October 09, 2014
9 October 2013

                  DTLS as a Transport Layer for RADIUS
                       draft-ietf-radext-dtls-07

Abstract

   The RADIUS protocol [RFC2865] has limited support for authentication
   and encryption of RADIUS packets.  The protocol transports data "in
   the clear", although some parts of the packets can have "obfuscated"
   content.  Packets may be replayed verbatim by an attacker, and
   client-server authentication is based on fixed shared secrets.  This
   document specifies how the Datagram Transport Layer Security (DTLS)
   protocol may be used as a fix for these problems.  It also describes
   how implementations of this proposal can co-exist with current RADIUS
   systems.

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/ietf/1id-abstracts.txt.

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

   This Internet-Draft will expire on January 12, 2014

Copyright Notice

DeKok, Alan                   Experimental                      [Page 1]
INTERNET-DRAFT    DTLS as a Transport Layer for RADIUS    9 October 2013

   Copyright (c) 2013 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

DeKok, Alan                   Experimental                      [Page 2]
INTERNET-DRAFT    DTLS as a Transport Layer for RADIUS    9 October 2013

Table of Contents

1.  Introduction .............................................    4
   1.1.  Terminology .........................................    4
   1.2.  Requirements Language ...............................    5
2.  Building on Existing Foundations .........................    6
   2.1.  Changes to RADIUS ...................................    6
   2.2.  Similarities with RADIUS/TLS ........................    7
      2.2.1.  Changes from RADIUS/TLS to RADIUS/DTLS .........    7
      2.2.2.  Reinforcement of RADIUS/TLS ....................    8
3.  Interaction with RADIUS/UDP ..............................    8
   3.1.  DTLS Port and Packet Types ..........................    9
   3.2.  Server Behavior .....................................    9
4.  Client Behavior ..........................................   10
5.  Connection Management ....................................   10
   5.1.  Server Connection Management ........................   10
      5.1.1.  Session Management .............................   11
   5.2.  Client Connection Management ........................   13
6.  Implementation Guidelines ................................   14
   6.1.  Client Implementations ..............................   14
   6.2.  Server Implementations ..............................   15
7.  Implementation Experience ................................   15
8.  Diameter Considerations ..................................   16
9.  IANA Considerations ......................................   16
10.  Security Considerations .................................   16
   10.1.  Legacy RADIUS Security .............................   17
   10.2.  Resource Exhaustion ................................   18
   10.3.  Client-Server Authentication with DTLS .............   18
   10.4.  Network Address Translation ........................   20
   10.5.  Wildcard Clients ...................................   20
   10.6.  Session Closing ....................................   20
   10.7.  Clients Subsystems .................................   21
11.  References ..............................................   21
   11.1.  Normative references ...............................   21
Show full document text