| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| terms [2025/05/07 23:38] – sginoza | terms [2026/02/12 05:44] (current) – external edit 127.0.0.1 |
|---|
| The list highlights terms that were frequently inconsistent and the decisions the RFC Production made regarding consistency, often after discussion with authors and/or working group chairs. | The list highlights terms that were frequently inconsistent and the decisions the RFC Production made regarding consistency, often after discussion with authors and/or working group chairs. |
| |
| | |
| * 'Acknowledgments' vs. 'Acknowledgements' | |< 100% - 75% >| |
| * If consistent (with or without the "e"), leave it. | ^ Term ^ Notes ^ |
| * If inconsistent, delete the "e". | | Acknowledgments and Acknowledgements |If consistent (with or without the "e"), leave it. If inconsistent, delete the "e". | |
| | | ASCII | Not 'US-ASCII' | |
| | | Autonomous System (AS) | Plural is 'Autonomous Systems (ASes)' | |
| * 'ASCII' (not 'US-ASCII') | | demultiplexer | As used in recent RFCs (not 'demultiplexor') | |
| | | Diffserv | Consistent with RFC titles except RFC 4594 (not 'DiffServ')| |
| * 'Autonomous System (AS)': plural is 'Autonomous Systems (ASes)' | | email | Per common use and as primary entry in various dictionaries\\ (not 'e-mail' or 'Email' or 'E-mail', etc.)| |
| | | I-D | Long-standing abbreviation (see [[https://www.rfc-editor.org/rfc/rfc4677.html|RFC 4677]])\\ I-D and Internet-Draft - with hyphen (not 'ID') | |
| * 'demultiplexer' (not 'demultiplexor') | | Internet | Capitalized when referring to the global IP-based Internet | |
| * Note: Consistent with RFC titles except RFC 4594 | | IPsec | Not 'IPSEC' or 'IPSec' | |
| | | multihomed and multihoming | Per more common use in RFCs (multi-homed or multi-homing) | |
| * 'email' (not 'e-mail' or 'Email' or 'E-mail', etc.) | | online | No space or hyphen (not 'on-line') | |
| * as it appears in media type registration template:\\ "Person & email address to contact for further information:" | | pseudowire | No space or hyphen (see RFCs [[https://www.rfc-editor.org/rfc/rfc4385.html|4385]], [[https://www.rfc-editor.org/rfc/rfc4618.html|4618]], [[https://www.rfc-editor.org/rfc/rfc4619.html|4619]], and [[https://www.rfc-editor.org/rfc/rfc4447.html|4447]]) \\ Google shows this to be the most common usage.\\ Exception: quoted titles of previously published documents. | |
| | | public key | No hyphen in attributive position; consistent with PKIX documents and [[https://www.rfc-editor.org/rfc/rfc4253.html|RFC 4253]] | |
| * 'I-D' (not 'ID') - long-standing abbreviation (see [[https://www.rfc-editor.org/rfc/rfc4677.html|RFC 4677]]) | | qubit | No hyphen | |
| * I-D - with hyphen | | subdomain | No hyphen | |
| * Internet-Draft - with hyphen | | suboptions | No hyphen, except with referring to IANA registries, where used with a hyphen. | |
| | | TEXTUAL-CONVENTION | Within ASN.1 of a MIB, 'TEXTUAL-CONVENTION' is used. However, in general text, it is more correct to use 'Textual Convention'.\\ For example, see RFCs [[https://www.rfc-editor.org/rfc/rfc3811.html|3811]], [[https://www.rfc-editor.org/rfc/rfc3812.html|3812]], [[https://www.rfc-editor.org/rfc/rfc3813.html|3813]], [[https://www.rfc-editor.org/rfc/rfc3814.html|3814]], and [[https://www.rfc-editor.org/rfc/rfc3815.html|3815]] | |
| * Internet (capitalized when referring to the global IP-based Internet) | | timestamp | More frequent in RFCs 4000+ (not 'time-stamp') | |
| | |
| * 'IPsec' (not 'IPSEC' or 'IPSec', etc.) | |
| | |
| * 'online' (not 'on-line' -- no space or hyphen) | |
| | |
| * 'pseudowire' (no space or hyphen) | |
| * See RFCs [[https://www.rfc-editor.org/rfc/rfc4385.html|4385]], [[https://www.rfc-editor.org/rfc/rfc4618.html|4618]], [[https://www.rfc-editor.org/rfc/rfc4619.html|4619]], and [[https://www.rfc-editor.org/rfc/rfc4447.html|4447]]. | |
| * Google shows this to be the most common usage. | |
| * Exception: quoted titles of previously published documents. | |
| | |
| * 'public key' (no hyphen in attributive position) | |
| * consistent with PKIX documents and [[https://www.rfc-editor.org/rfc/rfc4253.html|RFC 4253]] | |
| | |
| * 'subdomain' (no hyphen) | |
| | |
| * 'suboptions' (no hyphen) | |
| * Except with referring to IANA registries, where used with a hyphen. | |
| | |
| * 'TEXTUAL-CONVENTION' - e.g., RFCs [[https://www.rfc-editor.org/rfc/rfc3811.html|3811]], [[https://www.rfc-editor.org/rfc/rfc3812.html|3812]], [[https://www.rfc-editor.org/rfc/rfc3813.html|3813]], [[https://www.rfc-editor.org/rfc/rfc3814.html|3814]], and [[https://www.rfc-editor.org/rfc/rfc3815.html|3815]] | |
| * Within ASN.1 of a MIB, 'TEXTUAL-CONVENTION' is used. However, in general text, it is more correct to use 'Textual Convention'. | |
| | |
| | |
| * 'timestamp' (not 'time-stamp') | |
| * More frequent in RFCs 4000+ | |
| |
