IANA Considerations for Three Letter Acronyms
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 7
- Abstract
- Three Letter Acronyms (TLAs) are commonly used to identify components of networks or protocols as designed or specified within the IETF. A common concern is that one acronym may have multiple expansions. While this may not have been an issue in the past, network convergence means that protocols that did not previously operate together are now found in close proximity. This results in contention for acronyms, and confusion in interpretation. Such confusion has the potential to degrade the performance of the Internet as misunderstandings lead to misconfiguration or other operating errors. Given the growing use of TLAs and the relatively small number available, this document specifies a Badly Construed Proposal (BCP) for the management of a registry of TLAs within the IETF, and the procedures for the allocation of new TLAs from the registry. This memo provides information for the Internet community.
- Publication Date
- 2009-04-01
- Status Note
- Informational
- DOI
10.17487/RFC5513- Link
- https://doi.org/10.17487/RFC5513
- Author(s)
- Adrian Farrel
Latest version of IETF RFC 5513
Document Versions — IETF RFC 5513
-
▶ IETF RFC 5513 (2009-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 5226 [Superseded*]
Bibliographic Reference(s)
- Queen of the South Football Club, http://www.qosfc.com/ EXTERNAL
- Queen of the South Football Club, ahttp://www.qosfc.com/ EXTERNAL
- eProcumentStotl@nd, http://www.eprocurementscotland.com/Home/ePS- Service/P2P EXTERNAL
- Cardiff Rugby Football Club, http://www.cardiffrfc.com/ EXTERNAL
- International Essential Tremor Foundation, http://www.essentialtremor.org/ EXTERNAL
- IETF RFC 793 [Superseded*]
- IETF RFC 1819 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5513.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5513, IANA Considerations for Three Letter Acronyms. Available at https://doi.org/10.17487/RFC5513
Snippet:
IETF RFC 5513, IANA Considerations for Three Letter Acronyms. Available at https://doi.org/10.17487/RFC5513
HTML (ISO 690 compliant)
Preview:
IETF RFC 5513, IANA Considerations for Three Letter Acronyms. Available at https://doi.org/10.17487/RFC5513
Snippet:
<span class="citation"><cite>IETF RFC 5513</cite>, IANA Considerations for Three Letter Acronyms. Available at <a href="https://doi.org/10.17487/RFC5513" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5513</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5513, IANA Considerations for Three Letter Acronyms
doi: 10.17487/RFC5513
url: https://doi.org/10.17487/RFC5513
doi: 10.17487/RFC5513
url: https://doi.org/10.17487/RFC5513
Snippet:
<li> <cite id="bib-rfc5513">IETF RFC 5513</cite>, IANA Considerations for Three Letter Acronyms <span class="doi">10.17487/RFC5513</span> </li>
Referenced By
- IETF RFC 6493 [Active*]
- IETF RFC 6920 [Active*]