[Int-dir] INT directorate Review of draft-ietf-lamps-rfc3709bis-07

Donald Eastlake <d3e3e3@gmail.com> Wed, 23 November 2022 23:25 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66C98C14CF14; Wed, 23 Nov 2022 15:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s60hAsLSuK_4; Wed, 23 Nov 2022 15:25:39 -0800 (PST)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC83EC14CF12; Wed, 23 Nov 2022 15:25:38 -0800 (PST)
Received: by mail-ed1-x52f.google.com with SMTP id z63so389697ede.1; Wed, 23 Nov 2022 15:25:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ia19TT5GdaRmHN3vfr+IF7cZD1HxCqL4GYEOBnV6rEI=; b=EL5ZXtIK4doOqd8detkGtS5qfN0qMt1XGas3tgvST2XiJIzy+UUPgo8qGadJ9iBEbC /FVycjTufE2/nvKzTJnUCzpS8VK8irY/XcpPRp378x2dyVcv3HUv51xoPWELeJhuLjPl tYjPwexg1iOW8ePgMySsc3AEtDiEEWAMjlNQ9ZoRCSRTlooCPkQX6tf0CbXSpCMKtIHy CO4InqGVlcJgTO2QCOe8Nx2HoBRqN4Z82Iu8Cx2sDKWx3DEZ0Uob9TJRKs3Hkz197dNh E7BFEJmgf197YlsZoZlIyTa7RNro1MxCD40C9eYXxyo7TI1e4WzKO1DAdPA2MQN1YLlS EyeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ia19TT5GdaRmHN3vfr+IF7cZD1HxCqL4GYEOBnV6rEI=; b=N5H5PsEylaCHufbYH7JR5mtcTS3aI/0SandboziP8ce2Pp9DVvAeYm2nt3vKLfqmxA wvChJtY0RIXFPF6kdjPKxQzBy+DSqHI+2E9CcXL9u5qP6ykV5PworebTEANx1hk8SJ+T kc4oa4KaO52NRu31/+yTzIgg2UJYy9WEhzygAmCLPrzrjVgtwIW9WUnKeNQSP6vzSw93 YWeP0rFic90xMDYvWVgRFN1YI5ZKR+xX2Ht4xkdDRgCCM1EGJObW2EKzS5qmvmTjFFLQ BizeCJgEO7CpI4OCbuiWBKm2VjH9HQGoflTcf3rHnQ6PtDyVpvOSW3l4795zyGFs4r87 nK6g==
X-Gm-Message-State: ANoB5pmQ+5LY5EI/t0geHhsp7isOoPhZOBesoohzJOvR8zKCp1dyk8e8 BNb1Kx6pOGHakq14bX3xEO9g55QImltccWnQmOmRIxAiyN4=
X-Google-Smtp-Source: AA0mqf554vgGS124zR2GXVxccSRa/7urvKKpkAc0uMU9wWmS6q4ugjZF4dxy756OBDIiMGgj00HE7ekRJ/41cvt1NM4=
X-Received: by 2002:aa7:c6cc:0:b0:46a:44b2:b5ed with SMTP id b12-20020aa7c6cc000000b0046a44b2b5edmr3040421eds.212.1669245936508; Wed, 23 Nov 2022 15:25:36 -0800 (PST)
MIME-Version: 1.0
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 23 Nov 2022 18:25:24 -0500
Message-ID: <CAF4+nEGW1EYk7M6SacVG9KbnGj8j6QmpeOQJCdJytSHrEuy_3g@mail.gmail.com>
To: int-dir@ietf.org, int-ads@ietf.org
Cc: Last Call <last-call@ietf.org>, draft-ietf-lamps-rfc3709bis.all@ietf.org
Content-Type: multipart/alternative; boundary="00000000000016a10505ee2b9b10"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/5Kq9ApQkM_J1XMraTxbmnxH30O8>
Subject: [Int-dir] INT directorate Review of draft-ietf-lamps-rfc3709bis-07
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Nov 2022 23:25:43 -0000

I am an assigned INT directorate reviewer for
<draft-ietf-lamps-rfc3709bis-07.txt>. These comments were written primarily
for the benefit of the Internet Area Directors. Document editors and
shepherd(s) should treat these comments just like they would treat comments
from any other IETF contributors and resolve them along with any other Last
Call comments that have been received. For more details on the INT
Directorate, see https://datatracker.ietf.org/group/intdir/about/ <
https://datatracker.ietf.org/group/intdir/about/>.

Based on my review, if I was on the IESG I would ballot this document as NO
OBJECTION.

This document is generally in quite good shape. It specifies a certificate
extension for including logotypes in public key certificates and attribute
certificates. As such, usual INT Area considerations play very little part
in the draft.

The following are minor issues (typos, misspelling, minor text
improvements) with the document:

Section 9, Page 21: In the paragraph on has algorithm collisions, consider
"vulnerable to collision attacks." -> "vulnerable to collision attacks such
as MD5 [RFC6151]."

Nits:

Section 3, Page 7: "between of" -> "of between"

Section 3. Page 8: "more than one of the audio object" -> "more than one of
the audio objects"

Section 7, Page 18:
 - I think ".ext" as the column header for extension is a bit obscure. How
about ".ext" -> "Extension"?
 - It seems odd to require support for .svgz but not .svg since you
obviously have to support .svg internally if you support .svgz.

Section 10, Page 23: "hide the name resolution" -> "hides the name
resolution"

Stylistic:

Section 1.1, Page 4:
"the user in conscious contact with the result of a certificate-based
identification process," ->
"to the user's attention a certificate-based identification,"

Section 4.1, Pages 11&12: There are three flavors of logotype defined and
for each of them the same statement occurs that it "MAY be present in an
end entity certificate, a CA certificate, or an attribute certificate." I
would factor that out of the three sub paragraphs and change the lead in
line from "Logotype types defined in this specification are:" to something
like "Three Logotypes are specified in this section below. Each of them
"MAY be present in an end entity certificate, a CA certificate, or an
attribute certificate."

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com