RFC 7749: The "xml2rfc" Version 2 Vocabulary
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7991.
Current document in this lineage: RFC 7991 — The "xml2rfc" Version 3 Vocabulary
In plain English — editorial summary, not part of the RFC
This document defines the "xml2rfc" version 2 vocabulary: an XML-based language used for writing RFCs and Internet-Drafts. Version 2 represents the state of the vocabulary (as implemented by several tools and as used by the RFC Editor) around 2014. This document obsoletes RFC 2629.
Document record
- Document ID
- RFC7749
- Published
- February 2016
- Authors
- J. Reschke
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 76
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2629 (1999)
- RFC 7749 (2016)
- RFC 7991 (2016) ✓
Read the full history of The "xml2rfc" Version 3 Vocabulary →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7221Handling of Internet-Drafts by IETF Working GroupsCurrent
April 2014
- RFC 7994Requirements for Plain-Text RFCsUpdated
December 2016
- RFC 7996SVG Drawings for RFCs: SVG 1.2 RFCObsoleted
December 2016
- RFC 3975OMA-IETF Standardization CollaborationCurrent
February 2005
- RFC 3677IETF ISOC Board of Trustee Appointment ProceduresCurrent
December 2003
- RFC 3552Guidelines for Writing RFC Text on Security ConsiderationsUpdated
July 2003
- RFC 2860Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers AuthorityCurrent
June 2000
- RFC 2850Charter of the Internet Architecture Board (IAB)Updated
May 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?