IETF Logo Mail Archive

Re: [sipcore] Resend: WGLC: draft-ietf-sipcore-digest-scheme

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Sat, 25 May 2019 10:36 UTC

Return-Path: <rifaat.ietf@gmail.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 1D6AD120098 for <sipcore@ietfa.amsl.com>; Sat, 25 May 2019 03:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 JNdzuBNii8Pe for <sipcore@ietfa.amsl.com>; Sat, 25 May 2019 03:36:03 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 AE4A8120075 for <sipcore@ietf.org>; Sat, 25 May 2019 03:36:03 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id g84so9736403ioa.1 for <sipcore@ietf.org>; Sat, 25 May 2019 03:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T99Y3W5oZKESYGWF9pBhe1lugyxPvCYkarAeTfg4K8w=; b=JPcdGcnPFHjJs+aPgv97oCFlNwL7ivUDTwNq3I27SWccdPZrc75C5NxcKdJ6EiZucv /dYvjlck2h/ku6O1sE6BFFTmV7WQSlQXASvpFPqPWdsAagZUkDP5fVp+BABNdNqZ9tRL h8hc0pU8UUKth1aQCkTRI64fTqye/7LK0RJ2VCwvqMcjqNyv/oV8dcPfXY4Jg1UYcMHi aXoSf9yvWOMJ0WwdY8iKHZbcC+FtY8Pnf+GigEldc4ojSn9FPbbp3m8HnWdmZOJEjAdg tvMN1fE+PvJuLeG7NVB1hhOSKn8DHcfjwWtZzdQJXwcOKMb7ns3IF52d2q/lnZv1cvWK NL3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=T99Y3W5oZKESYGWF9pBhe1lugyxPvCYkarAeTfg4K8w=; b=XKLgjKvfdwt1JNk/Qo4ZsZiyiMXP8EKbRBkHI7qkPo2kp55vJNvpYBLmmr0L/5E3XZ 87N81jQ7Um06jPua0932zwDNl4ax6UdTVXN0G6Tw+ZqZCaVGXmFX7vOXCTPv3sq/mvT2 65RDN+g48rC9hxfwSgDypFjMqU+ZhsTWd9uPqqbCDWMwGUhUYmVjYPD7Kxxz0MpNXwXW GQI3q5+j98gNWOfs6DKImit4+6yMaVm1xAvkR9aHc2A1F7lYkyOfij75WJx2O8kUvIAS 2ABQwX7fcp4mYoyu85u/cGbG/b4f7UIpjYfJ6kipXAY+a3rKd/WBMXBuvJlDRKtN7GHY x8EQ==
X-Gm-Message-State: APjAAAWQFnEBggmebW4Rs20tlrwbrlVF3CiUl621W+YnnQC+RuG6SREy rSDaREp4MT81zm0AZCyIxzWLnHEzNDLlhRnj6HZqLrwB
X-Google-Smtp-Source: APXvYqzwTPuVQouqKk4SwbDtNLJfHNJsO6+aiPOekCJGBDseZSOhnUyoF19sCDgp1sGABfO3aA7g52CrTlIrZEfCVuY=
X-Received: by 2002:a5d:8e0c:: with SMTP id e12mr16453384iod.31.1558780562938; Sat, 25 May 2019 03:36:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAGL6epLxSTSXWxfNjsHjAh22c0OgvyP4Ss5rWpjjQi5D84ou4A@mail.gmail.com> <87lfz0eel1.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87lfz0eel1.fsf@hobgoblin.ariadne.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Sat, 25 May 2019 06:35:51 -0400
Message-ID: <CAGL6ep+Ha5ymB5Grpz-kz4OG3NgCuPCMKt-+EE0QRvHNB3Pkig@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: SIPCORE <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bca2030589b3e1fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/KpFnmlW7KYYMclrjKKWL3z50Wbo>
Subject: Re: [sipcore] Resend: WGLC: draft-ietf-sipcore-digest-scheme
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: Sat, 25 May 2019 10:36:05 -0000

Thanks Dale,

I will replace the 3 paragraph of section 2.1 with your proposed text.

Regards,
 Rifaat


On Mon, May 20, 2019 at 10:17 PM Dale R. Worley <worley@ariadne.com> wrote:

> Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> writes:
> > I liked your proposed changes; I will incorporate them into the next
> > version of the document.
>
> Though I did make a mistake -- RFC 7616 only applies to HTTP, so the
> statement in draft-ietf-sipcore-digest-scheme-02 section 2.3 para 2 is
> not redundant, even though it appears to be repeating RFC 7616.
> Therefore...
>
> >> This suggests the wording could be improved along thse lines (changes
> >> marked with "|"):
> >>
> >>    2.1.  Hash Algorithms
> >>
> >>    The Digest scheme has an 'algorithm' parameter that specifies the
> >>    algorithm to be used to compute the digest of the response.  The IANA
> >>  | registry named "Hash Algorithms for HTTP Digest Authentication"
> >>  | specifies the algorithms
> >>  | that correspond to 'algorithm' values.
> >>
> >>    [RFC3261] specifies only one algorithm, MD5, which is used by
> >>    default.  This document extends [RFC3261] to allow use of any
> >>    registered algorithm.
> >>
> >>  | [RFC7616] specifies the usage preference when a response
> >>  | contains multiple challenges specifying different algorithms.  That
> >>  | specification is not changed by this document.
>
> The above sentence is incorrect.  I intended it to replace the current
> para 3 of the section, and it would be good to replace para 3 with
> something correct that clarifies the same question.  Perhaps something
> like
>
>    A UAS prioritizes which algorithm to use based on the ordering of the
>    challenge headers in the response it is processing.  That process is
>    specified in section 2.3 and parallels the process used in HTTP
>    specified by [RFC7616].
>
> >>    Note that [RFC7616] defines a -sess variant for each algorithm; the
> >>    -sess variants are not used with SIP.
>
> Dale
>

v2.23.0 | Report a Bug | By Email