![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> From: Daniel Senie <dts at SENIE.COM> > ... > Guess I'm not the only one who finds it annoying to read a draft title > which is chock full of acronyms, and then an abstract which says the same > thing, with the same acronyms... If I can't determine what the author is > talking about from the announcement that gets sent to ietf-announce, > there's a good chance I won't read the draft and make comments. > > I think this should go beyond RFCs, and perhaps be added to the Guidelines > for Authors of Drafts. I disagree. Becaause there are too many drafts to read, every good filter is valuable. If the author doesn't know enough to use acronyms in the title properly, then chances are the draft itself won't be readable for additional reasons. Unreadable drafts and RFCs are less likely to be widely implemented. Even when they are widely implemented, life is too short. Vernon Schryver vjs at rhyolite.com
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.