Internet Draft                				    Bill Manning
May 1996                                                	     ISI 
Expires in six months						     


                  	Rules for the IP4.INT domain
         	      draft-manning-ip4.int-roe-00.txt

Status of this Memo

   This document is an Internet-Draft.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as ``work in progress.''

   To learn the current status of any Internet-Draft, please check the
   ``1id-abstracts.txt'' listing contained in the Internet- Drafts
   Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net
   (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific
   Rim).

Abstract:

   This memo provides for and documents the operation of the IP4.INT
   domain. In addition, it updates RFC 1035 section 3.5[1].

IPV4.INT.

   Creation of this domain was done to provide an alternative to the
   special domain IN-ADDR.ARPA for the registration of gateway location
   and Internet address to host mapping. The intent of this domain is
   to provide an alternative method to perform host address to host name 
   mapping.

   The use of this domain is in accord with RFC 1591[2], since the mapping
   that is done consitutes an database of international significence and
   is in conjunction with the IETF, a recognized standards setting body.

   This part of the domain space is structured according to address, and
   thereby guarantee that the appropriate data can be located without an 
   exhaustive search of the domain space.

   The domain begins at IP4.INT and has a substructure which follows the
   Internet adressing structure. It is expected that there will be native
   support for bit-level delegation in the servers and resolvers to support
   variable length subnets[3].

   Until such support is available, the IP4.INT domain will follow the
   same representation structure and in section 3.5 of RFC 1035.

Security considerations of this memo

   None.

Selected Releated Work

[1] 1035 Domain names - implementation and specification. P.V.
     Mockapetris. Nov-01-1987. (Format: TXT=125626 bytes) (Obsoletes
     RFC0973, RFC0882, RFC0883) (Updated by RFC1101, RFC1183, RFC1348,
     RFC1876)

[2] 1591 Domain Name System Structure and Delegation. J. Postel. March
     1994. (Format: TXT=16481 bytes)

[3] 1878 Variable Length Subnet Table For IPv4. T. Pummill & B. Manning.
     December 1995. (Format: TXT=19414 bytes) (Obsoletes RFC1860)

Authors' Addresses

	Bill Manning
	USC/ISI
	4676 Admiralty Way 
	Marina del Rey, CA. 90292
	+1.310.822.1511
	bmanning@isi.edu