The basic problem with Acronyms is that they do not
tend to include enough vowels;-)...
This leads to what I call "acronymics"
or "painful acronyms".
But, this problem has a possible solution:
If your first try with initial letters fails to satisfy,
try using the first 2 letters, likely including more vowels.
And, if that does not work, use the first 3 letters...
Etc, until you reach the degenerate case
of just using whatever language you prefer;-)...
This is a language independent solution.
All acronyms can be shown to degenerate
into some kind of natural language.
At 15:20 -0700 09/09/01, Bob Braden wrote:
>Jiwoong,
>
>In my view, any acronynm that would not be instantly understood by 98%
>of the IETF should be defined the first time it appears in the
>document. This seems like just plain common sense and courtesy to the
>reader.
>
>The RFC Editor has started to enforce this usage in the Abstract
>section of an RFC. It might not be a bad idea to enforce it
>everywhere.
>
>Bob Braden
