RFC 1348: DNS NSAP RRs
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1637.
Current document in this lineage: RFC 1706 — DNS NSAP Resource Records
In plain English — editorial summary, not part of the RFC
This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1348
- Published
- July 1992
- Authors
- B. Manning
- Status
- EXPERIMENTAL
- Stream
- Legacy
- Area
- —
- Pages
- 4
- Also known as
- —
- Obsoleted by:
- RFC 1637
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1348 (1992)
- RFC 1637 (1994)
- RFC 1706 (1994) ✓
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 1574Essential Tools for the OSI InternetCurrent
February 1994
- RFC 1629Guidelines for OSI NSAP Allocation in the InternetCurrent
May 1994
- RFC 2671Extension Mechanisms for DNS (EDNS0)Obsoleted
August 1999
- RFC 2672Non-Terminal DNS Name RedirectionObsoleted
August 1999
- RFC 2870Root Name Server Operational RequirementsObsoleted
June 2000
- RFC 2929Domain Name System (DNS) IANA ConsiderationsObsoleted
September 2000
- RFC 3110RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)Updated
May 2001
- RFC 3364Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6)Current
August 2002
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?