This shows you the differences between two versions of the page.
— |
acronym [2012/05/07 12:26] (current) rsewikiadmin created |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | Parent issue: Acronyms in RFC | ||
+ | Size (time): 1-6 months from start | ||
+ | |||
+ | Importance/ | ||
+ | |||
+ | |||
+ | Problem Statement: Once a purely internal reference for the RFC Editor, the acronym page has become a publicly available resource for authors to determine if and how certain phrases can be shortened. | ||
+ | |||
+ | Tangential to all of this is a related question of how acronyms should be used in an RFC; whether they should be expanded only upon first use, upon first use in a section, or as the author(s) choose. | ||
+ | |||
+ | |||
+ | RSE Actions: | ||
+ | |||
+ | |||
+ | RSOC Actions: | ||
+ | |||
+ | |||
+ | RFC Production Center & Publisher Actions: | ||
+ | * note: RPC preference is to keep this an informal service. Making it authoritative could introduce confusion in RFC where old usage does not match current requirement | ||
+ | |||
+ | |||
+ | Costs/ | ||
+ | |||
+ | Financial: if the decision is to make the acronym list authoritative, | ||
+ | |||
+ | Project schedules: | ||
+ | |||
+ | Reputation: no major impact as long as a decision is made and clearly communicated | ||
+ | |||
+ | Estimated completion date: TBD |