![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Dave Crocker wrote: > > I concur with Keith's assessment that threading AND searching are needed. > > This sub-thread raises a question I've contemplated for awhile, namely that > it is time for the IETF formally REQUIRE that working group mailing lists > be archived, with web access to individual messages. > > Per Keith's observation, I think that threading (HE might not like it but > *I* find it helpful) and searching be required also. > > thoughts? I would like to throw a few ideas into the pot. Our mailing lists use a variety of subscription engines, and are scattered all over the place. It would appear IETF has at least SOME computational resources as an organization. Perhaps a few significant machines could materialize (any computer makers care to make a donation?) and be used to run list services for the WG lists, and host the archives in a consistent fashion? As someone else mentioned, there is occasionally a lack of consistency to the lists and the methods used to host them. -- ----------------------------------------------------------------- Daniel Senie dts at senie.com Amaranth Networks Inc. http://www.amaranthnetworks.com
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.