IETF Logo Mail Archive

Re: [OPSAWG] Lars Eggert's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

Lars Eggert <lars@eggert.org> Wed, 01 March 2023 18:32 UTC

Return-Path: <lars@eggert.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEFF3C151545; Wed, 1 Mar 2023 10:32:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_HI=-5, 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 (1024-bit key) header.d=eggert.org
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 nhvbmuEhPmvN; Wed, 1 Mar 2023 10:32:48 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4B3CC14CF1C; Wed, 1 Mar 2023 10:32:47 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:9c3c:8227:4c1c:701e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id A2E6421AF9; Wed, 1 Mar 2023 20:32:40 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1677695560; bh=yhvQBRWAYLCd5W0uEDx20ZT24va73C8SzRtIW1TXuSw=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=znUPk/cSFoqymfGpWNuWRVtIU68zVmmE6pFKl9S5WTIeUg9H5gWOKQmDw/J4o8TjQ u4T1W+ZgixVI2TOPWTabBUyvIpCkSO6krnnDBDBxX6CCwcLodxWBVJUEe//bNDSMqQ KCDhQqP3So3Jb3WAezSNaSdlaAmevwoKZD4WVu0M=
Content-Type: multipart/signed; boundary="Apple-Mail=_8DD8207B-E0D6-4B5C-A594-9A74026C3AB6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <ED692615-B5CF-458B-A911-F965C56BB0DE@trevilon.com>
Date: Wed, 01 Mar 2023 20:32:39 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-opsawg-tlstm-update@ietf.org, opsawg@ietf.org, opsawg-chairs@ietf.org
Message-Id: <0B92A09F-C4BC-4919-B97C-D7FE39836698@eggert.org>
References: <167758765810.37270.16823163994872633891@ietfa.amsl.com> <ED692615-B5CF-458B-A911-F965C56BB0DE@trevilon.com>
To: Kenneth Vaughn <kvaughn@trevilon.com>
X-MailScanner-ID: A2E6421AF9.A8758
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/TisyNsh-vD66IY-V6bOOjUQOwxc>
Subject: Re: [OPSAWG] Lars Eggert's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2023 18:32:52 -0000

Hi,

On Mar 1, 2023, at 20:30, Kenneth Vaughn <kvaughn@trevilon.com> wrote:
>> No reference entries found for these items, which were mentioned in the text:
>> `[RFC3413]`, `[RFC2579]`, `[RFC3411]`, `[RFC2578]`, and `[RFC2580]`.
> All of these references are part of either STD58 or STD62, both of which are listed under normative references.
> 
> I have not made any changes as it is unclear how this should be handled.
>     •
> Do I leave as is?

yes, leave as is. (Bug in my checker tool it seems.)

>> Document updates `RFC6353`, but does not cite it as a reference, which is a bit
>> odd.
> I do not understand this comment. The document is cited in the body of the text (e.g., first paragraph of Section 2) and is listed under normative references. I am not sure what additional citation is being proposed.

Ditto. Sorry about that.

Lars

v2.23.0 | Report a Bug | By Email