ietf
[Top] [All Lists]

RE: I-D Working groups and mailing list

2011-08-08 15:44:05
-----Original Message-----
From: John C Klensin [mailto:john-ietf(_at_)jck(_dot_)com]
Sent: Sunday, August 07, 2011 9:19 AM
To: Murray S. Kucherawy; ietf(_at_)ietf(_dot_)org
Subject: RE: I-D Working groups and mailing list

(4) Others (probably a partially overlapping group with (3))
just find more rules and requirements for more boilerplate
undesirable.  They would (at least mostly) be happy if lots of
off-list notes went to authors of I-Ds for which the discussion
forum wasn't clear, asking them about the discussion forum and
recommending that it be included in the next draft.

But flip it around and see what you get: Why should I, as a document author who
wants to notify people where the discussion of the draft should take place, be
forced to use either an ad-hoc location in the document or have to send out a
bunch of additional emails? Why can't there be an *OPTIONAL* well known
location in our draft format (and corresponding XML element(s)) that automated
tools can pick up on so at a minimum this information can go out as part of the
new draft notifications?

In other words, the issue of whether or not there's a well defined way  to
incorporate this information is almost entirely orthogonal to whether or not we
require it's presence.

That might
actually encourage discussion and would be as, or more,
effective at retraining authors than more rules.

This is my preference.  If the author(s) don't include a "discuss this here"
section, then they're inviting direct comments, and maybe that's what they
prefer.

In that case the author can simply list their own address as the discussion
contact point. Why should have dig through an entire document looking for this
information or check my email for a separate message about it?

If not, they will quickly learn to either find or create a forum, even if
that's just ietf(_at_)ietf(_dot_)org, and mention such in the draft.

If it ain't broke, don't fix it.

But what we have now *is* broken, or at least fairly suboptimal.

                                Ned
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf