RFC1816 on U.S. Government Internet Domain Names

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 03 August 1995 19:00 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23115; 3 Aug 95 15:00 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa21866; 3 Aug 95 15:00 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23082; 3 Aug 95 15:00 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21987; 3 Aug 95 14:53 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa21720; 3 Aug 95 14:53 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA20660>; Thu, 3 Aug 1995 11:55:09 -0700
Message-Id: <199508031855.AA20660@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1816 on U.S. Government Internet Domain Names
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 03 Aug 1995 11:57:04 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1816:

        Title:      U.S. Government Internet Domain Names
        Author:     Federal Networking Council
        Date:       August 1995
        Mailbox:    execdir@fnc.gov
        Pages:      8
        Characters: 17,979
        Obsoletes:  1811

        URL:        ftp://ds.internic.net/rfc/rfc1816.txt


This memo provides an update and clarification to RFC 1811.  This
document describes the registration policies for the top-level domain
".GOV".  Thus far, Federal Agencies and their subsidiaries have
registered without any guidance.  This has resulted in multiple
registrations for Federal Agencies and naming schemes that do not
facilitate responsiveness to the public.  This document fixes this by
restricting registrations to coincide with the approved structure of
the US government.  The document cited, FIPS 95-1, provides a standard
recognized structure into which domain registrations for .GOV can be
fit.  This policy is exactly comparable to that for the top-level
domains.  The IANA requires that an organization/country apply for and
get a 2 letter code from ISO/ITU (e.g., US for United States) for
additional top-level registration.  As a side effect, this reduces the
number of .GOV level registrations and reduces the workload on the
Internic.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ds.internic.net/rfc/rfc1816.txt"><ftp://ds.internic.net/rfc/rfc1816.txt>