RFC 5997 on Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol

rfc-editor@rfc-editor.org Tue, 31 August 2010 06:06 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25DFF3A6A35 for <ietf-announce@core3.amsl.com>; Mon, 30 Aug 2010 23:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.34
X-Spam-Level:
X-Spam-Status: No, score=-102.34 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vDsdD8lDMcR4 for <ietf-announce@core3.amsl.com>; Mon, 30 Aug 2010 23:06:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C12633A6A3D for <ietf-announce@ietf.org>; Mon, 30 Aug 2010 23:06:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D8CB4E06EE; Mon, 30 Aug 2010 23:06:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5997 on Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20100831060633.D8CB4E06EE@rfc-editor.org>
Date: Mon, 30 Aug 2010 23:06:33 -0700 (PDT)
Cc: radiusext@ops.ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2010 06:06:05 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5997

        Title:      Use of Status-Server Packets in 
                    the Remote Authentication Dial In User 
                    Service (RADIUS) Protocol 
        Author:     A. DeKok
        Status:     Informational
        Stream:     IETF
        Date:       August 2010
        Mailbox:    aland@freeradius.org
        Pages:      24
        Characters: 55464
        Updates:    RFC2866

        I-D Tag:    draft-ietf-radext-status-server-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5997.txt

This document describes a deployed extension to the Remote
Authentication Dial In User Service (RADIUS) protocol, enabling
clients to query the status of a RADIUS server.  This extension
utilizes the Status-Server (12) Code, which was reserved for
experimental use in RFC 2865.  This document is not an Internet 
Standards Track specification; it is published for informational 
purposes.

This document is a product of the RADIUS EXTensions Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC