RFCEFDP at IETF 112

Wednesday, Sesssion 3
Attendees: will be taken by meetecho

Administrivia

Note well.
Chairs’s proposed flow slide. Will definitely need a new version of the document.
Program last call done; got many contributions. Have some new issues as a result.
No agenda changes.

https://github.com/intarchboard/program-rfced-future/issues

Issues believed to be editorial

106, 107, 111, 112, 121, 122, 124, 126, 130, 131, 133

Chair proposal: trust that the editor will do the right thing on these issues. If you see something you don’t like when the update comes out, please comment.
111 moved to “discuss” section.
No comments opposed from the floor, but will be confirmed on the list.

Issues we seem to have acceptance to accept

86, 104, 105, 108, 109, 114, 119, 125, 128, 132

Chair proposal to accept all the offered texts with exceptions noted below.

114 - Simpler process for certain changes
Does the RSCE have to wait to ask a question - RSCE can of course advise - see 128

117 - who controls the website, no text for that. Only accept was for the RSCE text

119 - “Heritage” Mike lists like a dozen characteristics that he wanted to be made explicit. Peter: 8728 and 8729 is quoted in the current draft. Joel: we need to have discussion of the first principles. Chair proposes that if we get a proposal quickly and can quickly get consensus, okay.

Issues that don’t have support

97, 113, 115, 116, 118, 120

Chair proposes to close all these, except as noted below and will confirm on the list.

97: Lars: if a second person leave, and the timer is not reset, that body gets less time. MSJ: tied to last-call issue. Other comments supporting this. Eliot: anyone upset if we do restart the timer? None in the WG, to be confirmed on the list.

Discussion issues

93 - Appeals against RSAB decisions - Proposed text from Martin. MT: Wants things to be done timely and expediently. Wording is perhaps not ideal. No consensus, back to the list.

94 - Who resolves disputes when they need to be timely? - Proposed text from Martin. MT: Timing/order was an issue, PSA proposed resolution onlist.

117 - RSWG for everything? RPC responsibilities and the community - Lots of discussion on list. Eliot to split into two issues, “statements” and responsibilities. Mirja: RSWG should be constrained to write RFC’s, statements should come from RSAB. MNot: I am curious why IAB and IESG put out non-RFC statements sometimes.

Meeting ends. We did not get to these two:

129 - RSWG Chairs issue community last call instead of RSAB - Different views

Added 111 - Selection committees (again)

Future work

We’re close, another interim if we can’t close the last few issues on the list.

Watch for a doc update soon.