datatracker.ietf.org
Sign In
Version 4.02, 2012-04-26
Report a bug

Transport Layer Security (TLS) encryption for RADIUS
draft-ietf-radext-radsec-12

Active Internet-Draft (radext WG)
Document Stream: IETF
Last updated: 2012-02-13
Intended RFC status:Experimental
Other versions: plain text, xml, pdf, html

IETF State: Submitted to IESG for Publication (radext)
Document shepherd:Jouni Korhonen

IESG State: RFC Ed Queue
RFC Editor State: AUTH48 REF
Responsible AD:Benoit Claise
IESG Note:Jouni Korhonen (jouni.korhonen@nsn.com) is the Document Shepherd.

RADIUS Extensions Working Group                                S. Winter
Internet-Draft                                                   RESTENA
Intended status: Experimental                                M. McCauley
Expires: August 17, 2012                                             OSC
                                                               S. Venaas
                                                             K. Wierenga
                                                                   Cisco
                                                       February 14, 2012

          Transport Layer Security (TLS) encryption for RADIUS
                      draft-ietf-radext-radsec-12

Abstract

   This document specifies a transport profile for RADIUS using
   Transport Layer Security (TLS) over TCP as the transport protocol.
   This enables dynamic trust relationships between RADIUS servers.

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 August 17, 2012.

Copyright Notice

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

Winter, et al.           Expires August 17, 2012                [Page 1]
Internet-Draft               RADIUS over TLS               February 2012

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

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
     1.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
     1.3.  Document Status  . . . . . . . . . . . . . . . . . . . . .  4
   2.  Normative: Transport Layer Security for RADIUS/TCP . . . . . .  5
     2.1.  TCP port and packet types  . . . . . . . . . . . . . . . .  5
     2.2.  TLS negotiation  . . . . . . . . . . . . . . . . . . . . .  5
     2.3.  Connection Setup . . . . . . . . . . . . . . . . . . . . .  5
     2.4.  Connecting Client Identity . . . . . . . . . . . . . . . .  7
     2.5.  RADIUS Datagrams . . . . . . . . . . . . . . . . . . . . .  8
   3.  Informative: Design Decisions  . . . . . . . . . . . . . . . . 10
     3.1.  Implications of Dynamic Peer Discovery . . . . . . . . . . 10
     3.2.  X.509 Certificate Considerations . . . . . . . . . . . . . 10
     3.3.  Ciphersuites and Compression Negotiation Considerations  . 11
     3.4.  RADIUS Datagram Considerations . . . . . . . . . . . . . . 11
   4.  Compatibility with other RADIUS transports . . . . . . . . . . 12
   5.  Diameter Compatibility . . . . . . . . . . . . . . . . . . . . 13
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   8.  Notes to the RFC Editor  . . . . . . . . . . . . . . . . . . . 15
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 15