Distributed system for Internet name service
Metadata
- Publisher
- IETF
- Doc Type
- Specification
- Pages
- 18
- Abstract
- This RFC proposes a distributed name service for DARPA Internet. Its purpose is to focus discussion on the subject. It is hoped that a general consensus will emerge leading eventually to the adoption of standards.
- Publication Date
- 1982-10-01
- Status Note
- Unknown
- DOI
10.17487/RFC830- Link
- https://doi.org/10.17487/RFC830
- Author(s)
- Z. Su
Latest version of IETF RFC 830
Document Versions — IETF RFC 830
-
▶ IETF RFC 830 (1982-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Postel, J., "Domains Name Server," RFC XXX, USC/Information Sciences Institute (to appear). EXTERNAL
- IETF RFC 790 [Superseded*]
- IETF RFC 819 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC830.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 830, Distributed system for Internet name service. Available at https://doi.org/10.17487/RFC830
Snippet:
IETF RFC 830, Distributed system for Internet name service. Available at https://doi.org/10.17487/RFC830
HTML (ISO 690 compliant)
Preview:
IETF RFC 830, Distributed system for Internet name service. Available at https://doi.org/10.17487/RFC830
Snippet:
<span class="citation"><cite>IETF RFC 830</cite>, Distributed system for Internet name service. Available at <a href="https://doi.org/10.17487/RFC830" target="_blank" rel="noopener">https://doi.org/10.17487/RFC830</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 830, Distributed system for Internet name service
doi: 10.17487/RFC830
url: https://doi.org/10.17487/RFC830
doi: 10.17487/RFC830
url: https://doi.org/10.17487/RFC830
Snippet:
<li> <cite id="bib-rfc830">IETF RFC 830</cite>, Distributed system for Internet name service <span class="doi">10.17487/RFC830</span> </li>
Referenced By
- IETF RFC 1034 [Active*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 3467 [Active*]
- IETF RFC 882 [Superseded*]
- IETF RFC 883 [Superseded*]