IETF Logo Mail Archive

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

"A. Jean Mahoney" <mahoney@nostrum.com> Mon, 01 April 2019 17:42 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 0761D120187 for <sipcore@ietfa.amsl.com>; Mon, 1 Apr 2019 10:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 E5GchjsEXX4x for <sipcore@ietfa.amsl.com>; Mon, 1 Apr 2019 10:42:00 -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 3B352120075 for <sipcore@ietf.org>; Mon, 1 Apr 2019 10:42:00 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x31HflvG007808 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 1 Apr 2019 12:41:48 -0500 (CDT) (envelope-from mahoney@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1554140510; bh=IOVTF8SSYuOS19qhphIN+EcG291UDlM/cGP33Zgi05c=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=pRxxF92Wzn7BAS+P52UqK6J6G2zuoaFMV/3TKWRXbR7OUEx091IndHpm+L/lM08WQ A1a3mGH3+9gZNu15uClz7S4R7jPAyPum3t0hTvf9qMGIyI+IsAv7/eT53/NeYbKnV+ CrQ9acwMBAFN93uet3vpCZxA7n9pPFwjtaWqOI0U=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be mutabilis-2.local
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "rifaat.sy@gmail.com" <rifaat.sy@gmail.com>, "Dale R. Worley" <worley@ariadne.com>, SIPCORE <sipcore@ietf.org>, Andy Hutton <andyhutton.ietf@gmail.com>
References: <D6AB3EE7.2B2C4%christer.holmberg@ericsson.com> <87vaexg01a.fsf@hobgoblin.ariadne.com> <CAB7PXwSQ7dhWTYsrevpttcrUfWftbJ4Hc_XJmbKMua4eeT_Z_Q@mail.gmail.com> <E4EAAECD-AE0C-4D7B-9DC8-67993F010808@ericsson.com> <CAGL6epK96StrqLxc4yfQ1Y3ENysH=+ME2SqrP0qbGB6njbgJoA@mail.gmail.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <b64ba0e6-164b-c790-980a-fb1b54ead437@nostrum.com>
Date: Mon, 01 Apr 2019 12:41:47 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.0
MIME-Version: 1.0
In-Reply-To: <CAGL6epK96StrqLxc4yfQ1Y3ENysH=+ME2SqrP0qbGB6njbgJoA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/kn2eTnvFGZ80w25Effsm5yvcJHc>
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.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 Apr 2019 17:42:02 -0000

Hi Rifaat,

On 3/30/19 8:28 PM, Rifaat Shekh-Yusef wrote:
> I am honestly really puzzled why this draft has not be adopted long time 
> ago.
> This could have been delivered few years ago already.
> 
> What is stopping this from happening?


Good question. Digging through the SIPCORE mailing list, this co-chair 
found a plan to call for WG adoption for 
draft-yusef-sipcore-digest-scheme after a few other drafts made it 
through WGLC. Given that those drafts are in the RFC editor's queue, I 
don't think anything stopped the call for adoption except that maybe it 
fell off the chairs' to-do list.

Please update the draft (it has expired), and I will send a separate 
email to the list about WG adoption.

Thanks!

Jean

PS - If you think the chairs may have forgotten something, feel free to 
send a note to the list or the sipcore-chairs email address. Thx!




> 
> Regards,
>   Rifaat
> 
> 
> 
> On Fri, Mar 29, 2019 at 4:47 AM Christer Holmberg 
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> 
> wrote:
> 
>     Hi,
> 
>     This thread is a year old, but I would like to bring it back to the
>     surface..
> 
>     The syntax needs to be fixed, so I would like the WG to adopt the draft.
> 
>     Regards,
> 
>     Christer
> 
> 
>     On 21/03/2018, 19.54, "Andy Hutton" <andyhutton.ietf@gmail.com
>     <mailto:andyhutton.ietf@gmail.com>> wrote:
> 
>          I would also like to see draft-yusef-sipcore-digest-scheme adopted.
> 
>          Andy
> 
>          On 16 February 2018 at 02:07, Dale R. Worley
>     <worley@ariadne.com <mailto:worley@ariadne.com>> wrote:
>          > Christer Holmberg <christer.holmberg@ericsson.com
>     <mailto:christer.holmberg@ericsson.com>> writes:
>          >> 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 was going to say, What is the name of the draft?, but it's
>          > draft-yusef-sipcore-digest-scheme, which is dated last
>     September, which
>          > is probably why I remember it.
>          >
>          > It not only updates the ABNF in RFC 3261, it also connects it
>     with RFC
>          > 7611.
>          >
>          > ---> So, I call for adoption of
>     draft-yusef-sipcore-digest-scheme as a
>          > WG draft.
>          >
>          > Dale
>          >
>          > _______________________________________________
>          > sipcore mailing list
>          > sipcore@ietf.org <mailto:sipcore@ietf.org>
>          > https://www.ietf.org/mailman/listinfo/sipcore
> 
> 
>     _______________________________________________
>     sipcore mailing list
>     sipcore@ietf.org <mailto: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