IETF Logo Mail Archive

Re: Informational RFC-to-be - Internet Registry IP Allocation Guidelines

Kim Hubbard <kimh@internic.net> Fri, 22 March 1996 23:10 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01016; 22 Mar 96 18:10 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01010; 22 Mar 96 18:10 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa11141; 22 Mar 96 18:10 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00983; 22 Mar 96 18:10 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00978; 22 Mar 96 18:10 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa11136; 22 Mar 96 18:10 EST
Received: from ops.internic.net by venera.isi.edu (5.65c/5.61+local-22) id <AA00249>; Fri, 22 Mar 1996 15:10:05 -0800
Received: (kimh@localhost) by ops.internic.net (8.7.4/InterNIC-RS) id SAA07610; Fri, 22 Mar 1996 18:09:45 -0500 (EST)
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kim Hubbard <kimh@internic.net>
Message-Id: <199603222309.SAA07610@ops.internic.net>
Subject: Re: Informational RFC-to-be - Internet Registry IP Allocation Guidelines
To: Scott Bradner <sob@newdev.harvard.edu>
Date: Fri, 22 Mar 1996 18:09:44 -0500
Cc: jkrey@isi.edu, sob@newdev.harvard.edu, iesg@isi.edu, kimh@internic.net, rfc-editor@isi.edu
In-Reply-To: <199603202335.SAA15835@newdev.harvard.edu> from "Scott Bradner" at Mar 20, 96 06:35:28 pm
X-Mailer: ELM [version 2.4 PL24alpha4]
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

>
Scott,

The only concern was that perhaps going the BCP route may take
a little longer than the RFC Info route.  If not than I am fine with BCP.

Thanks,

Kim

> It was reviewed and the wg liked it & wanted it to move
> as a BCP - the authors are a bit less sure
> 
> we should have a rsolution soon
> 
> Scott
>

v2.23.0 | Report a Bug | By Email