RFC 1788: ICMP Domain Name Messages
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6918.
Current version: RFC 6918 — Formally Deprecating Some ICMPv4 Message Types
In plain English — editorial summary, not part of the RFC
This document specifies ICMP messages for learning the Fully Qualified Domain Name associated with an IP address. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1788
- Published
- April 1995
- Authors
- W. Simpson
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 6918
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 7915IP/ICMP Translation AlgorithmCurrent
June 2016
- RFC 1858Security Considerations for IP Fragment FilteringUpdated
October 1995
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 1996
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 1997
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?