[sipcore] Doc Shepherd review of draft-ietf-sipcore-digest-scheme - Section 2.6

"A. Jean Mahoney" <mahoney@nostrum.com> Mon, 01 July 2019 19:07 UTC

Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E88B120A1E for <sipcore@ietfa.amsl.com>; Mon, 1 Jul 2019 12:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 1Lw-Dp4hudSF for <sipcore@ietfa.amsl.com>; Mon, 1 Jul 2019 12:07:22 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E795120A0A for <sipcore@ietf.org>; Mon, 1 Jul 2019 12:07:22 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x61J7FgP083805 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 1 Jul 2019 14:07:16 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1562008037; bh=CbhsoGFDBvW11f09ukUs1f2r6sVq+7M3s47Acm818Vo=; h=To:From:Subject:Date; b=tXrxtnCW6tzJyx23jU9ZaMqejoAZEJO0KhRczzF2AHvEhCjqCv4jvKSjvWE6JVCri 2ldeuvsaFpa9sOmcC6wzDkaeD/39GsN7JfzCZGV7T2t2aMhpICuzIuTzAt/9PehIj6 VzQbkwcThPUzy/CLgkkSsU66gOb12jcENXWxfBeY=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be mutabilis-2.local
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, SIPCORE <sipcore@ietf.org>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <dd1ba283-35a8-a288-a857-26cc0dfb43ad@nostrum.com>
Date: Mon, 01 Jul 2019 14:07:15 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/y7Og8NntGjawp2IasFTvIOBIvUQ>
Subject: [sipcore] Doc Shepherd review of draft-ietf-sipcore-digest-scheme - Section 2.6
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2019 19:07:24 -0000

Hi Rifaat,

As I was going through the draft on my Doc Shepherd pass, I found some 
issues in the text that was inherited from RFC3261 (section 2.6).

Mainly the text talks about servers and clients and doesn't cover 
proxies well. The section talks about the Authorization header field but 
doesn't mention the Proxy-Authorization header field. Bullet 8 does use 
the phrase "any resulting authorization header field", which may cover 
Proxy-Authorization, but it's not explicit. I think using the terms UAC 
and UAS in this section would help, and the Proxy-Authorization header 
field should be mentioned explicitly.

I'll send the rest of my comments on the draft (mostly nits) in another 
message.

Thanks!

Jean