Browse Prior Art Database

Distributed system for Internet name service (RFC0830)

IP.com Disclosure Number: IPCOM000004296D
Original Publication Date: 1982-Oct-01
Included in the Prior Art Database: 2019-Feb-14
Document File: 18 page(s) / 20K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Z. Su: AUTHOR

Related Documents

10.17487/RFC0830: DOI

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.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group Request for Comments: 830

A Distributed System for Internet Name Service

by Zaw-Sing Su

+-------------------------------------------------------------+ | | | 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. | | | +-------------------------------------------------------------+

October 1982

SRI International 333 Ravenswood Avenue Menlo Park, California 94025

(415) 859-4576

RFC 830 October 1982

A Distributed System for Internet Name Service

1 INTRODUCTION

For many years, the ARPANET Naming Convention "<user>@<host>" has served its user community for its mail system. The substring "<host>" has been used for other user applications such as file transfer (FTP) and terminal access (Telnet). With the advent of network interconnection, this naming convention needs to be generalized to accommodate internetworking. The Internet Naming Convention [1] describes a hierarchical naming structure for serving Internet user applications such as SMTP for electronic mail, FTP and Telnet for file transfer and terminal access. It is an integral part of the network facility generalization to accommodate internetworking.

Realization of Internet Naming Convention requires the establishment of both naming authority and name service. In this document, we propose an architecture for a distributed System for Internet Name Service (SINS). We assume the reader’s familiarity with [1], which describes the Internet Naming Convention.

Internet Name Service provides a network service for name resolution and resource negotiation for the establishment of direct communication between a pair of source and destination application processes. The source application process is assumed to be in possession of the destination name. In order to establish communication, the source application process requests for name service. The SINS resolves the destination name for its network address, and provides negotiation for network resources. Upon completion of successful name service, the source application process provides the destination address to the transport service for establishing direct communication with the destination application process.

2 OVERVIEW

2.1 System Organization

SINS is a distributed system for name service. It logically consists of two parts: the domain name service and the application interface (Figure 1). The domain name service is an application independent network service for the resolution of domain names. This resolution is provided through the cooperation among a set of domain

1

RFC 830 October 1982

name servers (DNSs). With each domain is associated a DNS.* The reader is referred to [2] for the specification of a domain name server. As noted in [1], a domain is an administrative but not necessarily a topological entity. It is represented in the networks by its associate...

Processing...
Loading...