Browse Prior Art Database

Domain name system implementation schedule (RFC0897)

IP.com Disclosure Number: IPCOM000003946D
Original Publication Date: 1984-Feb-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 8 page(s) / 15K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR

Abstract

Status of this Memo

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 20% of the total text.

Network Working Group Jon Postel

Request for Comments: 897 ISI

February 1984

Updates: RFC 881

Domain Name System Implementation Schedule

Status of this Memo

This memo is a policy statement on the implementation of the Domain

Style Naming System in the Internet. This memo is a partial update

of RFC 881. This is an official policy statement of the ICCB and the

DARPA.

The intent of this memo is to detail the schedule for the

implementation for the Domain Style Naming System. The explanation

of how this system works is to be found in the references.

The Current Situation

Simple Names

Hosts in the ARPA research and DDN operational communities are

currently assigned names in a flat or global name space of

character strings. There are some limits on these names. They

must start with a letter, end with a letter or digit and have only

letters or digits or hyphen as interior characters. Case is not

significant.

For example: USC-ISIF

Tables

Every host in the Internet is expected to have a way of

translating the name of any other host into its Internet address.

By and large, the name to address translation is done by looking

up the information in a table of all hosts.

The maintenance of this table is centralized at the Network

Information Center (NIC). Each host is expected to obtain a

current copy of the table on a timely basis.

Interface to the World

A great deal of mail moves between the Internet and other

"systems" that somehow transport mail among computers. This is

currently done by hiding some sort of "other-system" addressing

information in the local-part of the mail address and using a

mail-relay host in the host-part of the mailbox.

RFC 897 February 1984

Domain Implementation Schedule

For example,

OBERST%EDUCOM.MAILNET@MIT-MULTICS

EDMISTON.CIC@CSNET-RELAY

The Future Situation

Hierarchical Names

Because of the growth of the Internet, structured names (or domain

style names) will be used. Each element of the structured name

will be a character string (with the same constraints that

previously applied to the simple names).

For example: F.ISI.USC.ARPA

Servers

Every host in the Internet will be expected to have a way of

translating the name of any other host into its Internet address.

By and large, the name to address translation will be done by

interacting with a service. There will be a number of servers

that each hold a portion of the name to address information.

The maintenance of the translation data will be subdivided and

distributed.

There are several stages of implementation for the servers and

several levels of development for use...