RFC 8044 on Data Types in RADIUS

rfc-editor@rfc-editor.org Thu, 26 January 2017 01:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15F4B12942F; Wed, 25 Jan 2017 17:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnKGRT9gPiZN; Wed, 25 Jan 2017 17:29:16 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA1B7126D74; Wed, 25 Jan 2017 17:29:16 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BFE39B80F6C; Wed, 25 Jan 2017 17:29:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8044 on Data Types in RADIUS
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170126012916.BFE39B80F6C@rfc-editor.org>
Date: Wed, 25 Jan 2017 17:29:16 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/tiy5q1PkuanWj-OxFCdOj-mkhnw>
Cc: drafts-update-ref@iana.org, radext@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 26 Jan 2017 01:29:18 -0000

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

        
        RFC 8044

        Title:      Data Types in RADIUS 
        Author:     A. DeKok
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2017
        Mailbox:    aland@freeradius.org
        Pages:      35
        Characters: 63324
        Updates:    RFC 2865, RFC 3162, RFC 6158, RFC 6572, RFC 7268

        I-D Tag:    draft-ietf-radext-datatypes-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8044

        DOI:        10.17487/RFC8044

RADIUS specifications have used data types for two decades without
defining them as managed entities.  During this time, RADIUS
implementations have named the data types and have used them in
attribute definitions.  This document updates the specifications to
better follow established practice.  We do this by naming the data
types defined in RFC 6158, which have been used since at least the
publication of RFC 2865.  We provide an IANA registry for the data
types and update the "RADIUS Attribute Types" registry to include a
Data Type field for each attribute.  Finally, we recommend that
authors of RADIUS specifications use these types in preference to
existing practice.  This document updates RFCs 2865, 3162, 4072,
6158, 6572, and 7268.

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

This is now a Proposed Standard.

STANDARDS TRACK: 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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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