Browse Prior Art Database

IANA Considerations for RADIUS (Remote Authentication Dial In User Service) (RFC3575)

IP.com Disclosure Number: IPCOM000018643D
Original Publication Date: 2003-Jul-01
Included in the Prior Art Database: 2003-Jul-30
Document File: 9 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Aboba: AUTHOR

Abstract

This document describes the IANA considerations for the Remote Authentication Dial In User Service (RADIUS).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 18% of the total text.

Network Working Group                                           B. Aboba

Request for Comments: 3575                                     Microsoft

Updates: 2865                                                  July 2003

Category: Standard Track

                     IANA Considerations for RADIUS

              (Remote Authentication Dial In User Service)

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   This document describes the IANA considerations for the Remote

   Authentication Dial In User Service (RADIUS).

   This document updates RFC 2865.

1.  Introduction

   This document provides guidance to the Internet Assigned Numbers

   Authority (IANA) regarding registration of values related to the

   Remote Authentication Dial In User Service (RADIUS), defined in

   [RFC2865], in accordance with BCP 26, [RFC2434].  It also reserves

   Packet Type Codes that are or have been in use on the Internet.

1.1.  Specification of Requirements

   In this document, several words are used to signify the requirements

   of the specification.  These words are often capitalized.  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 [RFC2119].

Aboba                       Standards Track                     [Page 1]

RFC 3575             IANA Considerations for RADIUS            July 2003

1.2.  Terminology

   The following terms are used here with the meanings defined in BCP

   26:  "name space", "assigned value", "registration".

   The following policies are used here with the meanings defined in BCP

   26: "Private Use", "First Come First Served", "Expert Review",

   "Specification Required", "IESG Approval", "IETF Consensus",

   "Standards Action".

2.  IANA Considerations

   There are three name spaces in RADIUS that require registration:

   Packet Type Codes, Attribute Types, and Attribute Values (for certain

   Attributes).  This document creates no new IANA registries, since a

   RADIUS registry was created by [RFC2865].

   RADIUS is not intended as a general-purpose protocol, and allocations

   SHOULD NOT be made for purposes unrelated to Authentication,

   Authorization or Accounting.

2.1.  Recommended Registration Policies

   For registration requests where a ...