RFC 7930 on Larger Packets for RADIUS over TCP
rfc-editor@rfc-editor.org Wed, 17 August 2016 21:38 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 1FAF212D09A; Wed, 17 Aug 2016 14:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.869
X-Spam-Level:
X-Spam-Status: No, score=-103.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 qO4WvvLIUcvf; Wed, 17 Aug 2016 14:38:14 -0700 (PDT)
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 270F712D7BB; Wed, 17 Aug 2016 14:38:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 06790B80C07; Wed, 17 Aug 2016 14:38:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7930 on Larger Packets for RADIUS over TCP
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160817213805.06790B80C07@rfc-editor.org>
Date: Wed, 17 Aug 2016 14:38:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/YXoyfnwhYQwvDBvKtvULKZjmyGo>
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: Wed, 17 Aug 2016 21:38:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7930
Title: Larger Packets for RADIUS over TCP
Author: S. Hartman
Status: Experimental
Stream: IETF
Date: August 2016
Mailbox: hartmans-ietf@mit.edu
Pages: 10
Characters: 22676
Updates: RFC 6613
I-D Tag: draft-ietf-radext-bigger-packets-07.txt
URL: https://www.rfc-editor.org/info/rfc7930
DOI: http://dx.doi.org/10.17487/RFC7930
The RADIUS-over-TLS experiment described in RFC 6614 has opened
RADIUS to new use cases where the 4096-octet maximum size limit of a
RADIUS packet proves problematic. This specification extends the
RADIUS-over-TCP experiment (RFC 6613) to permit larger RADIUS
packets. This specification compliments other ongoing work to permit
fragmentation of RADIUS authorization information. This document
registers a new RADIUS code, an action that required IESG approval.
This document is a product of the RADIUS EXTensions Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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