Explicit Forged Answer Signal
draft-pan-dnsop-explicit-forged-answer-signal-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Author | Pan Lanlan | ||
| Last updated | 2024-07-23 (Latest revision 2024-01-10) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes that recursive resolver should give explict signal in the forged answer. Client could react more clearly based on the explict forged answer signal, to protect user on security and privacy.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)