Re: what is the status of the SSL informational RFC I sent you?
John C Klensin <klensin@mail1.reston.mci.net> Fri, 17 March 1995 19:14 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06875; 17 Mar 95 14:14 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06871; 17 Mar 95 14:14 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa14099; 17 Mar 95 14:14 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06864; 17 Mar 95 14:14 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06855; 17 Mar 95 14:14 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa14089; 17 Mar 95 14:14 EST
Received: from mail1.Reston.mci.net by venera.isi.edu (5.65c/5.61+local-21) id <AA19751>; Fri, 17 Mar 1995 11:14:37 -0800
Received: from jck.reston.mci.net (jck2.Reston.mci.net) by MAIL1.RESTON.MCI.NET (PMDF V4.3-10 #8388) id <01HO8UGSRBSW000C01@MAIL1.RESTON.MCI.NET>; Fri, 17 Mar 1995 14:14:38 -0500 (EST)
Date: Fri, 17 Mar 1995 14:14:01 -0500
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John C Klensin <klensin@mail1.reston.mci.net>
Subject: Re: what is the status of the SSL informational RFC I sent you?
X-Sender: klensin@mail1.reston.mci.net (Unverified)
To: Steve Coya <scoya@CNRI.Reston.VA.US>, "Jeffrey I. Schiller" <jis@mit.edu>
Cc: iesg@isi.edu, rfc-editor@isi.edu
Message-Id: <01HO8UGVR54M000C01@MAIL1.RESTON.MCI.NET>
X-Envelope-To: iesg@isi.edu, rfc-editor@isi.edu
Mime-Version: 1.0
X-Mailer: Windows Eudora Version 2.0.3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
>The IESG has the option of adding text to the cover/front page of an RFC. Not a solution. These folks will, as others have, claim RFC=Standard to a lot of people who won't have any idea how to fetch the RFC, much less read it. If we warn them off from an "RFC=Standard" claim, they will claim that RFC publication is the first step on their clear path to Internet Standard. We can't stop them from telling that story, it is their opinion against ours. And these folks have the proven ability to post a copy of the RFC on their Web page "for convenient reference" with the bothersome text stripped out "for user convenience". john
- what is the status of the SSL informational RFC I… jkrey
- Re: what is the status of the SSL informational R… Jeffrey I. Schiller
- Re: what is the status of the SSL informational R… IETF NM-AD
- Re: what is the status of the SSL informational R… Steve Coya
- Re: what is the status of the SSL informational R… Paul Mockapetris
- Re: what is the status of the SSL informational R… IETF NM-AD
- Re: what is the status of the SSL informational R… John C Klensin
- Re: what is the status of the SSL informational R… John C Klensin
- Re: what is the status of the SSL informational R… IESG Secretary