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

Martin Thomson <mt@lowentropy.net> Wed, 23 June 2021 02:19 UTC

Return-Path: <mt@lowentropy.net>
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 23E583A0933 for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 19:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 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_LOW=-0.7, SPF_PASS=-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=lowentropy.net header.b=S2sCRirR; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=EqUwQGRq
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 Pag3XYUAlAQL for <rfced-future@ietfa.amsl.com>; Tue, 22 Jun 2021 19:19:52 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED22A3A2452 for <rfced-future@iab.org>; Tue, 22 Jun 2021 19:19:51 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D9AAC5C00F8 for <rfced-future@iab.org>; Tue, 22 Jun 2021 22:19:50 -0400 (EDT)
Received: from imap10 ([10.202.2.60]) by compute4.internal (MEProxy); Tue, 22 Jun 2021 22:19:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm2; bh=7f6Km jaBlPdbaYjXA3mXMBBF0y2DiOZTwHrM6l9DKbQ=; b=S2sCRirR182H/5aHHGsqg gRow4kPxWnE3lENpfkrNilJAZeEoHB+yPw6L3TArR55984LSsI3W5l+njHw53/Z9 0QQSD8JoDZeArSMJ1KREZkmAfTdj5cQ/PqFR6Ss834GMY74WyIluxkraDpSrbFUB C3cT24MVfSQBLJm5igu608MNu9gsnd0rMFSZ8j5esxXv9386Fb/jQLgEcwQJNcc7 Ywzk/dw2GKeP21/neEJsq0/Co6WqRCtpvxQeXM4zQhA5kt7faXdzZOPyrz7VwvMO INZ7I1pKTGMHya47nbNahNpmRx0QDKkpKKJcowPdRkzPPiT9w1Scv+rNdxSq4wun w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=7f6KmjaBlPdbaYjXA3mXMBBF0y2DiOZTwHrM6l9DK bQ=; b=EqUwQGRqqjBCQhl5am9mlk4Hg4ACAPt3B/qu0lQ7ysICabYJiB4Ok4/eu iTlQX2GyacnV8aFRhDGPqBfcVkpjELHtc1ErLkzT3LkcyV1GJVy4I/njRLYQUg+Y A/4m+O+G0SQGVeKUW0NrLWVOAeO2LdPU3fCZwK+afu6Qdsvg2HRbVdXs0DH8to0b h7MK9WgWskpZmY9RR2vwTxQREB/NsXB0MVHlvJW2tHWCq14bRkcqf+nfvCGiaxIZ hU5smnSPYzUX9vJ1rxYJY5o5CVn2PhU6um+9lbaXpvF1Wi+iSg6tXdvoNAZ346+4 uk5+1FxynPfCZTROWZfDiPr4cWRKg==
X-ME-Sender: <xms:RprSYASDg9NypBJa0ivkmxnaFCcT2vqEypeyFmxmzaJLEl9ntoXnqQ> <xme:RprSYNx8Wr6hWrybjbSiKNcqudpOGBI6cp3SUaUlBdK6MTzzOEOZpYA_eLi7alkWx 8_hxRcW6GTDxBGXDb8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeegvddghedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepgfejueduieffledtge elheejvdettdejudduhefggeefgfekgfeuieetgefftddtnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:RprSYN0p5TL94Uhxk5ea3evFMBy0xQU0AcOHXx_PppUEseGZWlVwBA> <xmx:RprSYEDNzhEfv5Kob5GYXDYwsE9qkWsy5hC8L2ICtUPAwo-3nj-F-A> <xmx:RprSYJiouFT3j9CJqg5juHeWrR_kXuSsXJ2H_oHsFxEvmFwLAiPAeQ> <xmx:RprSYEvKN-puNAmUQAefFECgdvove94GISTmN9UrhHQZbunX4jPg0g>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 837DB4E00AA; Tue, 22 Jun 2021 22:19:50 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-530-gd0c265785f-fm-20210616.002-gd0c26578
Mime-Version: 1.0
Message-Id: <f5e7fe7c-f6d7-4193-a8ae-64549fe7ef10@www.fastmail.com>
In-Reply-To: <25bbe57b-f2fb-b07a-c5e4-0027156f03a7@nthpermutation.com>
References: <04B7BD6D-612C-410B-BD71-07680CE2D4AB@ietf.org> <09ba8d20-0793-4068-9857-04350b6e64ee@www.fastmail.com> <25bbe57b-f2fb-b07a-c5e4-0027156f03a7@nthpermutation.com>
Date: Wed, 23 Jun 2021 12:19:33 +1000
From: Martin Thomson <mt@lowentropy.net>
To: rfced-future@iab.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/DFecX2NPFbOZuw9Dk6Lrrf3Bi30>
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: Wed, 23 Jun 2021 02:19:57 -0000

On Wed, Jun 23, 2021, at 11:58, Michael StJohns wrote:
> Ultimately, legally and effectively, the timing and priority of any work 
> by the RPC is an LLC/RPC decision.  Ditto for any hired/contracted for 
> RSA/E (mutual agreement consistent with the contract/employment 
> agreement).  So yes - the RSAB may say "deprioritize" vs RSWG 
> "emphasize" at which point if there's disagreement, that's going to be 
> an interesting contractual discussion between the LLC contract manager 
> and the RPC based on input from both the RSAB and the RSWG.  That's just 
> reality and I don't really thing we need to spend a lot of time on 
> trying to change how those levers of power are manipulated.  If there's 
> a massive failure later, AND someone has a better idea, AND it can be 
> implemented through contractual language, THEN we can readdress this point.

I wasn't suggesting that we needed to change the substance here, just to change the emphasis on the text.  You'll note that I just reworded Jay's text, not changed the bullet points.
 
> Which also has me asking a question:  Should the LLC provide a liaison 
> to the RSAB as mandatory requirement?

Not mandatory, and I don't think we need formal encouragement for everyone to be proactively consultative.  I'd rather stay silent (for reasons similar to those you outline above).