RFC 4228: Requirements for an IETF Draft Submission Toolset
In plain English — editorial summary, not part of the RFC
This document specifies requirements for an IETF toolset to facilitate Internet-Draft submission, validation, and posting. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4228
- Published
- December 2005
- Authors
- A. Rousskov
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6778Requirements for Archiving IETF Email Lists and for Providing Web-Based Browsing and SearchingCurrent
October 2012
- RFC 7203An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity InformationCurrent
April 2014
- RFC 8512A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)Current
January 2019
- RFC 8676YANG Modules for IPv4-in-IPv6 Address plus Port (A+P) SoftwiresCurrent
November 2019
- RFC 8768Constrained Application Protocol (CoAP) Hop-Limit OptionCurrent
March 2020
- RFC 8782Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel SpecificationObsoleted
May 2020
- RFC 8783Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel SpecificationCurrent
May 2020
- RFC 8969A Framework for Automating Service and Network Management with YANGCurrent
January 2021
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?