Re: Informational RFC-to-be - draft-ietf-uri-url-irp-04.txt

Harald.T.Alvestrand@uninett.no Fri, 22 March 1996 17:39 UTC

Message-Id: <199603221738.AA12858@venera.isi.edu>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Harald.T.Alvestrand@uninett.no
To: Keith Moore <moore@cs.utk.edu>
Cc: rfc-ed@isi.edu, rfc-editor@isi.edu, jak@ckm.ucsf.edu, iesg@isi.edu
Subject: Re: Informational RFC-to-be - draft-ietf-uri-url-irp-04.txt
In-Reply-To: Your message of "Thu, 21 Mar 1996 14:08:50 EST." <199603211908.OAA06266@wilma.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 22 Mar 1996 13:47:34 +0100

Keith, Joyce:
the current rule for new URL formats is that they require standards-track
RFCs. (Rule by fiat from the ADs after URI self-destructed without a
review document).

John Kunze, I see you on the CC list: Is it OK with you and your co-authors
that I issue this as a 4-week Last Call on the IETF list?
I will take your word for it that this draft has had adequate review in the
Z39.50 community and that rough consensus is achieved there, so that only
the IETF community remains to be checked.

           Harald A

Informational RFC-to-be - draft-ietf-uri-url-irp-… rfc-ed
Re: Informational RFC-to-be - draft-ietf-uri-url-… Keith Moore
Re: Informational RFC-to-be - draft-ietf-uri-url-… Harald.T.Alvestrand
Re: Informational RFC-to-be - draft-ietf-uri-url-… John Kunze