Bob, I'm not sure. In my mind a "road map" tells you where something is going: http://en.wikipedia.org/wiki/Technology_roadmap I am kind of looking for where we are now, and possibly where we have been. -- Shane On Tue, 2011-03-01 at 09:34 -0800, Bob Braden wrote: > A few years ago some of us tried to interest the IETF in producing "road > maps" for all the major protocols/protocol families. As a worked > example, we produced a roadmap for TCP. It seems to me that you are > asking for more roadmaps. > > Bob Braden > > On 3/1/2011 4:18 AM, Shane Kerr wrote: > > Mark, > > > > FWIW, this came up in the dnsext working group a few years ago. In the > > end, I don't think anything was done, which is kind of a shame. A lot of > > old protocols could benefit by "this is what is important" documents > > (search the RFCs for "FTP" or "TELNET" to get some examples of protocols > > with lots and lots of RFCs that make it hard to decipher). > > > > Even worse for actual operators who may actually want to use the IETF > > recommendations and not become IETF experts! > > > > I'll join the<rfc-interest@xxxxxxxxxxxxxx> list as Joel suggests, > > although it seems quite chatty with procedural stuff. :-/ > > > > -- > > Shane > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf