Re: [Rfced-future] Suggested text for issues #56, #57, #61, #62

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 05 July 2021 04:52 UTC

Return-Path: <brian.e.carpenter@gmail.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 AEF993A1357 for <rfced-future@ietfa.amsl.com>; Sun, 4 Jul 2021 21:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level:
X-Spam-Status: No, score=-2.436 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 GztCpCk1N__x for <rfced-future@ietfa.amsl.com>; Sun, 4 Jul 2021 21:52:12 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 87F033A135A for <rfced-future@iab.org>; Sun, 4 Jul 2021 21:52:12 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id i184so2677690pfc.12 for <rfced-future@iab.org>; Sun, 04 Jul 2021 21:52:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=VVKr0H95nrhH7ddDcVj9nVgnDTyc9rZjwTg52HS58Wg=; b=rv0mZWKHM9/Pwe/G3ViFWTkL16EjVUXTNLNjS/3FbRpjzBZXog4lqBfWaYleTrSgI6 fKB4AaIfnXn3oVv2Y5ptmQ60fHqShbDbmihZuZQuiglwxRrGegq9ekvoEk3aPrqRdiFp 08lSIWIAsyoD/5rj0kCCJjZFrTAf7ioPW/F7SUaxuIkzJBsLWGeep2Ij8+KmEat9Tt2q IeV1m0kvdhAoFnO1MI00rCHqE6+NzK490kr8x+sTjmypOml/IODOtp6n8d155dB7J03y TTBLfh+pwKHkd9H3W282TMZ4l4hZc76YVfO20lCX/vt5xWro3GPwtuDodvjfOmPsDBa4 yKUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=VVKr0H95nrhH7ddDcVj9nVgnDTyc9rZjwTg52HS58Wg=; b=V4U9o3/jBD68BmyoHci+I2ZZQSGiHw/U1iaM+fsjjivGf4Ssh2MOwfBvqb1T1FPa6y KotNRxky8dFTmjhHt7FMiz+K7LgkSBSxOoQRR4qp2jxkmDSiHLG4jgNvVsSq3gkDVCl/ 3vI2vG5rgu/x30E11AjyKLdAT6qWvLnjE0V3HDSRU6S5Rx3BF9lUzBkgfN4PjTLERO3O dwbEg/rYioYn8ZTRBo8XiADawAq95nySzMmnWvdRTbJV2SPcdCQ93RGQ3M5taeyQ1t5Y qZ/MVYA19PnhjyXZgZOl/RqgsRkGGHJEX6W/SC510tCIySqi1q9Kl8zcScqnbtkRewSH PQVQ==
X-Gm-Message-State: AOAM530aKfKtD1JoxlQMNS+nsEZknUi5E91Q0YmWNiUrNPeGLasxI6rB pv8FcagqY7YGljIYID/UZjlLxtBIvr48hA==
X-Google-Smtp-Source: ABdhPJyvvMih5nrX/ZAg7q8qDNdEmSl8ijBTcHC+wfC3ifgG6TIrBv3ivNIBOm1PWNPi9O0VMVJjDQ==
X-Received: by 2002:a63:d709:: with SMTP id d9mr13912304pgg.337.1625460730852; Sun, 04 Jul 2021 21:52:10 -0700 (PDT)
Received: from ?IPv6:2406:e003:1188:5b01:80b2:5c79:2266:e431? ([2406:e003:1188:5b01:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id 125sm11146596pfg.52.2021.07.04.21.52.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 04 Jul 2021 21:52:10 -0700 (PDT)
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Eliot Lear <lear@lear.ch>, Jay Daley <jay@ietf.org>, Michael StJohns <msj@nthpermutation.com>
Cc: rfced-future@iab.org
References: <c19898f2-7103-d816-b8a0-e00c221a36a8@lear.ch> <896D122F-C341-4B1F-9467-48040F691A42@ietf.org> <096215b8-ba95-7406-fbe5-fcf145417fc3@gmail.com> <9114EB06-AB70-4E6A-A72B-0D7D5867C74A@ietf.org> <538d1ce7-6e4b-fea0-f04b-36669c43dec1@nthpermutation.com> <A38FB1EF-6093-42AB-9EFA-02761AD43DCE@ietf.org> <996b71fc-6ebd-06a1-9a0a-2695a6044381@nthpermutation.com> <C75BE50A-B4BC-46EE-8B6D-06F79F8DE386@ietf.org> <4ad09680-b067-4475-9232-e8f69101e7c0@lear.ch> <3295300e-d396-36fc-2137-6452de7f5296@nthpermutation.com> <b20cf9e2-fff2-f772-b483-b0ad006a160b@nthpermutation.com> <B9289BB9-6BF2-4684-8A5C-D291941CD7A5@ietf.org> <a5bf2148-101b-345e-99ed-baf9be4a9bba@lear.ch> <848d287a-d2e5-7e61-90c4-e3718c010906@gmail.com> <086c5844-ef49-4221-94f2-67408182c6a6@it.aoyama.ac.jp>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <3b86de0d-6823-c740-7928-4258a420d990@gmail.com>
Date: Mon, 05 Jul 2021 16:52:05 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <086c5844-ef49-4221-94f2-67408182c6a6@it.aoyama.ac.jp>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/scvyLmhUtaufu8i5NmFxzhNtn-w>
Subject: Re: [Rfced-future] Suggested text for issues #56, #57, #61, #62
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: Mon, 05 Jul 2021 04:52:17 -0000

On 05-Jul-21 16:31, Martin J. Dürst wrote:
> 
> 
> On 2021-07-01 05:57, Brian E Carpenter wrote:
>> On 01-Jul-21 07:40, Eliot Lear wrote:
>>>
>>> Here's the model, slightly tweaked, but the goal is not to wordsmith this model, but rather to explain the relationships with the RPC in particular (e.g., the first two bullets are really just there for completeness; we've covered that ground).  I don't think this text goes into the 
draft.  We need something that is a bit more elaborated.  But if
>> people are comfortable with the general approach, then we have a good starting point to develop appropriate text.
>>>
>>>>    * The RSWG establishes policy, with input from the community, the 
RSAB, and the RSEA.
>>>>    * The RSAB considers those proposals and approves or returns as appropriate.
>>>>    * The RPC periodically reports to the RSAB on how it is implementing
>> that policy.
>>>>    * The RSEA provides expertise to the RPC and RSAB on how to implement the policy on an ongoing and operational basis, perhaps raising issues along the way for both the RSAB and community to consider.
>>
>> Yes, I think that position's the RSEA's role nicely (and to my mind, fixes the name as RSA because the RSEA is clearly *not* in authority).
> 
> I'm somewhat worried here. While I agree with Martin Thomson (see 
> separate mail) that it's the RSWG that establishes policy, I think it's 

> important to mention that the RS[EA...] not only provides expertise on 
> how to implement policy, but also on potential new policies, including 
> proposing new policies by themselves. "perhaps raising issues" may have 

> been written to include that, but in my view, it's quite weak.

That text isn't the primary part of the RSEA's job description, though.
I thought it was OK in the context of this part of the draft.

    Brian

> 
> Regards,   Martin.
> 
> 
>>     Brian
>>
>>>>
>>>> If issues arise with particular policies, the RPC still brings them to
>> the RSAB who interprets the policy, and provides interim guidance to the RPC, informing the RSWG of those interpretations.
>>>>
>>> Are there people who are generally uncomfortable with the overall approach?  Please discuss.
>>>
>>> Eliot
>>>