Remote Authentication Dial In User Service (RADIUS) Protocol Extensions
draft-ietf-radext-radius-extensions-07

The information below is for an old version of the document
Document Type Active Internet-Draft (radext WG)
Last updated 2013-01-04 (latest revision 2012-12-26)
Replaces draft-dekok-radext-radius-extensions
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Other - see Comment Log
Consensus Unknown
Document shepherd Jouni Korhonen
IESG IESG state In Last Call
Telechat date
Responsible AD Benoit Claise
IESG note Jouni Korhonen (jouni.nospam@gmail.com) is the document shepherd.
Send notices to radext-chairs@tools.ietf.org, draft-ietf-radext-radius-extensions@tools.ietf.org
Network Working Group                                         Alan DeKok
INTERNET-DRAFT                                            Network RADIUS
Category: Proposed Standard                                     Avi Lior
Updates: 2865, 2866, 3575, 5176, 6158                                BWS
<draft-ietf-radext-radius-extensions-07.txt>
Expires: June 26, 2013
26 December 2012

      Remote Authentication Dial In User Service (RADIUS) Protocol
                               Extensions
               draft-ietf-radext-radius-extensions-07.txt

Abstract

   The Remote Authentication Dial In User Service (RADIUS) protocol is
   nearing exhaustion of its current 8-bit Attribute Type space.  In
   addition, experience shows a growing need for complex grouping, along
   with attributes which can carry more than 253 octets of data.  This
   document defines changes to RADIUS which address all of the above
   problems.

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

Copyright Notice

DeKok, Alan                  Standards Track                    [Page 1]
INTERNET-DRAFT              RADIUS Extensions           26 December 2012

   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.

DeKok, Alan                  Standards Track                    [Page 2]
INTERNET-DRAFT              RADIUS Extensions           26 December 2012

Table of Contents

1.  Introduction .............................................    5
   1.1.  Caveats and Limitations .............................    6
      1.1.1.  Failure to Meet Certain Goals ..................    6
      1.1.2.  Implementation Recommendations .................    6
   1.2.  Terminology .........................................    7
   1.3.  Requirements Language ...............................    8
2.  Extensions to RADIUS .....................................    9
   2.1.  Extended Type .......................................   10
   2.2.  Long Extended Type ..................................   11
   2.3.  TLV Data Type .......................................   13
      2.3.1.  TLV Nesting ....................................   15
   2.4.  EVS Data Type .......................................   16
   2.5.  Integer64 Data Type .................................   17
   2.6.  Vendor-ID Field .....................................   18
   2.7.  Attribute Naming and Type Identifiers ...............   18
      2.7.1.  Attribute and TLV Naming .......................   18
      2.7.2.  Attribute Type Identifiers .....................   19
      2.7.3.  TLV Identifiers ................................   19
      2.7.4.  VSA Identifiers ................................   20
   2.8.  Invalid Attributes ..................................   20
3.  Attribute Definitions ....................................   21
   3.1.  Extended-Type-1 .....................................   22
   3.2.  Extended-Type-2 .....................................   23
   3.3.  Extended-Type-3 .....................................   23
   3.4.  Extended-Type-4 .....................................   24
   3.5.  Long-Extended-Type-1 ................................   25
   3.6.  Long-Extended-Type-2 ................................   26
4.  Vendor Specific Attributes ...............................   28
   4.1.  Extended-Vendor-Specific-1 ..........................   28
Show full document text