IETF Logo Mail Archive

Re: [Rfced-future] Issue 144

Eric Rescorla <ekr@rtfm.com> Thu, 06 January 2022 17:07 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 DC1183A1317 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 09:07:45 -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 96AbU7AokvEK for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 09:07:40 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 BD49A3A1316 for <rfced-future@iab.org>; Thu, 6 Jan 2022 09:07:40 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id t8so2551975ilf.12 for <rfced-future@iab.org>; Thu, 06 Jan 2022 09:07:40 -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=RAJtDW/cYN+3/Ob0zckbkORChmw93aH39r/DmG6I/P4=; b=6mbOHRCxfQC67izrYTJU+G9zAFgSkwH+0DKUJcubf7wxgDJVQ5zc3j7+kRMMzkfCMv K/ptmdxTyHgIdkfgLw3vABjox4BwM5m1Ncy+5rzaoq7R6+lxRNINgB91vwJAa9z1MfSJ oZaodI6aNt/Gk63ZRhil2+sSpu5q+/ODQ/5PAlb6t5+yqS3yhEUcVInB6sCo3MTrQw0A pzQMMRa4GKa7YG2sFmooW92I7Me4zAhKUyAOrYY/WyB9NpWKCPOVqSvw9Jsi7Vf9q47M vdQ+8W2u++XfQ3fA2wLOI/OOZBC9dAQ4odD8C5R2IDwS0I2Vb4IH6/sqW7QpfUrr3Nad 930Q==
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=RAJtDW/cYN+3/Ob0zckbkORChmw93aH39r/DmG6I/P4=; b=q8VsF7XoO9HOUpsEiA6CRxafHAAX7tAZCoHauXi/z7tdVreETcqiA3hCIszYsX7BSE aLrtDu1kyVP6qlRrQrgYjNkbzsi9N/n1+9sfnNeP0NyRZpTb9ENTbO7ubJc0yNv0CLg3 jokZi59vY3ThfmtZ0OPyqDuhv4EQjBLXz6vcTg2itTgf+UBtXOM2bfqKeOe8+Xq6Jo5t 8+owmxS9JuOAx0P9h12bNNWreMJ5uCdpIrJtXJLQpK0lYDtg0IzbtPz7dktk6nF9L/1V urfd1GvV2Caj3FoTB00LSa2VG25ZI6HhVDnNUv2fuemlbmTrUQ7K110dm4sp2mA9zGxn kqBA==
X-Gm-Message-State: AOAM5332t7b29J3TG6BhFkrdVrYUojKGvn7gbKgv+yvX+UAqV/iHee+f hRe0xjwpB+F7AbwB1ijcNJ1zlcDWlqmvluJEammKSw==
X-Google-Smtp-Source: ABdhPJzf4kIokeTwR6hqo2hPXkAvkpDozXLonRyQKGTIDF6X23dvARwCALBZWOFXW0keNZRWDO+Ec36w7p+FfRt3FEc=
X-Received: by 2002:a05:6e02:14d1:: with SMTP id o17mr28663106ilk.276.1641488859101; Thu, 06 Jan 2022 09:07:39 -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> <CABcZeBNcuywBJfHAbL_5GYgLp6t+-pWWBbuCZKnQzqjp7BYxNg@mail.gmail.com> <DC6F136A-8FC4-4A6F-B42A-ED8BE3544999@akamai.com>
In-Reply-To: <DC6F136A-8FC4-4A6F-B42A-ED8BE3544999@akamai.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 06 Jan 2022 09:07:03 -0800
Message-ID: <CABcZeBOGPsA7WmBcw_NwjLa60G1_8F0ZW4YzNNeyLy3rLNOhiw@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
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="00000000000059920405d4ece82f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/G32gOclfkDy469cqQzr2RRyQEgY>
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 17:07:46 -0000

On Thu, Jan 6, 2022 at 9:02 AM Salz, Rich <rsalz@akamai.com> wrote:

>
>
>    - This is kind of what I had in mind, though maybe we have to copy by
>    value?
>
>
>
> I don’t want to make a copy, since if the IETF changes its policies, the
> RSGW should follow what the IETF does.
>

Sorry for not being clear. I agree with this, but I suspect others may feel
differently in that they don't want this
to be subject to changed IETF policies.

So, my preference order is

1. Refer to the IETF policies
2. Copy the now current IETF policies
3. Invent our own.

-Ekr

v2.23.0 | Report a Bug | By Email