RFC 5090 on RADIUS Extension for Digest Authentication

rfc-editor@rfc-editor.org Fri, 15 February 2008 02:21 UTC

To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5090 on RADIUS Extension for Digest Authentication
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, radiusext@ops.ietf.org
Message-Id: <20080215021032.D17DE113E4C@bosco.isi.edu>
Date: Thu, 14 Feb 2008 18:10:32 -0800
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk

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

        
        RFC 5090

        Title:      RADIUS Extension for Digest Authentication 
        Author:     B. Sterman, D. Sadolevsky,
                    D. Schwartz, D. Williams,
                    W. Beck
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    baruch@kayote.com, 
                    dscreat@dscreat.com, 
                    david@kayote.com,  dwilli@cisco.com, 
                    beckw@t-systems.com
        Pages:      33
        Characters: 68299
        Obsoletes:  RFC4590

        I-D Tag:    draft-ietf-radext-rfc4590bis-02.txt

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

This document defines an extension to the Remote Authentication
Dial-In User Service (RADIUS) protocol to enable support of Digest
Authentication, for use with HTTP-style protocols like the Session
Initiation Protocol (SIP) and HTTP.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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 Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

RFC 5090 on RADIUS Extension for Digest Authentic… rfc-editor