RFC 8467: Padding Policies for Extension Mechanisms for DNS (EDNS(0))
In plain English — editorial summary, not part of the RFC
RFC 7830 specifies the "Padding" option for Extension Mechanisms for DNS (EDNS(0)) but does not specify the actual padding length for specific applications. This memo lists the possible options ("padding policies"), discusses the implications of each option, and provides a recommended (experimental) option.
Document record
- Document ID
- RFC8467
- Published
- October 2018
- Authors
- A. Mayrhofer
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
- RFC 7830The EDNS(0) Padding OptionCurrent
May 2016
- RFC 9109Network Time Protocol Version 4: Port RandomizationCurrent
August 2021
- RFC 9172Bundle Protocol Security (BPSec)Current
January 2022
- RFC 9173Default Security Contexts for Bundle Protocol Security (BPSec)Current
January 2022
- RFC 6618Mobile IPv6 Security Framework Using Transport Layer Security for Communication between the Mobile Node and Home AgentCurrent
May 2012
- RFC 6164Using 127-Bit IPv6 Prefixes on Inter-Router LinksUpdated
April 2011
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?