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 aa06848; 17 Mar 95 14:14 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06844; 17 Mar 95 14:14 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa14083; 17 Mar 95 14:14 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06837; 17 Mar 95 14:14 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06833; 17 Mar 95 14:13 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa14073; 17 Mar 95 14:13 EST
Received: from mail1.Reston.mci.net by venera.isi.edu (5.65c/5.61+local-21) id <AA19737>; Fri, 17 Mar 1995 11:14:29 -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:35 -0500 (EST)
Date: Fri, 17 Mar 1995 14:13:58 -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: "Jeffrey I. Schiller" <jis@mit.edu>, jkrey@isi.edu
Cc: iesg@isi.edu, rfc-editor@isi.edu
Message-Id: <01HO8UGTOBGM000C01@MAIL1.RESTON.MCI.NET>
X-Envelope-To: iesg@isi.edu, jkrey@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
>At 11:48 3/16/95, jkrey@isi.edu wrote: >>IESG: >> >>What is going on? Publish one version as "informational" and >>a later version as ... ???? I agree with Jeff. There are a couple of other things afoot here, including rumours about trying to round up all major NetScape server users to publically endorse the protocol as the right/best solution for Internet security, that point in this direction. Right-to-publish should no more extend to deliberate attempts to subvert the system than freedom of speech extends to yelling "fire" in the proverbial crowded theatre. 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