[Acme] comments on acme-subdomains
Michael Richardson <mcr+ietf@sandelman.ca> Wed, 02 March 2022 15:07 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB613A077A for <acme@ietfa.amsl.com>; Wed, 2 Mar 2022 07:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 y76c6Md71vMT for <acme@ietfa.amsl.com>; Wed, 2 Mar 2022 07:07:50 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D16BD3A07EA for <acme@ietf.org>; Wed, 2 Mar 2022 07:07:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 0016838BC6 for <acme@ietf.org>; Wed, 2 Mar 2022 10:16:47 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gkHj7HHkBnmz for <acme@ietf.org>; Wed, 2 Mar 2022 10:16:45 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id E75AA38BB9 for <acme@ietf.org>; Wed, 2 Mar 2022 10:16:44 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1646234204; bh=BJWWi195wPm+ZW8TpHl73zvlhuqvdVqQXE0eZ1bf1fM=; h=From:To:Subject:Date:From; b=6dC+rD8bRHr1W3CK//2yldHggOwrtnWkMTRotgBgKl/dDBYfJPNJLwbJv+/9w5ij3 vg8TakEyRZ8TByixPBHIuEIl7bVxEVDKIhDKUZLQRZnXvcI3cHJTS0T3yyN2PB8AKj pZdillobul2TdX7e/46jH6MULz0uncdIszXAeUwOFwcnGdygqvOf53doghPDhQppIR a0fFsawOqzfMQ1D7YDHVvxAXBen1LMRfqEjbQf6+tEFI2gO403qgOs8uS3uMI9RjR5 B+vhIdacho1ujFwTWu64850gqeCprVVVhmUqSq4s4OjnE65IV3fUl1R8xHzayA3Gvk LAKgIubcLxr7w==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8E64F197 for <acme@ietf.org>; Wed, 2 Mar 2022 10:07:44 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: acme@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 02 Mar 2022 10:07:44 -0500
Message-ID: <19083.1646233664@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/VEYbV-cHcCMVuzY5F5ToZxyjWjw>
Subject: [Acme] comments on acme-subdomains
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2022 15:07:56 -0000
I have posted a -02, only with kdrfc updates, and in order to get XML uploaded so that I can link to paragraph links: We have issue https://github.com/upros/acme-subdomains/issues/4 which says: Section 5, page 14, step 3: Typo. The server replies w/ an identifier of "sub1.example.org" instead of “sub2.example.com” I think that this refers to: https://www.ietf.org/archive/id/draft-ietf-acme-subdomains-02.html#section-5-16 it took me awhile to find the spot where the typo exactly is. Deb, I think that the fix is at: https://github.com/upros/acme-subdomains/pull/5/commits/c67527e897e8588ef6582944c2ba242bcc1ff3e0 In the document, we use "example.com" as the CA, and "XXX.example.org" as the client. I wonder if it might be clearer if we instead used: certificationauthority.example and: XXX.enterprise.example instead? -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- [Acme] comments on acme-subdomains Michael Richardson