IETF Logo Mail Archive

[DNSOP] Re: [Ext] Re: Request: Review changes - draft-ietf-dnsop-rfc7958bis-03 → 04.

Paul Hoffman <paul.hoffman@icann.org> Tue, 13 August 2024 22:20 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0BF6C14F6BE for <dnsop@ietfa.amsl.com>; Tue, 13 Aug 2024 15:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 IQ4esSTmVJlk for <dnsop@ietfa.amsl.com>; Tue, 13 Aug 2024 15:20:53 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) by ietfa.amsl.com (Postfix) with ESMTP id 79AB4C14EB19 for <dnsop@ietf.org>; Tue, 13 Aug 2024 15:20:53 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa2.lax.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 47DMKqHd029941 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dnsop@ietf.org>; Tue, 13 Aug 2024 22:20:53 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 13 Aug 2024 15:20:51 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1544.011; Tue, 13 Aug 2024 15:20:51 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Andres Pavez <andres.pavez@iana.org>
Thread-Topic: [Ext] [DNSOP] Re: Request: Review changes - draft-ietf-dnsop-rfc7958bis-03 → 04.
Thread-Index: AQHa7cc4cBPJBUWlGkKmZcuCicEUfLImN+aA
Date: Tue, 13 Aug 2024 22:20:51 +0000
Message-ID: <24055741-F457-41AD-A1C7-8962EDC26544@icann.org>
References: <F349AAFF-991C-41FE-8D71-628AB753B68B@contoso.com>
In-Reply-To: <F349AAFF-991C-41FE-8D71-628AB753B68B@contoso.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="iso-2022-jp"
Content-ID: <045C2CADD731514F8E0029F0B50C39F1@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-08-13_12,2024-08-13_02,2024-05-17_01
Message-ID-Hash: UNTNTFZ5OYLJIBGODHHEAM7HRK3WXUXB
X-Message-ID-Hash: UNTNTFZ5OYLJIBGODHHEAM7HRK3WXUXB
X-MailFrom: paul.hoffman@icann.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "dnsop@ietf.org" <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: [Ext] Re: Request: Review changes - draft-ietf-dnsop-rfc7958bis-03 → 04.
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/MNs5FArpyqsMGpRWMIdbA_BQNwA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

On Aug 13, 2024, at 14:24, Andres Pavez <andres.pavez@iana.org> wrote:
> 
> I am writing to report an typo in the document.
> 
> In Section 3.3, the text currently reads
> "[...] Note, however, that cryptographic assurance for the contents of the trust anchor now comes from the web PKI or the IANA CA, as described in Section 3.2. [...]"
> 
> The correct text should be:
> "[...] Note, however, that cryptographic assurance for the contents of the trust anchor now comes from the web PKI or the ICANN CA, as described in Section 3.2. [...]"
> 
> Proposed Correction: Replace "IANA CA" with "ICANN CA."

Yipes, that's a good catch. Thanks for watching carefully!

We'll note this for the IESG so that someone does a "needs new draft" and this will be reflected there.

--Paul Hoffman

v2.26.15 | Report a Bug | By Email | System Status