'Fwd: [Rfced-future] Upcoming Community Consultations on Next Generation RFC Model'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf-announce
Subject:    Fwd: [Rfced-future] Upcoming Community Consultations on Next Generation RFC Model
From:       IAB Chair <iab-chair () iab ! org>
Date:       2021-10-27 13:05:39
Message-ID: 5E4A1F50-DBFF-4F1E-8FB3-D7D195C13010 () iab ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Dear colleagues,

I would like to draw your attention to the message below. The IAB RFC Series \
Editorial Future Development Program is about to finish its work and it's now a good \
time to review draft-iab-rfcefdp-rfced-model!

Please see below for further information!

Mirja

> Begin forwarded message:
> 
> From: Eliot Lear <lear@lear.ch>
> Subject: [Rfced-future] Upcoming Community Consultations on Next Generation RFC \
>                 Model
> Date: 27. October 2021 at 14:12:47 CEST
> To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, gendispatch@ietf.org, The IETF \
>                 List <ietf@ietf.org>, rfc-interest@ietf.org
> Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Brian Rosen <br@brianrosen.net>
> Reply-To: "rfced-future@iab.org" <rfced-future@iab.org>
> 
> Dear colleagues,
> 
> In March of 2020 the IAB kicked off the RFC Series Editorial Future Development \
> Program, a program opened to the entire community, with an eye toward reviewing the \
> RFC Editor model found in draft-iab-rfcefdp-rfced-model-05[1]. We are now coming to \
> the conclusion of our work, and the IAB will soon begin its formal consideration, \
> which is governed by RFC 4845[2]. Part of that process includes solicitation of \
> community input. 
> The program has developed an evolution of the RFC Editor Model and a small change \
> to the charter of the IAB. You can find this evolution in \
> draft-iab-rfcefdp-rfced-model-05 as well as two companion drafts[3,4,5]. This draft \
> brings together many different points of view, as you can see from the mailing list \
> archive[6]. 
> Here are some of the proposed changes that you may wish to know:
> 
> The community oversees the evolution of the series by means of an open working \
> group. Proposed changes that reach rough consensus will be reviewed by an RFC \
> Series Approval Board (RSAB) that consists of the RSCE and people representing the \
> various streams. 
> The RFC Editor role is changing to that of a consulting editor (RFC Series \
> Consulting Editor or RSCE). In this model, an expert will provide guidance to the \
> community, the streams, and to the RPC to evolve the series. 
> The IAB will no longer manage or oversee the RFC series. The community and the \
> streams will do that. The IAB will continue to be in the appeal path if there are \
> disputes. 
> There are a lot of things that won't change. The RPC would continue to handle \
> day-to-day functions of the RFC Editor function, and authors should not see any \
> immediate change in terms of how RFCs are published. They continue to be managed \
> through the LLC. We will continue to benefit from the expertise of a professional \
> expert, now the RSCE. 
> Of course, there's a lot more detail that is specified in the drafts.
> 
> This is what will soon be put forth for your comments. In the meantime, even though \
> the formal comment period is not yet open, we invite you to review the model now \
> and bring whatever questions you might have to the program when we meet on \
> Wednesday, November 10th, at 14.30 GMT at the IETF meeting. Of course you can also \
> join the mailing list[7] and contribute your questions and comments there. 
> On behalf of the program,
> 
> Brian and Eliot
> 
> [1] https://www.iab.org/activities/programs/rfc-editor-future-development-program/ \
> <https://www.iab.org/activities/programs/rfc-editor-future-development-program/> \
> [2] https://www.rfc-editor.org/rfc/rfc4845.html \
> <https://www.rfc-editor.org/rfc/rfc4845.html> [3] \
> https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-05 \
> <https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-05> [4] \
> https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-iab-charter-03 \
> <https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-iab-charter-03> [5] \
> https://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01 \
> <https://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01> [6] \
> https://mailarchive.ietf.org/arch/browse/rfced-future/ \
> <https://mailarchive.ietf.org/arch/browse/rfced-future/> [7] \
> https://www.iab.org/mailman/listinfo/rfced-future \
> <https://www.iab.org/mailman/listinfo/rfced-future>--  Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future

[Attachment #5 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: \
space; line-break: after-white-space;" class="">Dear colleagues,<div class=""><br \
class=""></div><div class="">I would like to draw your attention to the message \
below. The IAB RFC Series Editorial Future Development Program is about to finish its \
work and it's now a good time to review draft-iab-rfcefdp-rfced-model!</div><div \
class=""><br class=""></div><div class="">Please see below for further \
information!</div><div class=""><br class=""></div><div class="">Mirja</div><div \
class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote \
type="cite" class=""><div class="">Begin forwarded message:</div><br \
class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; \
margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: \
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, \
1.0);" class=""><b class="">From: </b></span><span style="font-family: \
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Eliot Lear \
&lt;<a href="mailto:lear@lear.ch" class="">lear@lear.ch</a>&gt;<br \
class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: \
0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, \
Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b \
class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica \
Neue, Helvetica, sans-serif;" class=""><b class="">[Rfced-future] Upcoming Community \
Consultations on Next Generation RFC Model</b><br class=""></span></div><div \
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" \
class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, \
sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span \
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" \
class="">27. October 2021 at 14:12:47 CEST<br class=""></span></div><div \
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" \
class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, \
sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span \
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" \
class="">"<a href="mailto:irtf-discuss@irtf.org" class="">irtf-discuss@irtf.org</a>" \
&lt;<a href="mailto:irtf-discuss@irtf.org" class="">irtf-discuss@irtf.org</a>&gt;, <a \
href="mailto:gendispatch@ietf.org" class="">gendispatch@ietf.org</a>, The IETF List \
&lt;<a href="mailto:ietf@ietf.org" class="">ietf@ietf.org</a>&gt;, <a \
href="mailto:rfc-interest@ietf.org" class="">rfc-interest@ietf.org</a><br \
class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: \
0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, \
Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b \
class="">Cc: </b></span><span style="font-family: -webkit-system-font, Helvetica \
Neue, Helvetica, sans-serif;" class="">"<a href="mailto:rfced-future@iab.org" \
class="">rfced-future@iab.org</a>" &lt;<a href="mailto:rfced-future@iab.org" \
class="">rfced-future@iab.org</a>&gt;, Brian Rosen &lt;<a \
href="mailto:br@brianrosen.net" class="">br@brianrosen.net</a>&gt;<br \
class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: \
0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, \
Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b \
class="">Reply-To: </b></span><span style="font-family: -webkit-system-font, \
Helvetica Neue, Helvetica, sans-serif;" class="">"<a \
href="mailto:rfced-future@iab.org" class="">rfced-future@iab.org</a>" &lt;<a \
href="mailto:rfced-future@iab.org" class="">rfced-future@iab.org</a>&gt;<br \
class=""></span></div><br class=""><div class="">  

    <meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">

  <div class=""><p class="">Dear colleagues,</p><p class="">In March of 2020 the IAB \
kicked off the RFC Series Editorial  Future Development Program, a program opened
      to the entire community, with an eye toward reviewing the RFC
      Editor model found in draft-iab-rfcefdp-rfced-model-05[1]. We are
      now coming to the
      conclusion of our work, and the IAB will soon begin its formal
      consideration, which is governed by
      RFC 4845[2]. Part of that process includes solicitation of
      community input.</p><p class="">The program has developed an evolution of the \
RFC Editor Model  and a small change to the charter of the IAB.
      You can find this evolution in draft-iab-rfcefdp-rfced-model-05 as
      well as two companion drafts[3,4,5].
      This draft brings together many different points of view, as you
      can see from the mailing list archive[6].</p><p class="">Here are some of the \
proposed changes that you may wish to know:</p>  <ol class="">
      <li class=""><p class="">The community oversees the evolution of the series by \
means  of an open working group.
          Proposed changes that reach rough consensus will be reviewed
          by an RFC Series Approval Board (RSAB) that
          consists of the RSCE and people representing the various
          streams.</p>
      </li>
      <li class=""><p class="">The RFC Editor role is changing to that of a \
consulting  editor (RFC Series Consulting Editor or RSCE). In
          this model, an expert will provide guidance to the community,
          the streams, and to the RPC to evolve the series.</p>
      </li>
      <li class=""><p class="">The IAB will no longer manage or oversee the RFC \
series. The  community and the streams will do that. The IAB
          will continue to be in the appeal path if there are disputes.</p>
      </li>
    </ol><p class="">There are a lot of things that won't change. The RPC would
      continue to handle day-to-day functions of the RFC
      Editor function, and authors should not see any immediate change
      in terms of how RFCs are published. They continue to be
      managed through the LLC. We will continue to benefit from the
      expertise of a professional expert, now the RSCE.</p><p class="">Of course, \
                there's a lot more detail that is specified in the
      drafts.</p><p class="">This is what will soon be put forth for your comments. \
In the  meantime, even though the formal comment period is not
      yet open, we invite you to review the model now and bring whatever
      questions you might have to the program when we meet
      on Wednesday, November 10th, at 14.30 GMT at the IETF meeting. Of
      course you can also join the mailing list[7] and
      contribute your questions and comments there.</p><p class="">On behalf of the \
program,</p><p class="">Brian and Eliot</p><p class="">[1] <a \
href="https://www.iab.org/activities/programs/rfc-editor-future-development-program/" \
rel="nofollow" class="moz-txt-link-freetext">https://www.iab.org/activities/programs/rfc-editor-future-development-program/</a><br \
class="">  [2] <a href="https://www.rfc-editor.org/rfc/rfc4845.html" rel="nofollow" \
class="moz-txt-link-freetext">https://www.rfc-editor.org/rfc/rfc4845.html</a><br \
class="">  [3] <a href="https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-05" \
rel="nofollow" class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model-05</a><br \
class="">  [4] <a href="https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-iab-charter-03" \
rel="nofollow" class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/html/draft-carpenter-rfced-iab-charter-03</a><br \
class="">  [5] <a href="https://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01" \
rel="nofollow" class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/html/draft-rosen-rfcefdp-update-2026-01</a><br \
class="">  [6] <a href="https://mailarchive.ietf.org/arch/browse/rfced-future/" \
rel="nofollow" class="moz-txt-link-freetext">https://mailarchive.ietf.org/arch/browse/rfced-future/</a><br \
class="">  [7] <a href="https://www.iab.org/mailman/listinfo/rfced-future" \
rel="nofollow" class="moz-txt-link-freetext">https://www.iab.org/mailman/listinfo/rfced-future</a></p>
  </div>
-- <br class="">Rfced-future mailing list<br class=""><a \
href="mailto:Rfced-future@iab.org" class="">Rfced-future@iab.org</a><br \
class="">https://www.iab.org/mailman/listinfo/rfced-future<br \
class=""></div></blockquote></div><br class=""></div></body></html>

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

[prev in list] [next in list] [prev in thread] [next in thread] 