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

Scott Bradner <sob@newdev.harvard.edu> Wed, 20 March 1996 23:41 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00961; 20 Mar 96 18:41 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00956; 20 Mar 96 18:41 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa15670; 20 Mar 96 18:41 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00949; 20 Mar 96 18:41 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00945; 20 Mar 96 18:41 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa15664; 20 Mar 96 18:41 EST
Received: from newdev.harvard.edu by venera.isi.edu (5.65c/5.61+local-22) id <AA07514>; Wed, 20 Mar 1996 15:37:35 -0800
Received: (from sob@localhost) by newdev.harvard.edu (8.6.9/8.6.9-MT2.02) id SAA15835; Wed, 20 Mar 1996 18:35:28 -0500 (EST)
Date: Wed, 20 Mar 1996 18:35:28 -0500
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Scott Bradner <sob@newdev.harvard.edu>
Message-Id: <199603202335.SAA15835@newdev.harvard.edu>
To: jkrey@isi.edu, sob@newdev.harvard.edu
Subject: Re: Informational RFC-to-be - Internet Registry IP Allocation Guidelines
Cc: iesg@isi.edu, kimh@internic.net, rfc-editor@isi.edu

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