draft-ietf-sipcore-digest-scheme-04.txt   draft-ietf-sipcore-digest-scheme-05.txt 
SIP Core R. Shekh-Yusef SIP Core R. Shekh-Yusef
Internet-Draft Avaya Internet-Draft Avaya
Updates: 3261 (if approved) May 28, 2019 Updates: 3261 (if approved) May 30, 2019
Intended status: Standards Track Intended status: Standards Track
Expires: November 29, 2019 Expires: December 1, 2019
The Session Initiation Protocol (SIP) Digest Authentication Scheme The Session Initiation Protocol (SIP) Digest Authentication Scheme
draft-ietf-sipcore-digest-scheme-04 draft-ietf-sipcore-digest-scheme-05
Abstract Abstract
This document updates the Digest Access Authentication scheme used by This document updates the Digest Access Authentication scheme used by
the Session Initiation Protocol (SIP) to add support for more secure the Session Initiation Protocol (SIP) to add support for more secure
digest algorithms, e.g. SHA-256 and SHA-512-256, to replace the digest algorithms, e.g. SHA-256 and SHA-512-256, to replace the
broken MD5 algorithm. broken MD5 algorithm.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 29, 2019. This Internet-Draft will expire on December 1, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 40 skipping to change at page 3, line 40
WWW-Authenticate and Proxy-Authenticate header fields, including in WWW-Authenticate and Proxy-Authenticate header fields, including in
which order to insert and process them. It provides guidance which order to insert and process them. It provides guidance
regarding forking. Finally, it updates the SIP protocol BNF as regarding forking. Finally, it updates the SIP protocol BNF as
required by the updates. required by the updates.
2.1. Hash Algorithms 2.1. Hash Algorithms
The Digest scheme has an 'algorithm' parameter that specifies the The Digest scheme has an 'algorithm' parameter that specifies the
algorithm to be used to compute the digest of the response. The IANA algorithm to be used to compute the digest of the response. The IANA
registry named "HTTP Digest Hash Algorithms" specifies the algorithms registry named "HTTP Digest Hash Algorithms" specifies the algorithms
that correspond to 'algorithm' values, and specifies a priority for that correspond to 'algorithm' values.
each algorithm.
[RFC3261] specifies only one algorithm, MD5, which is used by [RFC3261] specifies only one algorithm, MD5, which is used by
default. This document extends [RFC3261] to allow use of any default. This document extends [RFC3261] to allow use of any
registered algorithm. registered algorithm.
A UAS prioritizes which algorithm to use based on the ordering of the A UAS prioritizes which algorithm to use based on the ordering of the
challenge header fields in the response it is processing. That challenge header fields in the response it is processing. That
process is specified in section 2.3 and parallels the process used in process is specified in section 2.3 and parallels the process used in
HTTP specified by [RFC7616]. HTTP specified by [RFC7616].
 End of changes. 5 change blocks. 
6 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/