![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Jeffrey Hutzelman wrote:One might want to wonder, a bit, about the IETF's having a growing number of such documents, and that this might make it more difficult to know enough about IETF procedures and the like
On the contrary, I don't think the process has gotten any more complex; we just have more documentation about it.
[...] I'm sure the list is longer, but the above seem sufficient for making the point.
Yes, the rules are different, just as the rules for Informational RFCs are different from standards track RFCs. That's why the idea of a new RFC sub-category make sense.
Maybe. But it seems sort of heavyweight to me.
The same sort of correction would have taken the IETF six months to a year plus a lot of arguing and reopening old issues.
And then there is the possibility that you are describing a deeper IETF problem that needs its own focus...
-- Jeff
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.