--- 1/draft-ietf-sipcore-digest-scheme-09.txt	2019-09-19 04:13:56.951587373 -0700
+++ 2/draft-ietf-sipcore-digest-scheme-10.txt	2019-09-19 04:13:56.971587878 -0700
@@ -1,19 +1,19 @@
 
 SIP Core                                                  R. Shekh-Yusef
 Internet-Draft                                                     Avaya
-Updates: 3261 (if approved)                           September 16, 2019
+Updates: 3261 (if approved)                           September 18, 2019
 Intended status: Standards Track
-Expires: March 19, 2020
+Expires: March 21, 2020
 
    The Session Initiation Protocol (SIP) Digest Authentication Scheme
-                  draft-ietf-sipcore-digest-scheme-09
+                  draft-ietf-sipcore-digest-scheme-10
 
 Abstract
 
    This document updates RFC 3261 by updating 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 broken MD5 algorithm, which might be used
    for backward compatibility reasons only.
 
 Status of This Memo
@@ -24,21 +24,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on March 19, 2020.
+   This Internet-Draft will expire on March 21, 2020.
 
 Copyright Notice
 
    Copyright (c) 2019 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -70,21 +70,21 @@
      2.3.  UAS Behavior  . . . . . . . . . . . . . . . . . . . . . .   4
      2.4.  UAC Behavior  . . . . . . . . . . . . . . . . . . . . . .   5
      2.5.  Forking . . . . . . . . . . . . . . . . . . . . . . . . .   5
      2.6.  HTTP Digest Authentication Scheme Modifications . . . . .   5
      2.7.  Augmented BNF for SIP . . . . . . . . . . . . . . . . . .   7
    3.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
    4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
    5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
    6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
      6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
-     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
+     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9
 
 1.  Introduction
 
    The Session Initiation Protocol [RFC3261] uses the same mechanism
    that the Hypertext Transfer Protocol (HTTP) uses for authenticating
    users.  This mechanism is called Digest Access Authentication, and it
    is a simple challenge-response mechanism that allows a server to
    challenge a client request and allows a client to provide
    authentication information in response to that challenge.  The
@@ -103,22 +103,24 @@
    Authentication" registry, so that algorithms can be added in the
    future.
 
    This document updates the Digest Access Authentication scheme used by
    SIP to support the algorithms listed in the "Hash Algorithms for HTTP
    Digest Authentication" registry defined by [RFC7616].
 
 1.1.  Terminology
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
-   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
-   document are to be interpreted as described in [RFC8174].
+   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
+   "OPTIONAL" in this document are to be interpreted as described in BCP
+   14 [RFC2119] [RFC8174] when, and only when, they appear in all
+   capitals, as shown here.
 
 2.  SIP Digest Authentication Scheme Updates
 
    This section describes the modifications to the operation of the
    Digest mechanism as specified in [RFC3261] in order to support the
    algorithms defined in the "Hash Algorithms for HTTP Digest
    Authentication" registry described in [RFC7616].
 
    It replaces the reference to [RFC2617] with a reference to [RFC7616]
    in [RFC3261], and describes the modifications to the usage of the
@@ -336,20 +338,25 @@
    The author would like to thank the following individuals for their
    careful reviews, comments, and suggestions: Paul Kyzivat, Olle
    Johansson, Dale Worley, Michael Procter, Inaki Baz Castillo, Tolga
    Asveren, Christer Holmberg, Brian Rosen, Jean Mahoney, and Adam
    Roach.
 
 6.  References
 
 6.1.  Normative References
 
+   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
+              Requirement Levels", BCP 14, RFC 2119,
+              DOI 10.17487/RFC2119, March 1997,
+              <https://www.rfc-editor.org/info/rfc2119>.
+
    [RFC3261]  Rosenberg, J., Schulzrinne, H., Camarillo, H., Johnston,
               A., Peterson, J., Sparks, R., Handley, M., and E.
               Schooler, "SIP: Session Initiation Protocol", RFC 3261,
               June 2002.
 
    [RFC7234]  Fielding, R., Nottingham, M., and J. Reschke, "Hypertext
               Transfer Protocol (HTTP/1.1): Caching", RFC 7234, June
               2014.
 
    [RFC7616]  Shekh-Yusef, R., Ahrens, D., and S. Bremer, "HTTP Digest