RFC 4949: Internet Security Glossary, Version 2
In plain English — editorial summary, not part of the RFC
This Glossary provides definitions, abbreviations, and explanations of terminology for information system security. The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026). The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4949
- Published
- August 2007
- Authors
- R. Shirey
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 365
- Also known as
- FYI36
- Obsoletes:
- RFC 2828
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5513IANA Considerations for Three Letter AcronymsCurrent
April 2009
- RFC 3504Internet Open Trading Protocol (IOTP) Version 1, ErrataCurrent
March 2003
- RFC 3179Script MIB Extensibility Protocol Version 1.1Current
October 2001
- RFC 3120A URN Namespace for XML.orgCurrent
June 2001
- RFC 3106ECML v1.1: Field Specifications for E-CommerceUpdated
April 2001
- RFC 3076Canonical XML Version 1.0Current
March 2001
- RFC 3075XML-Signature Syntax and ProcessingObsoleted
March 2001
- RFC 2935Internet Open Trading Protocol (IOTP) HTTP SupplementCurrent
September 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?