On 3/1/2011 3:01 AM, Mark Nottingham wrote:
This is a very good question.
I've considered setting up a wiki page or similar to serve this purpose for
the HTTP family of specifications.
...
If we can find a way to do this, and to cut through the clutter of all of the
other information, it would be very helpful IMO. I'm not sure where it would
start, though.
...
On 01/03/2011, at 3:19 AM, Worley, Dale R (Dale) wrote:
My question is... how is this advice expected to trickle out into actual
use? There are more than 6000 RFCs, and they don't seem to be organized in
a useful way that I can find.
Well, this is entirely premature for the schedule I had in mind -- I had hoped
to add one or two more example sets before exposing this widely -- but this
thread is too timely to ignore.
If you all promise to keep in mind that it is only a /very/ rough and formative
effort, please take a look at:
<http://bbiw.net/trac/suites/>
I believe what it's trying to do is exactly what you are asking for. It's in
trac wiki form because it's intended for eventual adoption by the IETF tools
site. I've been pursuing the activity somewhat like I did for the Outcomes
wiki, although this is proving to be much more effort: getting the design right
and adding initial data is more complicated.
If this does not match what you folks have in mind, my understanding why would
be helpful. If it does seem to be in the right direction, what changes would
you like to see?
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf