datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

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

Document type: Active Internet-Draft (radext WG)
Document stream: IETF
Last updated: 2014-03-04
Intended RFC status: Experimental
Other versions: plain text, xml, pdf, html

IETF State: WG Consensus: Waiting for Write-Up
Document shepherd: Jouni Korhonen

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

RADIUS Extensions Working Group                                S. Winter
Internet-Draft                                                   RESTENA
Intended status: Experimental                                M. McCauley
Expires: September 4, 2014                                           OSC
                                                          March 03, 2014

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

Abstract

   This document specifies a means to find authoritative RADIUS servers
   for a given realm.  It is used in conjunction with either 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 September 4, 2014.

Copyright Notice

   Copyright (c) 2014 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 September 4, 2014               [Page 1]
Internet-Draft            RADIUS Peer Discovery               March 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Document Status . . . . . . . . . . . . . . . . . . . . .   4
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  DNS RR definition . . . . . . . . . . . . . . . . . . . .   4
       2.1.1.  S-NAPTR . . . . . . . . . . . . . . . . . . . . . . .   5
       2.1.2.  SRV . . . . . . . . . . . . . . . . . . . . . . . . .   9
       2.1.3.  Optional name mangling  . . . . . . . . . . . . . . .   9
     2.2.  Definition of the X.509 certificate property
           SubjectAltName:otherName:NAIRealm . . . . . . . . . . . .  11
   3.  DNS-based NAPTR/SRV Peer Discovery  . . . . . . . . . . . . .  12
     3.1.  Applicability . . . . . . . . . . . . . . . . . . . . . .  12
     3.2.  Configuration Variables . . . . . . . . . . . . . . . . .  13
     3.3.  Terms . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     3.4.  Realm to RADIUS server resolution algorithm . . . . . . .  14
       3.4.1.  Input . . . . . . . . . . . . . . . . . . . . . . . .  14
       3.4.2.  Output  . . . . . . . . . . . . . . . . . . . . . . .  15
       3.4.3.  Algorithm . . . . . . . . . . . . . . . . . . . . . .  15
       3.4.4.  Validity of results . . . . . . . . . . . . . . . . .  17
       3.4.5.  Delay considerations  . . . . . . . . . . . . . . . .  18
       3.4.6.  Example . . . . . . . . . . . . . . . . . . . . . . .  18
   4.  Operations and Manageability Considerations . . . . . . . . .  20
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  22
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  24
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  25
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  26
   Appendix A.  Appendix A: ASN.1 Syntax of NAIRealm . . . . . . . .  27

1.  Introduction

   RADIUS in all its current transport variants (RADIUS/UDP, RADIUS/TCP,
   RADIUS/TLS, RADIUS/DTLS) requires manual configuration of all peers
   (clients, servers).

   Where more than one administrative entity collaborates for RADIUS
   authentication of their respective customers (a "roaming
   consortium"), the Network Access Identifier (NAI)
   [I-D.ietf-radext-nai] is the suggested way of differentiating users

[include full document text]