Re: [kitten] [EXTERNAL] Re: IANA number assignment for checksum type

Robbie Harwood <rharwood@redhat.com> Fri, 18 June 2021 16:31 UTC

Return-Path: <rharwood@redhat.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF30B3A18BA for <kitten@ietfa.amsl.com>; Fri, 18 Jun 2021 09:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=redhat.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 tiEishTdswRX for <kitten@ietfa.amsl.com>; Fri, 18 Jun 2021 09:31:43 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (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 0FA123A18B7 for <kitten@ietf.org>; Fri, 18 Jun 2021 09:31:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1624033901; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=2c27+y/VtHj8WET5GInqPIdPECZp0s3Es8pyxp81xDA=; b=MndANfubi8hnH4BaBq0fd2CfUjCcqB4HOs1iPDqlqza9AGKT1ZQPBFPonj9ndm01DAtsQs kdlCl0EVd0E5aVUSMhf35fmVlFTD8SQ0rbVNPyhIC0R3vH5sA5EoPE+OBr8TQnR1L5cada Z6dFGySj+p6qpXSdfevcRkrDuQmHu2A=
Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-542-RMjy7oU7Nw-CzWwlKm_zzA-1; Fri, 18 Jun 2021 12:31:36 -0400
X-MC-Unique: RMjy7oU7Nw-CzWwlKm_zzA-1
Received: by mail-qt1-f198.google.com with SMTP id d7-20020ac811870000b02901e65f85117bso7071245qtj.18 for <kitten@ietf.org>; Fri, 18 Jun 2021 09:31:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=2c27+y/VtHj8WET5GInqPIdPECZp0s3Es8pyxp81xDA=; b=YMkv/Tz4DD/TVjpbKEd1bJtMeg/yj3w5pL1OEVc+Qd/G2GHKMnptaFeKMiwr/GkkRo 8ePJbcB8ek3APGlepUE+dR+FOLhNdKMWP+JDt2IavXtufpNUvC0gy/YZsQ9EXxp/Js02 81GzKpLkb+5e/1+5oygXi+727lO0CMlIuCG4YM/VCO23fGnYEO+KajijfQuSTLpmGgHm VA/Sr+//djPeQqnFvcOmlqjOQTPKWmbq+XeFnsEIKI0isNi1SY32G6QsoSPQb12A0fW5 c1r56aY0UvC1Y7g9y2MlrECAZMQXtiU1Jt4rOkx090M43TO/z1zBmxW9xq1VE3Wv2KtC E5tQ==
X-Gm-Message-State: AOAM533k5ehUwU4fHZout4SWJO0fcwczmQeS+Wt9SGAtCjwuZlErG3do aLc8climYJ1Om2tcAjNm2MfqwTz9xoeSpXbhgWCIf4gaMgfIdz+Xb4y3KYLDgR6qTttcYTJzh3t vWJOk63s=
X-Received: by 2002:a05:620a:809:: with SMTP id s9mr3575736qks.48.1624033896004; Fri, 18 Jun 2021 09:31:36 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJwC9TWPqJHedZ1vYY/hcobNc7PwHEyCI64CSm3GB6U1TDeq7AY/jEYgGo3aL8wOxwZP4ALhzg==
X-Received: by 2002:a05:620a:809:: with SMTP id s9mr3575715qks.48.1624033895810; Fri, 18 Jun 2021 09:31:35 -0700 (PDT)
Received: from localhost (c-71-232-17-31.hsd1.ma.comcast.net. [71.232.17.31]) by smtp.gmail.com with ESMTPSA id t30sm4236537qkm.11.2021.06.18.09.31.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Jun 2021 09:31:35 -0700 (PDT)
From: Robbie Harwood <rharwood@redhat.com>
To: Jishnu Renugopal <Jishnu.Renugopal@microsoft.com>, "kitten@ietf.org" <kitten@ietf.org>
In-Reply-To: <MWHPR2101MB08098FF14AE954451F03EB1295309@MWHPR2101MB0809.namprd21.prod.outlook.com>
References: <MWHPR2101MB0809EB5EFF1989B9E1F1772295379@MWHPR2101MB0809.namprd21.prod.outlook.com> <jlg4kdz9ivm.fsf@redhat.com> <MWHPR2101MB08098FF14AE954451F03EB1295309@MWHPR2101MB0809.namprd21.prod.outlook.com>
Date: Fri, 18 Jun 2021 12:31:32 -0400
Message-ID: <jlgr1gzjfrv.fsf@redhat.com>
MIME-Version: 1.0
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=rharwood@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/CZd7vMuAcoFwHYpFYfTvyYyg-JQ>
Subject: Re: [kitten] [EXTERNAL] Re: IANA number assignment for checksum type
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2021 16:31:48 -0000

Jishnu Renugopal <Jishnu.Renugopal@microsoft.com> writes:

> We are implementing RFC 8636 partially.
>
> Instead of rfc8636
> (ietf.org)<https://datatracker.ietf.org/doc/html/rfc8636#section-3>
> which updates paChecksum from RFC 4556 where it is always a SHA1
> checksum; we are extending pkauthenticator to include other checksums
> also. In this case, SHA2.

Could you please not divert from RFC 8636?  The rest of the ecosystem
already implemented this RFC - it would be rather frustrating if
Microsoft decided to implement something different from everyone else.
This is doubly true since this is a document we recently standardized,
and there were no objections to it at the time.

On a technical level, as it says in the registry link you used, new
assignments require either a standards-track RFC or expert review for
any other RFC.

--Robbie