RFC 2673: Binary Labels in the Domain Name System
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6891.
Current document in this lineage: RFC 6891 — Extension Mechanisms for DNS (EDNS(0))
In plain English — editorial summary, not part of the RFC
This document defines a "Bit-String Label" which may appear within domain names. This new label type compactly represents a sequence of "One-Bit Labels" and enables resource records to be stored at any bit- boundary in a binary-named section of the domain name tree. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2673
- Published
- August 1999
- Authors
- M. Crawford
- Status
- HISTORIC
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2671 (1999)
- RFC 2673 (1999)
- RFC 6891 (2013) ✓
Read the full history of Extension Mechanisms for DNS (EDNS(0)) →
Referenced by
3 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.
- RFC 2931DNS Request and Transaction Signatures ( SIG(0)s )Current
September 2000
- RFC 2672Non-Terminal DNS Name RedirectionObsoleted
August 1999
- RFC 2874DNS Extensions to Support IPv6 Address Aggregation and RenumberingUpdated
July 2000
- RFC 2930Secret Key Establishment for DNS (TKEY RR)Updated
September 2000
- RFC 3110RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)Updated
May 2001
- RFC 3123A DNS RR Type for Lists of Address Prefixes (APL RR)Current
June 2001
- RFC 3596DNS Extensions to Support IP Version 6Current
October 2003
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
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?