Reviews of independent submissions

[elear]

Description

Section 7 of RFC 4846 specifies how reviews are meant to be handled. This has not really been the case. While this feature is supposed to be made available on the RFC Editor web site, perhaps it is best done through the data tracker. That's a discussion point.

As discussed, reviews are expected to be made available to the authors unless the reviewer requests otherwise. Also, the RFC Editor (really the ISE) may, at their discretion, publicly publish reviews. This has to be somewhat configurable at both the draft level and with a default based on the desire of the RFC Editor. My experience thus far is that I would generally make reviews public unless I receive a request that states otherwise. That sounds like a reviewer checkbox.

Code of Conduct

• [X] I agree to follow the IETF's Code of Conduct

[elear]

The solution discussed was to use the directorate function to allow reviews to be uploaded. Bubbling up to @rjsparks for prioritization when you are ready for it.

[rjsparks]

I think we discussed this at 120, but you would use the review team functionality only for public reviews, correct? Adding things that are supposed to remain private to the datatracker has been problematic.

[elear]

Don't sweat the private ones.