[radext] RFC 7360 on Datagram Transport Layer Security (DTLS) as a Transport Layer for RADIUS

rfc-editor@rfc-editor.org Fri, 05 September 2014 00:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 853631A030F; Thu, 4 Sep 2014 17:30:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level:
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 0C4qOxtgmCyJ; Thu, 4 Sep 2014 17:30:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 7C70B1A030B; Thu, 4 Sep 2014 17:30:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6EACE18047E; Thu, 4 Sep 2014 17:29:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140905002958.6EACE18047E@rfc-editor.org>
Date: Thu, 4 Sep 2014 17:29:58 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/hBCuKzp1okxTmo9sDvDLGQ-jjQs
Cc: drafts-update-ref@iana.org, radext@ietf.org, rfc-editor@rfc-editor.org
Subject: [radext] RFC 7360 on Datagram Transport Layer Security (DTLS) as a Transport Layer for RADIUS
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 00:30:49 -0000

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

        
        RFC 7360

        Title:      Datagram Transport Layer Security (DTLS) 
                    as a Transport Layer for RADIUS 
        Author:     A. DeKok
        Status:     Experimental
        Stream:     IETF
        Date:       September 2014
        Mailbox:    aland@freeradius.org
        Pages:      27
        Characters: 60007
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-radext-dtls-13.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7360.txt

The RADIUS protocol defined in RFC 2865 has limited support for
authentication and encryption of RADIUS packets.  The protocol
transports data in the clear, although some parts of the packets can
have obfuscated content.  Packets may be replayed verbatim by an
attacker, and client-server authentication is based on fixed shared
secrets.  This document specifies how the Datagram Transport Layer
Security (DTLS) protocol may be used as a fix for these problems.  It
also describes how implementations of this proposal can coexist with
current RADIUS systems.

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/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