[Icar] icar-experiment-early-review-00 comments
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Icar] icar-experiment-early-review-00 comments
a couple of short comments on the icar consensus doc..
semi-substantial
----------------
5.1 Who requests a review
==> this doesn't specify what happens to the review requests which do not
come from WG chairs/secretaries or ADs. In particular, if a doc author
wants to get review of his shiny -00 submission nobody else has bothered to
comment.....
editorial
---------
Quite apart from
the ICAR process, any member of the IETF community may, of
course, review a WG document at any time s/he wishes and provide
that input to the WG.
==> this should maybe be generalized a bit for the case where it isn't a WG
document (but individual submission to an AD). This cornercase seems to be
missing from a couple of places in the draft..
o people who have authored 2 IETF RFCs approved for publication by
the IESG, which includes non-WG documents submitted directly to
the IESG, but not documents submitted directly to the RFC editor
==> This should probably be clearer worded like:
o people who have authored at least 2 IETF RFCs approved for publication by
the IESG (which also includes non-WG documents submitted directly to
the IESG, but not documents submitted directly to the RFC editor)
o current WG chairs whose WG has produced 2 RFCs
==> .. at least 2 ... ;-) -- not sure if this is pedantically required
though..
It is up to the WG chair(s) / secretary to choose the reviewers who
review the document. In order to do this, reviewers in the pool must
be clearly labeled with their area(s) of expertise they feel
qualified to provide .
==> ... "input on"
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
Icar mailing list
Icar at ietf.org
https://www1.ietf.org/mailman/listinfo/icar
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.