RFC 8760 on The Session Initiation Protocol (SIP) Digest Access Authentication Scheme

rfc-editor@rfc-editor.org Thu, 19 March 2020 21:59 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 774053A10A3; Thu, 19 Mar 2020 14:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 nCD5fXATVpLK; Thu, 19 Mar 2020 14:59:30 -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 7E82B3A10A4; Thu, 19 Mar 2020 14:59:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AA600F4071C; Thu, 19 Mar 2020 14:59:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8760 on The Session Initiation Protocol (SIP) Digest Access Authentication Scheme
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sipcore@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200319215919.AA600F4071C@rfc-editor.org>
Date: Thu, 19 Mar 2020 14:59:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ciafVCkR0aMt4rxrL2NuCRqfxVU>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 19 Mar 2020 21:59:37 -0000

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

        
        RFC 8760

        Title:      The Session Initiation Protocol (SIP) 
                    Digest Access Authentication Scheme 
        Author:     R. Shekh-Yusef
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    rifaat.ietf@gmail.com
        Pages:      9
        Updates:    RFC 3261

        I-D Tag:    draft-ietf-sipcore-digest-scheme-15.txt

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

        DOI:        10.17487/RFC8760

This document updates RFC 3261 by modifying the Digest Access
Authentication scheme used by the Session Initiation Protocol (SIP)
to add support for more secure digest algorithms, e.g., SHA-256 and
SHA-512/256, to replace the obsolete MD5 algorithm.

This document is a product of the Session Initiation Protocol Core 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