IETF Logo Mail Archive

Re: [Rfced-future] Issue 144

Eric Rescorla <ekr@rtfm.com> Thu, 06 January 2022 16:44 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3ED23A0D72 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 08:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.com
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 UBC4slvQaSLc for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 08:44:26 -0800 (PST)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 31E313A0DA0 for <rfced-future@iab.org>; Thu, 6 Jan 2022 08:44:26 -0800 (PST)
Received: by mail-il1-x12f.google.com with SMTP id v10so2531616ilj.3 for <rfced-future@iab.org>; Thu, 06 Jan 2022 08:44:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HxlIn0G/g4wLrreX9mysfOUqzLlgVIAgqu/3+5/ISu0=; b=kMvHajZl0wjl3TOjXisTrZ+QXWJz0Cbf8Iqh7Tn9M5lHVXcqN48UrGc9MN3+0aF8Wi TFrIcmTG9xseldmVPN5IoYVZMGTpwUy7bMGOV6vqiWmQ9o7RsvHeqWKyY3clnNqxiP3U 5q823ox2q8RfXd1+7O7+dsa0zKXHdOg4Mjlm8B/K7JfETaO5ZFhrBl+F3z4fbwPe4Yx1 28/4hmU6XyhRQadaS2ADRT+/2PYph/b+HMM+hSgRqZrg/VtrxGaOOnq2oOzBRFobP0YS 0dOINBWc2j1aeD3T/Jkfx+HSEb+Qyd7DxoZprfZAtqpnJboEP5HPRlrCKNT8fJK2MGV3 bY/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HxlIn0G/g4wLrreX9mysfOUqzLlgVIAgqu/3+5/ISu0=; b=uw7ReRzlIxCwJO0Ct12t+UMGWBf4XlfECfR3bXK7wgFqm/subwbX3+XT11pi4j0td7 ZMWzK3I3AKsrPgQNW09YsI7/cIpm8x1RUUoYXwCNFzT+yZ4wJp2aggB734Q7XsPBpshQ UBUiRKrg94RS0JpcaUpCMnCz8nmOId25Q+wlBZ9FJAUiyACR4KPuU2WiOLcyxgoco4rw FX/b/VCPCIhmZ61QVY4KMBZiUqvdiQLJinycQltryNjqH0RAwH7RtlyI4+qWt497PLoW a27VAoqa4GYQgnPVxdmThdUgDkBpmxltYl7jrK2ndzVR7PqMqPK/WbaFeCkj8y0tQkDe Afdw==
X-Gm-Message-State: AOAM533V3PGSX02k4VBEREL3HCpe8GXXA+Ue/9Q4n5gZVFJTKxkP/Lqk yiUvJoNx3L1sthZvnHe11j5UdUC3eqfqF1fK8TNSXUSEs0I=
X-Google-Smtp-Source: ABdhPJz4O10oumP68pztrALAFbv4dI5W3DSbYtApx+Rv7AeOsQmsUMr1lmhAk6lQyYdaOkealXVosshKAGRWmvFTOa8=
X-Received: by 2002:a05:6e02:1b05:: with SMTP id i5mr29966737ilv.60.1641487464097; Thu, 06 Jan 2022 08:44:24 -0800 (PST)
MIME-Version: 1.0
References: <CABcZeBO3-q+SMTFNZyeC50eghFs1CJNSLojmr1Zip1g_nsGZHQ@mail.gmail.com> <d7ce7879-2324-69d1-0770-e104aff6c68c@stpeter.im> <53497e97-ed65-93c8-5f4c-3f4ee9943501@stpeter.im> <FBE56AF3-8E2A-43D1-920B-F3F1EA6C6CD4@sobco.com> <8F21BC41-404A-4007-8436-AE2506C6A0A2@akamai.com>
In-Reply-To: <8F21BC41-404A-4007-8436-AE2506C6A0A2@akamai.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 06 Jan 2022 08:43:48 -0800
Message-ID: <CABcZeBNcuywBJfHAbL_5GYgLp6t+-pWWBbuCZKnQzqjp7BYxNg@mail.gmail.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: Scott Bradner <sob@sobco.com>, Peter Saint-Andre <stpeter@stpeter.im>, "rfced-future@iab.org" <rfced-future@iab.org>
Content-Type: multipart/alternative; boundary="00000000000033860405d4ec9517"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ha9eY_dhSu8tZyMz6zw_IKVOmrw>
Subject: Re: [Rfced-future] Issue 144
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2022 16:44:31 -0000

This is kind of what I had in mind, though maybe we have to copy by value?

On Thu, Jan 6, 2022 at 6:16 AM Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org>
wrote:

> >    "The RSWG is also empowered to hold in-person or online meetings,
> which shall be announced at least four weeks in advance for in-person or
> hybrid meetings and at least two weeks in advance for all-online meetings."
>
> Any reason we can't just say "notification must follow the current IETF
> policy" ?
>
> --
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>

v2.23.0 | Report a Bug | By Email