This review is being done on an experimental basis to gauge whether the comprehensive review of proposals will have a benefits worth the effort. Suggestions were made to publish a list of operational criteria by which the proposals will be measured. Other ideas included a dedicated section in the RFCs similar to the security considerations section identifying possible operational impacts. The Working Group has worked out a few bugs and the area director has pressed the group to get the current version out as a Proposed Standard. The editing cycle is continuing too long.
Revisions are possible as the proposals go to draft standard.
The IESG continued a discussion from the last meeting to refine the requirements for a protocol to be advanced to Draft Standard. After a bit of discussion, the following requirements was made. ALL protocols being considered for Draft Standard status must have at least two implementations, each of which supports all features and options and between which all features and options have been tested. Features and options which have been speicified for future use but which have not been tested must be removed from the specification prior to advancement to Draft Standard. The IESG earlier adopted a position that all protocols eligible for advancement to Draft Standard be presented to an IETF plenary.