NAI-based Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS
draft-ietf-radext-dynamic-discovery-05

The information below is for an old version of the document
Document Type Active Internet-Draft (radext WG)
Authors Stefan Winter  , Mike McCauley 
Last updated 2012-12-13
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
RADIUS Extensions Working Group                                S. Winter
Internet-Draft                                                   RESTENA
Intended status: Experimental                                M. McCauley
Expires: June 16, 2013                                               OSC
                                                       December 13, 2012

    NAI-based Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS
                 draft-ietf-radext-dynamic-discovery-05

Abstract

   This document specifies a means to find authoritative RADIUS servers
   for a given realm.  It can be used in conjunction with RADIUS/TLS and
   RADIUS/DTLS.

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 June 16, 2013.

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

Winter & McCauley         Expires June 16, 2013                 [Page 1]
Internet-Draft            RADIUS Peer Discovery            December 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
     1.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  DNS-based NAPTR/SRV Peer Discovery . . . . . . . . . . . . . .  3
     2.1.  Applicability  . . . . . . . . . . . . . . . . . . . . . .  3
     2.2.  DNS RR definition  . . . . . . . . . . . . . . . . . . . .  3
     2.3.  Realm to RADIUS server resolution algorithm  . . . . . . .  6
       2.3.1.  Input  . . . . . . . . . . . . . . . . . . . . . . . .  6
       2.3.2.  Output . . . . . . . . . . . . . . . . . . . . . . . .  7
       2.3.3.  Algorithm  . . . . . . . . . . . . . . . . . . . . . .  7
       2.3.4.  Validity of results  . . . . . . . . . . . . . . . . .  8
       2.3.5.  Delay considerations . . . . . . . . . . . . . . . . .  9
       2.3.6.  Example  . . . . . . . . . . . . . . . . . . . . . . .  9
   3.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   5.  Normative References . . . . . . . . . . . . . . . . . . . . . 11

Winter & McCauley         Expires June 16, 2013                 [Page 2]
Internet-Draft            RADIUS Peer Discovery            December 2012

1.  Introduction

1.1.  Requirements Language

   In this document, several words are used to signify the requirements
   of the specification.  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]

1.2.  Terminology

   RADIUS/TLS Client: a RADIUS/TLS [RFC6614] instance which initiates a
   new connection.

   RADIUS/TLS Server: a RADIUS/TLS [RFC6614] instance which listens on a
   RADIUS/TLS port and accepts new connections

   RADIUS/TLS node: a RADIUS/TLS client or server

2.  DNS-based NAPTR/SRV Peer Discovery

2.1.  Applicability

   Dynamic server discovery as defined in this document is only
   applicable for AAA transactions where a RADIUS server receives a
   request with a realm for which no home RADIUS server is known.  I.e.
   where static server configuration does not contain a known home
   authentication server, or where the server configuration explicitly
   states that the realm destination is to be looked up dynamically.
   Furthermore, it is only applicable for new user sessions, i.e. for
   the initial Access-Request.  Subsequent messages concerning this
   session, for example Access-Challenges and Access-Accepts use the
   previously-established communication channel between client and
   server.
Show full document text