CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 08:44:35 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=IK5K6eFyfQtV86iwqysgWmV2M.1OtUZqfWJ0xC2wMxw-1759999475-1.0.1.1-7C9O3MMtCRh87c9yvCXJi23P.lhQdwr3o9sZ8uo5tlQRsxRe5P1tRCrwQXfFaGGfd2xQNlD3TC5ZSNuoC4wB1LIo6.YqW5UPSYxl.8ZjfDg; path=/; expires=Thu, 09-Oct-25 09:14:35 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bc98cd3a12f473-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 7830 » RFC Editor
Search RFCs
RFC 7830
The EDNS(0) Padding Option, May 2016
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7830
Discuss this RFC: Send questions or comments to the mailing list dns-privacy@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7830
Abstract
This document specifies the EDNS(0) "Padding" option, which allows DNS clients and servers to pad request and response messages by a variable number of octets.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us