IETF Logo Mail Archive

Re: [sipcore] ABNF: request-digest: 32 characters, only 32 characters and nothing but 32 characters?

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> Thu, 15 February 2018 16:01 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 B03AD126BF6 for <sipcore@ietfa.amsl.com>; Thu, 15 Feb 2018 08:01:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 qd2-GCxXTPYb for <sipcore@ietfa.amsl.com>; Thu, 15 Feb 2018 08:01:52 -0800 (PST)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 1EC02127978 for <sipcore@ietf.org>; Thu, 15 Feb 2018 08:01:51 -0800 (PST)
Received: by mail-vk0-x232.google.com with SMTP id z9so98423vkd.5 for <sipcore@ietf.org>; Thu, 15 Feb 2018 08:01:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X+KyUa4KDuAJ2MRy8jqXsSyUPsWK5nUrYVOGKIjpZuQ=; b=lrZd/TeQgwu7t0SYb5jF3H0BPhtkHxwRu2/YpLlfE39thqyJDIsP3wh/N/MZpPqVsN QIor7Ar+Rabbu0lOUkMVIS7IK1n3McplDwT0PycDgX3KIasX+w3jddZ5BH2fMGQ6FHX/ ewuvGnaOmYTGgR8UvFJANS4ihTRIvsQcGzVechHwgF11W9xl58LMWrOG/g87Ovo/T36Y kBMfYKjvAdg0iDkCLNznkfgTnwpYSm2zD7S32KmS5jUWGVtXdeG8Gcp4xeTAcNcYVfu6 clLwUSmpTw3mPRrm6MrinSikm66CQXogTnIu9Pdc/Ft9x6irltk+0iTBXQLean37SdKo qI2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X+KyUa4KDuAJ2MRy8jqXsSyUPsWK5nUrYVOGKIjpZuQ=; b=TG+T+MjingMuqOgdg4goEq7neVg0lsfF52Kjn104ueP3TdOA5Be+Qzv2DmSeo/RAbn PMSOPF1aGBi9TIiOrqGA8cXmzzGHtVmJeW5uk20uiRLvZPoKP6V0bbPWCNAlz3TNgd7x AmbTYNygw+kybv78Bn2ZIqD+x66QUlYyh6401UCJlYHQrOnPGpEnlWAPU4QLYMjG9JaB t1UbY5PopghGZoaLqKY3305qh7u7L+t0tsc6aOY9XNH6WY1rwXRBWYhF4Zn+PzzBFhoX r8j/MKBqtrQhGQxJC6y/i6YV6Dxccht/SFNBHR0t8NEMCY9p79fba5g/oBEOBKICACrh OZJw==
X-Gm-Message-State: APf1xPDqiNMmTE8Kid1jpwBcc9bWflVOCG4KGq4CNuheqI81f8CRPAQt 6NkORJ/vktz2wOWQyyGBbWN6Sh0YvNnx5Q59eN4=
X-Google-Smtp-Source: AH8x224serGaOXW04/RaZftedZ0kXL33+L4+Hiz31Pkmm0K7DC6cSc1Ks0QCdS9oKLpLLs0wTmn5i6Z7vV2HSnVfDH4=
X-Received: by 10.31.154.194 with SMTP id c185mr2411700vke.60.1518710510064; Thu, 15 Feb 2018 08:01:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.45.141 with HTTP; Thu, 15 Feb 2018 08:01:49 -0800 (PST)
In-Reply-To: <D6AB3EE7.2B2C4%christer.holmberg@ericsson.com>
References: <D6A9C069.2B0CC%christer.holmberg@ericsson.com> <87d117gei6.fsf@hobgoblin.ariadne.com> <D6AAFAD2.2B1CF%christer.holmberg@ericsson.com> <D6AB3EE7.2B2C4%christer.holmberg@ericsson.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Date: Thu, 15 Feb 2018 11:01:49 -0500
Message-ID: <CAGL6epK5h24soYJ-6ei1FUu2pcDuBB7HRT+cjkb0wO02aXB4iQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "Dale R. Worley" <worley@ariadne.com>, "rifaat.sy@gmail.com" <rifaat.sy@gmail.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141da2878352b056542589e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/9q-_HlWaswUwjk6Z3t3co9VJNtA>
Subject: Re: [sipcore] ABNF: request-digest: 32 characters, only 32 characters and nothing but 32 characters?
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 15 Feb 2018 16:01:55 -0000

Dale,

The HTTP Authorization header is defined in RFC7235:
https://tools.ietf.org/html/rfc7235

As Christer mentioned, the SIP Digest draft has updated the SIP ABNF in
section 3:
https://tools.ietf.org/html/draft-yusef-sipcore-digest-scheme-06#section-3

Regards,
 Rifaat


On Thu, Feb 15, 2018 at 6:33 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> I realised that Rifaat’s draft actually updates the ABNF (by removing the
> 32 characters restriction), so we wouldn’t need anything in addition to
> that.
>
> I know the draft has been discussed in the past. I don’t remember what the
> outcome has been, but my suggestion would be to actually adopt the draft.
>
> Regards,
>
> Christer
>
>
> On 15/02/18 08:41, "sipcore on behalf of Christer Holmberg"
> <sipcore-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
> wrote:
>
> >Hi,
> >
> >>Christer Holmberg <christer.holmberg@ericsson.com> writes:
> >>>>I suspect this has been implicitly updated by the later versions of
> >>>>HTTP
> >>>>Digest.  It looks like RFC 7616 is the central piece of that, but I
> >>>>can't find the reference to the revised BNF.
> >>>
> >>> I can't find the revised BNF either, but I find the following text in
> >>>7616:
> >>> [...]
> >>>
> >>> So, to me it seems like we need to update the ABNF in 3261.
> >>
> >>First off, can Rifaat point us to the BNF?
> >>
> >>In regard to updating 3261, why don't we have it properly point to 7616
> >>and its successors, so we don't have to have to keep revising 3261 to
> >>track 7616?
> >
> >Well, assuming that is possible to begin with, it would also require an
> >update to 3261, wouldn¹t it? :)
> >
> >But, regarding the syntax, I don¹t understand why we have to limit the
> >number of characters (32, 64, or whatever). Just allow an unlimited number
> >of characters, and it will be future proof.
> >
> >Regards,
> >
> >Christer
> >
> >_______________________________________________
> >sipcore mailing list
> >sipcore@ietf.org
> >https://www.ietf.org/mailman/listinfo/sipcore
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

v2.23.0 | Report a Bug | By Email