Doing nothing is always an option. These kind folks are proposing doing
something, though, rather than nothing. This makes sense, because the
working group might no longer exist, and email archives are useless for
getting a summary of perhaps a few years of commentary that may have
occurred.
Do you have a specific objection to doing something, or do you just not
want to have to be the one to do it? :)
On Tue, Jul 19, 2016 at 3:16 PM, MH Michael Hammer (5304)
<MHammer(_at_)ag(_dot_)com>
wrote:
-----Original Message-----
From: ietf [mailto:ietf-bounces(_at_)ietf(_dot_)org] On Behalf Of Yaron
Sheffer
Sent: Tuesday, July 19, 2016 7:54 AM
To: IETF
Subject: How to get feedback on published RFCs [resending as plaintext]
Once an RFC is published, there is essentially no way for readers to
provide
feedback: what works, what are the implementation pitfalls, how does the
document relate to other technologies or even to other RFCs.
We IETF insiders usually know what is the relevant working group, and can
take our feedback there. Non-insiders though don't have any contact
point,
and so will most likely keep their feedback to themselves. These
non-IETFers
are the target audience of our documents! Unfortunately, our so-called
"Requests for Comments" are anything but an invitation to submit
comments.
A simple solution would be to include a pointer to the relevant working
group as a header or note to the RFC. There could be a standard "How to
comment" section. No need for additional tools or process.
Mke