Re: Those "rfced" I-D filenames
Valdis.Kletnieks@vt.edu Mon, 26 February 1996 19:29 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27692; 26 Feb 96 14:29 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27688; 26 Feb 96 14:29 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa13047; 26 Feb 96 14:29 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27647; 26 Feb 96 14:29 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27569; 26 Feb 96 14:27 EST
Received: from black-ice.cc.vt.edu by CNRI.Reston.VA.US id aa12982; 26 Feb 96 14:27 EST
Received: from localhost (valdis@LOCALHOST [127.0.0.1]) by black-ice.cc.vt.edu (8.7.4/8.7.3) with ESMTP id OAA33084; Mon, 26 Feb 1996 14:26:48 -0500
Message-Id: <199602261926.OAA33084@black-ice.cc.vt.edu>
X-Mailer: exmh version 1.6.5 12/8/95
To: Fred Bohle <fab@fab.md.interlink.com>
cc: kasten@ftp.com, randy@psg.com, rfc-editor@isi.edu, ietf@CNRI.Reston.VA.US
Subject: Re: Those "rfced" I-D filenames
In-reply-to: Your message of "Mon, 26 Feb 1996 14:18:04 +0500." <9602261918.AA23975@fab.md.interlink.com>
X-Orig-Sender: ietf-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
References: <9602261918.AA23975@fab.md.interlink.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 26 Feb 1996 14:26:40 -0500
Source-Info: From (or Sender) name not authenticated.
On Mon, 26 Feb 1996 14:18:04 +0500, Fred Bohle said: > What matters is what the IESG says is a standard, not what is issued as an > RFC. Look at all the RFC's issued on April 1 of each year. RFC1098? ;) In any case, Frank Kastenholz has reminded me that said documents can't get onto the standards track without IESG approval, which answers most of my concerns. I'll follow up on the 'poised' list re: my question about discussion archives... /Valdis
- Re: Those "rfced" I-D filenames Ross Finlayson
- Re: Those "rfced" I-D filenames Dorian Kim
- Re: Those "rfced" I-D filenames Randy Bush
- Re: Those "rfced" I-D filenames Dave Barr
- Those "rfced" I-D filenames The RFC Editor
- Re: Those "rfced" I-D filenames D. J. Bernstein
- Re: Those "rfced" I-D filenames Perry E. Metzger
- Re: Those "rfced" I-D filenames Valdis.Kletnieks
- Re: Those "rfced" I-D filenames Greg Minshall
- Re: Those "rfced" I-D filenames Brian Carpenter CERN-CN
- Those "rfced" I-D filenames Gary Scott Malkin
- Re: Those "rfced" I-D filenames Frank Kastenholz
- Re: Those "rfced" I-D filenames Scott W Brim
- Re: Those "rfced" I-D filenames Jon Crowcroft
- re: Those "rfced" I-D filenames Mark Crispin
- Re: Those "rfced" I-D filenames Christian Huitema
- Re: Those "rfced" I-D filenames Valdis.Kletnieks
- Re: Those "rfced" I-D filenames Frank Kastenholz
- Re: Those "rfced" I-D filenames Frank Kastenholz
- Re: Those "rfced" I-D filenames Jon Crowcroft
- Re: Those "rfced" I-D filenames Ned Freed
- Re: Those "rfced" I-D filenames Frank Kastenholz
- Re: Those "rfced" I-D filenames Frank Kastenholz
- Re: Those "rfced" I-D filenames Garrett A. Wollman
- Re: Those "rfced" I-D filenames J. Patrick Narkinsky
- Re: Those "rfced" I-D filenames Frank Kastenholz
- Re: Those "rfced" I-D filenames Valdis.Kletnieks
- Re: Those "rfced" I-D filenames Henning Schulzrinne
- Re: Those "rfced" I-D filenames Fred Bohle