BCP 32
Subscribe to BCP 32
Get notified when:
- An RFC is added to or removed from this BCP
- A RFC within the collection changes status, obsoleted by, updates, updated by, or subseries.
BCPs are stable identifiers for Best Current Practices. A BCP may consist of a single RFC or a group of RFCs related to a specific IETF process or recommended guidelines. The collection may become empty as the BCP evolves.
RFC 2606: BCP 32: Reserved Top Level DNS Names
- D. Eastlake 3rd
- A. Panitz
- June 1999
- IETF publication
- Internet Area
Abstract
To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Abstract
To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.