IETF Logo Mail Archive

Re: [Last-Call] Tsvart last call review of draft-rsalz-2028bis-05

Lars Eggert <lars@eggert.org> Mon, 07 March 2022 08:29 UTC

Return-Path: <lars@eggert.org>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D733A0A86; Mon, 7 Mar 2022 00:29:37 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 3GqDvFCi-tKN; Mon, 7 Mar 2022 00:29:26 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (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 A667C3A0A73; Mon, 7 Mar 2022 00:29:25 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:d856:7fda:b24d:a65a]) (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 EFBE71D873A; Mon, 7 Mar 2022 10:29:16 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1646641757; bh=Do2CAqyikRQL9pBPMzz13qiuaDDxuhDIEXnY0crEliQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=cYvwZLU0j6TCbRbBblzOfDKP6frFVqsVKzE2uhzqTAMVEIfiOpPeYaBwI+xp+596W 92DfWhpgtnD0OpNpOu7tNJeKxoIXT3lcmoBKobTY9Q7dzcpRNgWD3S57lxDAGxpHnr b4UcAkkBg5B1MxocV/zbsIqPObofP+7ZB3x5N348=
Content-Type: multipart/signed; boundary="Apple-Mail=_88323845-C6B2-4083-894B-696FE6B83DF5"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <6261D50C-9528-427D-885E-56901711E5E5@akamai.com>
Date: Mon, 7 Mar 2022 10:29:16 +0200
Cc: David Black <david.black@dell.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "draft-rsalz-2028bis.all@ietf.org" <draft-rsalz-2028bis.all@ietf.org>
Message-Id: <A555E703-713A-438E-B252-EBB4E98B83F6@eggert.org>
References: <164645467318.28405.3420005942250386923@ietfa.amsl.com> <6261D50C-9528-427D-885E-56901711E5E5@akamai.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
X-MailScanner-ID: EFBE71D873A.A743A
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/last-call/B_iWK47PDo0DVCRGueghPzIO8iY>
Subject: Re: [Last-Call] Tsvart last call review of draft-rsalz-2028bis-05
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2022 08:29:39 -0000

Hi,

On 2022-3-5, at 15:34, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>>   It would be helpful for Section 3 to note that with the exception of the General
>    Area, each Area usually has more than one AD.
> 
> I put it in the Area Director, individual section.  Okay?  Chaired by the IETF Chair is a little clunky, if anyone has suggestions.

do we in fact want to mention this here? IIRC nothing would prevent the appointment of a second GEN AD, which could handle just the GEN area but not be a second IETF chair.

Thanks,
Lars

v2.8.7 | Report a Bug | By Email