From nobody Sun Aug  9 19:44:03 2020
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 C3FBE3A1326
 for <rfced-future@ietfa.amsl.com>; Sun,  9 Aug 2020 19:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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_MSPIKE_H4=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=lowentropy.net header.b=t/B3xJcR;
 dkim=pass (2048-bit key)
 header.d=messagingengine.com header.b=dAUg+UbG
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 veJi8P41fgWI for <rfced-future@ietfa.amsl.com>;
 Sun,  9 Aug 2020 19:44:00 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com
 [64.147.123.24])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 065E83A0E52
 for <rfced-future@iab.org>; Sun,  9 Aug 2020 19:43:59 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
 by mailout.west.internal (Postfix) with ESMTP id 28F461685
 for <rfced-future@iab.org>; Sun,  9 Aug 2020 22:43:59 -0400 (EDT)
Received: from imap2 ([10.202.2.52])
 by compute2.internal (MEProxy); Sun, 09 Aug 2020 22:43:59 -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; s=fm3; bh=qqsDK40ihc6XzKdOLiCzL7ZEz32bpPZ
 PpdF69TZaRlw=; b=t/B3xJcRPAWn4V/GexImMPw6xy+wydqU4jqOcR1KtxU6zBE
 hFUG1XifjMLDz3f6yBwTYUq/ZVC96CdTV2NC5Bh0FAEtzdqzRZgsmAGh6nHJ+Ur/
 OVb4swUZv0mt83IQ94d1/GhMnGhQHEUhRxgz5iXrccV92h6mlh+9BqxZidKNZtv1
 9B8MO88788/jEmC+TB4JTFudWRfg/BFlGOYAevz4NxewLesLxbukyOtGGMRtRGJP
 6pbuAks56wrkD8sG4VqPUflPLi7/kgRtPbAVvhbCcj6qi2G+4uhSHF5rN4pHUont
 pA8yDWFRDKSKr9hVvrHxdods8m4VGEjAPl0S57w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=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=qqsDK4
 0ihc6XzKdOLiCzL7ZEz32bpPZPpdF69TZaRlw=; b=dAUg+UbGDcreGzJfIJpmCW
 mg0+rYPrr9RvLhUV0eTgkOXCTHAgBQw99y1+VfDRt8J7zZj5dBU9YthE6IMo38CJ
 6kQfmckfMJWJM7NZlafndrWj6H4rTsjMPdmKuUERa7dHBwySYn6N7WSlDsEpMvLC
 6VfIKup/tj9QfQrUwt+cAzq6lxgl34LpY6EOOQyuDreG0TWi+63mc8jSDI3EvBE7
 Hjrs/XWvTPd402NW2Wn0iiZuf58VOoDyCZrhraL7b+t8cEp4PvR9TC0ySl/7Buny
 C7TOd7kj72Q21bleeHhHnZkzBEFN1kwSbWUIM9Y0qX+fZtYG5J6L+d1ESD9Tj5kw
 ==
X-ME-Sender: <xms:brQwX05LcxewktqCyllWoFCjT2jQTgG6nPxxcpInjZ4SeFvw4q25BA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrkeejgdeivdcutefuodetggdotefrodftvf
 curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
 uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre
 dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif
 vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepleehhfdvveeuieegfeekie
 eigeeiveehuedthfeitddufeetvdejteevieegudelnecuffhomhgrihhnpehivghtfhdr
 ohhrghdpihgrsgdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh
 grihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:brQwX15Anem1ulH9NZNgnRZQ_5QNk7_YYAmVsjYMKq6YZ3mkakydmQ>
 <xmx:brQwXzc00ZFQM1RnfCvjmBN8y6xa9cvfm6rG9yz7ZaBLT_3f9SFwmw>
 <xmx:brQwX5IRlCSNsLpwjO7e8d5crPlDdZF4uBtU9qnV2MfRYGVZWLfjgg>
 <xmx:brQwX3YDn05yjMlDo77RP0Mnbfo4pOzUAGYh9hrZhBDfPtH4kDwBtg>
Received: by mailuser.nyi.internal (Postfix, from userid 501)
 id 22E38E00EA; Sun,  9 Aug 2020 22:43:58 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-143-g3d58b38-fm-20200806.002-g3d58b387
Mime-Version: 1.0
Message-Id: <7d7a228a-5182-4afc-b804-1ab0c5250ac2@www.fastmail.com>
In-Reply-To: <AFAC09A3-4242-4774-8765-45176290E9E3@brianrosen.net>
References: <AFAC09A3-4242-4774-8765-45176290E9E3@brianrosen.net>
Date: Mon, 10 Aug 2020 12:43:02 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: rfced-future@iab.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Uwbz9DoYvTzQvMFuFgIzuqMayNg>
Subject: Re: [Rfced-future] Next Step - proposals?
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, 10 Aug 2020 02:44:02 -0000

Hi Brian,

I just updated and posted <https://datatracker.ietf.org/doc/html/draft-thomson-rfced-model-01>.  I believe that the original did address your requirements already, but I've added a little bit more content and made a few corrections.

Cheers,
Martin

On Sat, Aug 8, 2020, at 00:55, Brian Rosen wrote:
> Dear colleagues,
> 
> The chairs would like to thank you for participating in the IETF 108 
> meeting of the RFC Editor Futures program.  We learned quite a bit at 
> that meeting, not the least of which was that the group is not yet 
> prepared to choose a direction.
> 
> Therefore, what we are thinking is that the next step should be for 
> people to develop fleshed out proposals.  It would be good to have 
> several alternatives that explore the different philosophies that have 
> been expressed in the group.  Each proposal should be very clear on a 
> few points:
> 
>  * Overall motivation and philosophy
>  * What each proposed entity is responsible for
>  * What the relationship of each entity is to other entities 
>  * What accountability, selection, and transparency mechanisms are in 
> play for each entity
> 
> The next step would be for us to discuss these proposals and see if we 
> can find some common ground.  Our thinking is that we would appoint a 
> neutral editor to document that common ground, which could come from 
> any proposal.
> 
> The timing for any interim to discuss these depends very much on having 
> proposals.  There are some drafts already of course, and we hope we can 
> have more soon.
> 
> Thoughts?
> 
> Eliot and Brian
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>

