Re: draft-hubbard-registry-guidelines-03.txt

Brian Carpenter CERN-CN <brian@dxcoms.cern.ch> Sun, 21 July 1996 08:35 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06560; 21 Jul 96 4:35 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06556; 21 Jul 96 4:35 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa03774; 21 Jul 96 4:35 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06548; 21 Jul 96 4:35 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06544; 21 Jul 96 4:35 EDT
Received: from dxmint.cern.ch by CNRI.Reston.VA.US id aa03769; 21 Jul 96 4:35 EDT
Received: from dxcoms.cern.ch (dxcoms.cern.ch [137.138.28.176]) by dxmint.cern.ch with SMTP id KAA19529; Sun, 21 Jul 1996 10:35:05 +0200 (MET DST)
Received: by dxcoms.cern.ch; (5.65v3.0/1.1.8.2/28Jul95-0949AM) id AA13047; Sun, 21 Jul 1996 10:35:04 +0200
Message-Id: <9607210835.AA13047@dxcoms.cern.ch>
Subject: Re: draft-hubbard-registry-guidelines-03.txt
To: Jim Browning <jfbb@atmnet.net>
Date: Sun, 21 Jul 1996 10:35:04 +0200
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Brian Carpenter CERN-CN <brian@dxcoms.cern.ch>
Cc: davidc@apnic.net, dfk@ripe.net, kimh@internic.net, markk@internic.net, Postel@isi.edu, cidrd@iepg.org, iesg@CNRI.Reston.VA.US, ietf@CNRI.Reston.VA.US
In-Reply-To: <01BB7662.DCA516E0@jfbb.atmnet.net> from "Jim Browning" at Jul 20, 96 05:42:44 pm
X-Mailer: ELM [version 2.4 PL25]
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Jim,

>--------- Text sent by Jim Browning follows:
> 
...
> > IANA
> >
> > The Internet Assigned Numbers Authority has authority over all number
> > spaces used in the Internet.  This includes Internet Address Space. IANA
> > allocates parts of the Internet address space to regional IRs according
> > to its established needs.
> 
> The source of IANA's authority should be referenced: 
> <draft-ietf-poised95-ietf-orgs-03.txt>, or another more definitive 
> reference if there is one.

see RFC 1601

  Brian Carpenter