Re: [Rfced-future] Comments on -07
Peter Saint-Andre <stpeter@stpeter.im> Fri, 07 January 2022 02:00 UTC
Return-Path: <stpeter@stpeter.im>
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 20C973A0D79 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 18:00:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=stpeter.im header.b=E9mXL3eX; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=aHGHpuSk
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 1hhO5Bgpo4DH for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 18:00:32 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A47C83A0D76 for <rfced-future@iab.org>; Thu, 6 Jan 2022 18:00:32 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AAB7F5C01C0; Thu, 6 Jan 2022 21:00:31 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 06 Jan 2022 21:00:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:subject:to:references:from :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=D dz301MU14sfR2hQcpOST5plwoI/dvAoeV9V+X2SmBk=; b=E9mXL3eXD2BTWI0ao O6imXS5vEM2Pfw9EfxjYSha3kqma34ZZtVZqTS/8/Dcfa4Oo6Fkzg7We1nVkTG3o EFFgz/VtBhnfqXd3eVDJT5MN/QPBo5yfUnLn3ySNsOkgAxGhRhwO3liCFvUWI30Q QoyKJKzWUHzreF8JjiCbzYqILg/NgYrSdEbdIKffzKzR1JtY9wO1GTub6jb3ksix DNEzMJ/9S/+nkZuJ9drRYlHHMjFrpwyr3EIs+RMeeXz1zNtdMjQmVHaaMcfBCwrM MCmrCqI4ov+C9EVUQr9uU81GeCoBK25i0ixXhcailzona9PrluciSKlYjg5Le6No qarPw==
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=fm1; bh=Ddz301MU14sfR2hQcpOST5plwoI/dvAoeV9V+X2Sm Bk=; b=aHGHpuSk/DCd2MpFxb2aWsZcca9/l885l7Q/oNLCWdLQeveLR9qhWIbhm me+1AZW21qI7Ad8o/EGzfQKfKhtvxaJIozGoobOV9opSEfQ+49E7oxSMzdRcUv39 KmI9YhBKK9UplV3UxCdcdXwp6N/hDbXHD+0cEFiNvx0KEP+UHKffclzQeA/gSrme Yhy888653gEvirpKwwGjlemsMGnWAUekJgChDmFAXOjHOXMoy6s6w4CGs/vSqPY4 74CFAFpGsv9DlMZOkOBsx8EW+CEzkQXq7YLxF+QguRDdXwBKRMy1CCP60vcJ2+Tj xSVxki32fUlzlb6Dv8581BXrmyImg==
X-ME-Sender: <xms:v57XYfVZJ3sCXYxv1pj2uMWl9vZse4T4yLWueaQ7KZAZCTNG-NmOsg> <xme:v57XYXmHZXYmXlO6qcpjIccPPD8EkBTFvrXU3DCCSF-9zOvP0LZI7tI5DUTfCjpJr PLRV1w2yrxCIq0gLA>
X-ME-Received: <xmr:v57XYba83WmvBzyQSVIkGuuBD2CuDOHpgfSrG6LZb_J1hMKNz2slkhWQhuPS5WGeHaFtRPPY5YgHyHsiuOy8jGaTFBk7fITILvN_s9Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegtddgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomheprfgvthgv rhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqne cuggftrfgrthhtvghrnhepvedtgfettefgffevheetvddugedugfelveeftdelveetgfef gefggfefledukeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:v57XYaVJoFubTjHx-X4JndMv_mk9Pnu-2UlbMkahlQHcOs0ceJliVg> <xmx:v57XYZldyTvk6FvoN6V_HMMVRbqMep9xIUXqzgxGyH2ZoAapV3BS5Q> <xmx:v57XYXfsxtazghTGrbhLPFJQDi3Qa0rYB4ecbidhj-jRxq4w2V5DaA> <xmx:v57XYewk_xAfdW_cQtQy2FEmYodNGzQlMwQBzMTJwN-xJ0gr-YA6hg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 6 Jan 2022 21:00:31 -0500 (EST)
Message-ID: <84c39595-8bde-d0c4-8513-5813075a84cf@stpeter.im>
Date: Thu, 06 Jan 2022 19:00:27 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Michael StJohns <msj@nthpermutation.com>, Eliot Lear <lear@lear.ch>, "rfced-future@iab.org" <rfced-future@iab.org>
References: <18d1c2c5-cb1d-58d3-d566-0b5f55f7d28f@nthpermutation.com> <211d997a-ea0d-f56c-7329-d0cbc73638a4@lear.ch> <e047ef33-f5fb-ded4-a09c-98812d24d190@nthpermutation.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <e047ef33-f5fb-ded4-a09c-98812d24d190@nthpermutation.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/vek0o_xyb5-LJlThDZ6hJaks7Nk>
Subject: Re: [Rfced-future] Comments on -07
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: Fri, 07 Jan 2022 02:00:38 -0000
On 12/23/21 10:26 AM, Michael StJohns wrote: > On 12/23/2021 2:33 AM, Eliot Lear wrote: >> >> Hi Mike, >> >> On this: >> >> On 22.12.21 21:56, Michael StJohns wrote: >>> S 4.3 bullet 16 - Is this needed if the RPC is an ex officio member >>> of the RSAB? >> >> For context the bullet says the following: >> >> 16. Liaising with stream approving bodies and other representatives >> of the streams as needed. >> >> N.B., “as needed.” >> >>> Shouldn't that be where this interaction mostly happens? "Stream >>> approving bodies" is different than "stream manager" and not having a >>> single POC might be problematic. (Sorry - I see this change was made >>> -05 to -06, but there are a number of places in this document where >>> telling the RPC to talk to an organization is just a bad idea - this >>> comes under the heading of unintended consequences). >> >> One example of when it would be necessary for the RPC and a stream to >> communicate would be in relation to boiler plate questions or >> changes. Another case might involve meta-information such as >> obsoleting/updating of RFCs. According to the draft, these sorts of >> things would not be appropriate for the RSAB, but for the individual >> streams themselves. >> >> Eliot >> > I think that's a fair interpretation, but it used to be "stream > managers" and AFAICT, that was changed to "stream approving bodies" > primarily to eliminate the "stream manager" term, rather than to address > the point you made and hence leading to the question. It also is weird > when reading it for the ISE. > > How about "Liaising with other representatives of the streams as needed" > which says that just not the RSAB member of a stream might be important? I think this is an improvement. Peter
- Re: [Rfced-future] Comments on -07 Eliot Lear
- Re: [Rfced-future] Comments on -07 Michael StJohns
- [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Jay Daley
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Jay Daley
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Eliot Lear
- Re: [Rfced-future] Comments on -07 Eliot Lear
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Martin J. Dürst
- Re: [Rfced-future] Comments on -07 Ole Jacobsen
- Re: [Rfced-future] Comments on -07 Martin J. Dürst
- Re: [Rfced-future] Comments on -07 Peter Saint-Andre
- Re: [Rfced-future] Comments on -07 Salz, Rich
- [Rfced-future] Filling the RSCE position (was: Re… John C Klensin
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 John C Klensin
- Re: [Rfced-future] Comments on -07 Martin Thomson
- Re: [Rfced-future] Comments on -07 Martin Thomson
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… Eric Rescorla
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Jay Daley
- Re: [Rfced-future] Filling the RSCE position (was… Stephen Farrell
- Re: [Rfced-future] Filling the RSCE position (was… Jay Daley
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Eric Rescorla
- Re: [Rfced-future] Filling the RSCE position (was… Jay Daley
- Re: [Rfced-future] Filling the RSCE position (was… Mirja Kuehlewind
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… Mirja Kuehlewind
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Mirja Kuehlewind
- Re: [Rfced-future] Filling the RSCE position (was… Lars Eggert
- Re: [Rfced-future] Comments on -07 Peter Saint-Andre
- Re: [Rfced-future] Filling the RSCE position (was… Peter Saint-Andre
- Re: [Rfced-future] Comments on -07 Peter Saint-Andre
- Re: [Rfced-future] Filling the RSCE position (was… S Moonesamy
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… S Moonesamy