Correlating requests and replies in the Remote Authentication Dial In User Service (RADIUS) Protocol via the Request Authenticator.
draft-dekok-radext-request-authenticator-03

Document Type Active Internet-Draft (individual)
Last updated 2017-12-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Network Working Group                                         Alan DeKok
INTERNET-DRAFT                                                FreeRADIUS
Category: Proposed Standard
Updates: 2885
<draft-dekok-radext-request-authenticator-03.txt>
Expires: May 04, 2018
4 December 2017

                Correlating requests and replies in the
      Remote Authentication Dial In User Service (RADIUS) Protocol
                     via the Request Authenticator.
            draft-dekok-radext-request-authenticator-03.txt

Abstract

   RADIUS uses a one-octet Identifier field to correlate requests and
   responses, which limits clients to 256 "in flight" packets per
   connection.  This document removes that limitation by allowing
   Request Authenticator to be used as an additional field for
   identifying packets.  The capability is negotiated on a per-
   connection basis, and requires no changes to the RADIUS packet
   format, attribute encoding, or data types.

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 November 18, 2017.

DeKok, Alan                  Standards Track                    [Page 1]
INTERNET-DRAFT         Identifying RADIUS packets.       4 December 2017

Copyright Notice

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

   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.

DeKok, Alan                  Standards Track                    [Page 2]
INTERNET-DRAFT         Identifying RADIUS packets.       4 December 2017

Table of Contents

   11.1. .....................................................    3
1.  Introduction .............................................    4
   1.1.  Compatability with Existing RADIUS ..................    5
   1.2.  Outline of the document .............................    6
   1.3.  Terminology .........................................    6
   1.4.  Requirements Language ...............................    7
2.  Review of Current Behavior ...............................    8
   2.1.  Client Behavior .....................................    8
   2.2.  Server Behavior .....................................    9
3.  Alternative Approaches ...................................   10
   3.1.  Multiple Source Ports ...............................   11
   3.2.  Diameter ............................................   11
   3.3.  Multiple RADIUS packets in UDP ......................   11
   3.4.  An Extended ID field ................................   12
   3.5.  This Specification ..................................   13
4.  Protocol Overview ........................................   13
   4.1.  Why this works ......................................   14
5.  Signaling via Status-Server ..............................   15
   5.1.  Static Configuration ................................   17
6.  Original-Request-Authenticator Attribute .................   17
7.  Transport Considerations .................................   19
Show full document text