[Sidrops] Re: Deb Cooley's No Objection on draft-ietf-sidr ops-rpki-ccr-08: (with COMMENT)

S Moonesamy <sm+ietf@elandsys.com> Tue, 23 June 2026 10:33 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: sidrops@mail2.ietf.org
Delivered-To: sidrops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A0AFB105B379D for <sidrops@mail2.ietf.org>; Tue, 23 Jun 2026 03:33:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782210829; bh=sHE0TUi/SPmQVGo5qR4d5kwLUg2DHeScGae/JvuoG04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FRtk95vOZZ+J00xAc/w3iXKrY60hvh8VAntxXFs2XOq5HcNMJkmuX7dZ5EuCtP0kG PFlKFD8Ebw4WONMIsy9/RboOQCvIMdFdPHMB20iCrM0N2CrM40u3WtO4DcJytjHVqN RaCETOSSm3qSLX08b8/9k5pgM/2JnfztJm0uqeTs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Du8dBG38Zm2 for <sidrops@mail2.ietf.org>; Tue, 23 Jun 2026 03:33:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 7A46C105B379A for <sidrops@ietf.org>; Tue, 23 Jun 2026 03:33:48 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.225.120.111]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 65NAWbIf025158 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jun 2026 03:33:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1782210814; x=1782297214; i=@elandsys.com; bh=sHE0TUi/SPmQVGo5qR4d5kwLUg2DHeScGae/JvuoG04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=plAjiQjkpi7DoeUhOBRayOWXaINlGLYPPTlkVbGBC0f4x5HYVvEKUV9wk3isdgTa2 TAqa6YGh6IT5cxnrrAReMubVB03meJHwtBNDVuPfIpqK5VNxT2aASVQMPqm+btnKF0 +fxYSdpu42uJe8UK1qPTW62Q2WAaz7vgfNfPEMs0=
Message-Id: <6.2.5.6.2.20260623030921.0a1d7838@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 23 Jun 2026 03:19:46 -0700
To: Job Snijders <job@bsd.nl>, sidrops@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <ajnDNoSHLH15UJnZ@feather.sobornost.net>
References: <178215466078.1222153.17712275187408238068@dt-datatracker-f9b87776f-xzl65> <ajmX6MRcv1ns9zzy@theobuehler.org> <6.2.5.6.2.20260622133422.0a6c5d30@elandnews.com> <ajmhOzOdlEVTbS8E@feather.sobornost.net> <6.2.5.6.2.20260622151005.12c56f90@elandnews.com> <ajnDNoSHLH15UJnZ@feather.sobornost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: 5GZQA2MZVXBIM3WE6GSGEIJMQ7DUNC5R
X-Message-ID-Hash: 5GZQA2MZVXBIM3WE6GSGEIJMQ7DUNC5R
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Theo Buehler <tb@theobuehler.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Sidrops] Re: Deb Cooley's No Objection on draft-ietf-sidr ops-rpki-ccr-08: (with COMMENT)
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/89vDQEtVMzK6yKSV2rnBN799k2k>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Hi Job,
At 04:20 PM 22-06-2026, Job Snijders wrote:
>Perhaps so. I am not sure this is very relevant to the CCR specification
>at hand. It has always been up to software library maintainers to
>decide whether they intend to support the RPKI use case and its
>non-cryptographic use of SHA-1 in their software.
>
>It seems NIST did not deprecate SHA-1 for non-cryptographic use:
>
>         "For non-digital-signature applications, the use of SHA-1 
> is acceptable
>         for applications that do not require collision resistance."
> 
>https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar2.pdf
>
>If I'm not mistaken, NIST even indicated they'll kindly continue to make
>the SHA-1 specification available for as historic artefact.

My reading of the above is that there shouldn't be any significant 
problem.  I suggest filing this discussion under: the matter was discussed.

Regards,
S. Moonesamy