IETF Logo Mail Archive

Re: [sipcore] Call for WG adoption: draft-yusef-sipcore-digest-scheme

worley@ariadne.com (Dale R. Worley) Thu, 04 April 2019 02:30 UTC

Return-Path: <worley@alum.mit.edu>
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 50B501201B6 for <sipcore@ietfa.amsl.com>; Wed, 3 Apr 2019 19:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level:
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 ru51e6UFVl-M for <sipcore@ietfa.amsl.com>; Wed, 3 Apr 2019 19:30:10 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BF3E1200F8 for <sipcore@ietf.org>; Wed, 3 Apr 2019 19:30:10 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id BrpChZey1XWW4Bs8nhMjCF; Thu, 04 Apr 2019 02:30:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1554345009; bh=jlI1cKLZ7ejmdMY8+B4JAf0Or9+cErCcn72gF4mNWxs=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=MKIKupfaCSaqw2ankvgV1TnQ+6wMpirEFFxsXkynP/aCfK1qTwjOQqooq/1POdESw pY83dxeqI7rTSqFirR+NasxOUCdRuY0UC4tJqYDpypUEvy4AQcAevnaJasr+jnmG0x N9FhbUNVgW6O9op04NeT+QbwEL8QHZY8OaapXbndmt8P2iLjwqil0vEyamYALA8mxR eLoWOyKjDFTx+3UcySXGciz6uqVy2v51LDxwzKlTBKR6Hb3iSjbbCGZjq8WP4SpUO/ q/KHif7mFhqhJxYAgsNS7ef7lad/6fDg78Jo6kX7MBvNnuY2O7DuxaX8gTLdKxm+Jp scgdaoMBEF7/w==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id Bs8lhozSyQ0wIBs8mhGFLV; Thu, 04 Apr 2019 02:30:09 +0000
X-Xfinity-VMeta: sc=0;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id x342U7tq017683; Wed, 3 Apr 2019 22:30:07 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x342U6rT017671; Wed, 3 Apr 2019 22:30:06 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: mahoney@nostrum.com, sipcore@ietf.org
In-Reply-To: <38f783ca-00c1-9a34-a3f6-fc63c018e272@nostrum.com>
Sender: worley@ariadne.com
Date: Wed, 03 Apr 2019 22:30:06 -0400
Message-ID: <87pnq2h58x.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/wPszEwYLbJvcWliacI0O9M3C2dU>
Subject: Re: [sipcore] Call for WG adoption: draft-yusef-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: Thu, 04 Apr 2019 02:30:12 -0000

> On 01/04/2019, 23.46, A. Jean Mahoney wrote:
>     This is a call for adoption of draft-yusef-sipcore-digest-scheme in the 
>     SIPCORE working group.
>     
>     https://datatracker.ietf.org/doc/draft-yusef-sipcore-digest-scheme/

I favor adopting draft-yusef-sipcore-digest-scheme.

(Editorial:  The Abstract needs revision.  As far as I can tell, the
general idea is to have MD5 be replaced by SHA-256 in general usage.
But the specifics are that the document adds both SHA-256 and
SHA-512-256 and does not remove MD5.)

Dale

v2.23.0 | Report a Bug | By Email