metasystema.org
ObsoletedEXPERIMENTALIETF stream

RFC 2168: Resolution of Uniform Resource Identifiers using the Domain Name System

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3401, RFC 3402, RFC 3403, RFC 3404.

Current document in this lineage: RFC 3401 — Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS; RFC 3402 — Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm; RFC 3403 — Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database; RFC 3404 — Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)

In plain English — editorial summary, not part of the RFC

The requirements document for URN resolution systems defines the concept of a "resolver discovery service". This document describes the first, experimental, RDS. It is implemented by a new DNS Resource Record, NAPTR (Naming Authority PoinTeR), that provides rules for mapping parts of URIs to domain names. This memo defines an Experimental Protocol for the Internet community.

Document record

Document ID
RFC2168
Published
June 1997
Authors
R. Daniel; M. Mealling
Status
EXPERIMENTAL
Stream
IETF
Area
app
Pages
20
Also known as
—
Obsoleted by:
RFC 3401, RFC 3402, RFC 3403, RFC 3404
Updated by:
RFC 2915

Standards lineage

This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.

  1. RFC 2168 (1997)
  2. RFC 2915 (2000)
  3. RFC 3401 (2002)
  4. RFC 3402 (2002)
  5. RFC 3403 (2002)
  6. RFC 3404 (2002) ✓

Read the full history of Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) →

Referenced by

5 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/2168-resolution-of-uniform-resource-identifiers-using-the-domain-name-system