RADIUS Extensions for Server Load Balancing
draft-massameno-radius-lb-00

Document Type Active Internet-Draft (individual)
Last updated 2020-06-25
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized 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)
Internet Engineering Task Force                      D.J. Massameno, Ed.
Internet-Draft                                           Yale University
Intended status: Informational                              25 June 2020
Expires: 27 December 2020

              RADIUS Extensions for Server Load Balancing
                      draft-massameno-radius-lb-00

Abstract

   This document describes a method for a Network Access Server (NAS) to
   dynamically discover all available RADIUS servers.  It defines a new
   message type within the STATUS-SERVER message, which is requested by
   the NAS and provided by the RADIUS server.  The NAS is then able to
   load balance its RADIUS messages across multiple RADIUS servers based
   on priority and weight supplied by the initial server.

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 https://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 27 December 2020.

Copyright Notice

   Copyright (c) 2020 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 (https://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.

Massameno               Expires 27 December 2020                [Page 1]
Internet-Draft                  radius-lb                      June 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Overall Message Exchange Summary  . . . . . . . . . . . . . .   4
     2.1.  Attributes Needed for Status-Server-LB  . . . . . . . . .   5
     2.2.  Table of Attributes . . . . . . . . . . . . . . . . . . .   5
     2.3.  Required Status-Server-LB Attributes  . . . . . . . . . .   6
       2.3.1.  NAS-IP Address and/or NAS-Identifier  . . . . . . . .   6
       2.3.2.  Message-Authenticator . . . . . . . . . . . . . . . .   6
   3.  LB-Request Attribute  . . . . . . . . . . . . . . . . . . . .   6
   4.  LB-Response Attribute . . . . . . . . . . . . . . . . . . . .   7
     4.1.  LB-Response Attribute Format  . . . . . . . . . . . . . .   8
   5.  The SVR-Record TLV  . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  SVR-Record-IPv4 . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  SVR-Record-IPv6 . . . . . . . . . . . . . . . . . . . . .   9
     5.3.  Table of Sub-Attributes . . . . . . . . . . . . . . . . .  10
   6.  Sub-Attributes Needed for SVR-Record TLV  . . . . . . . . . .  11
     6.1.  LB-TTL  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.2.  LB-Priority . . . . . . . . . . . . . . . . . . . . . . .  12
     6.3.  LB-Weight . . . . . . . . . . . . . . . . . . . . . . . .  12
     6.4.  LB-IPv4 . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.5.  LB-IPv6 . . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Load Balancing Rules  . . . . . . . . . . . . . . . . . . . .  15
     7.1.  Session-Based Load Balancing  . . . . . . . . . . . . . .  15
     7.2.  Load Balancing Weight . . . . . . . . . . . . . . . . . .  15
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
     8.1.  Clear Text Transmission . . . . . . . . . . . . . . . . .  16
     8.2.  Reconnaissance  . . . . . . . . . . . . . . . . . . . . .  16
     8.3.  MD5 . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   9.  NAS identifying Initial RADIUS Servers  . . . . . . . . . . .  16
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Modern networks require Authentication, Authorization and Accounting
   (AAA) services for a wide range of deployment scenarios.  Many of
   these scenarios are mission critical and require fault tolerance and
Show full document text