Re: [netmod] MD5 in ianach ex-RFC7317

Kent Watsen <kent@watsen.net> Wed, 10 February 2021 17:25 UTC

Return-Path: <010001778cf9f1a6-cf78c278-ec2b-4410-9939-5c51e3cc9844-000000@amazonses.watsen.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB80A3A1085 for <netmod@ietfa.amsl.com>; Wed, 10 Feb 2021 09:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 l2Z3SOPPxXWK for <netmod@ietfa.amsl.com>; Wed, 10 Feb 2021 09:25:28 -0800 (PST)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03F503A1079 for <netmod@ietf.org>; Wed, 10 Feb 2021 09:25:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1612977926; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=CZGyCLrLK0dvDkDyG33sgKpsFtP9UXxq1Ry6uplhL9I=; b=UxDxhKBMhUW2fy0SLgpnceCEJLcgzEfXVO0MYeVjNkSOKEjP3S4Z63u++j75XiUb SL0J1schFrarTgR5alofw6tZUkcGHep67SCISDXZE3YAIeogkPRb13Azk3wdTLKFLTJ 4NxnHZjbN/NX2sAT3s5rjvWJWn0MrOjx+9rE2rQM=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Kent Watsen <kent@watsen.net>
In-Reply-To: <AM7PR07MB6248CEA69F73E225D9EC99F9A08D9@AM7PR07MB6248.eurprd07.prod.outlook.com>
Date: Wed, 10 Feb 2021 17:25:26 +0000
Cc: "netmod@ietf.org" <netmod@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <010001778cf9f1a6-cf78c278-ec2b-4410-9939-5c51e3cc9844-000000@email.amazonses.com>
References: <AM7PR07MB624833298D6872811059D186A08E9@AM7PR07MB6248.eurprd07.prod.outlook.com> <0100017787c260d9-55bdd1ae-c12b-4cb6-87b4-94e95951fe36-000000@email.amazonses.com> <AM7PR07MB6248AFD0CC1FB88329BF8C46A08E9@AM7PR07MB6248.eurprd07.prod.outlook.com> <0100017787e7c265-3993cc0c-a9c5-4072-b4bc-abba6fb7f7db-000000@email.amazonses.com> <20210209191054.j4ggkl3lvt5c566o@anna.jacobs.jacobs-university.de> <AM7PR07MB624899B3F2A08E786D505C4FA08D9@AM7PR07MB6248.eurprd07.prod.outlook.com> <010001778cb9cf93-5e68e4c3-f85a-4d3c-931c-1913aec9de85-000000@email.amazonses.com> <AM7PR07MB6248CEA69F73E225D9EC99F9A08D9@AM7PR07MB6248.eurprd07.prod.outlook.com>
To: tom petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2021.02.10-54.240.8.33
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/6K02Xj2WfRyDTcb34VCR74CCUFY>
Subject: Re: [netmod] MD5 in ianach ex-RFC7317
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2021 17:25:30 -0000


> On Feb 10, 2021, at 11:46 AM, tom petch <ietfc@btconnect.com> wrote:
> 
> Not quite for me.  The current version is that on the IANA website, RFC7317 is history at least for IANACH so I think that the YANG reference for the update should be to the IANA website.
> 

Please provide OLD/NEW text.

FWIW, RFC8407 says:

   A "revision" statement MUST be present for each published version of
   the module.  The "revision" statement MUST have a "reference"
   substatement.  It MUST identify the published document that contains
   the module.

So what is the “document”?

    revision 2021-MM-DD {
      description
        “Deprecated the 'crypt-hash-md5’ feature per RFC 6151.";
      reference
        "RFC 6151:
             Updated Security Considerations for the MD5
             Message-Digest and the HMAC-MD5 Algorithms";
    }

But note that 6151 was published long before 7317 and, besides, it doesn’t “deprecate” MD5.

We can’t reference 8573 because it's NTP-specific.  Perhaps iana-crypt-hash is fine, and instead ntp-yang-data-model should be republished, augmenting in the desired “status” while referencing 8573.

K.