| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 22:20:47 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
server: cloudflare
cf-ray: 95f468c918f29dfa-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2931 » RFC Editor
Search RFCs
RFC 2931
DNS Request and Transaction Signatures ( SIG(0)s ), September 2000
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 2535
- Author:
- D. Eastlake 3rd
- Stream:
- IETF
- Source:
- dnsext (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2931
Discuss this RFC: Send questions or comments to the mailing list dnsext@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2931
Abstract
This document describes the minor but non-interoperable changes in Request and Transaction signature resource records ( SIG(0)s ) that implementation experience has deemed necessary. [STANDARDS-TRACK]
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