Re: IESG Comment on SSL

Steve Coya <scoya@CNRI.Reston.VA.US> Sun, 26 March 1995 17:05 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04015; 26 Mar 95 12:05 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04011; 26 Mar 95 12:05 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07165; 26 Mar 95 12:05 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04004; 26 Mar 95 12:05 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04000; 26 Mar 95 12:05 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa07160; 26 Mar 95 12:05 EST
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa03994; 26 Mar 95 12:05 EST
To: John C Klensin <klensin@mail1.reston.mci.net>
cc: iesg@CNRI.Reston.VA.US
Subject: Re: IESG Comment on SSL
In-reply-to: Your message of "Fri, 24 Mar 95 09:06:53 EST." <01HOIBRZPZUA000KEK@MAIL1.RESTON.MCI.NET>
Date: Sun, 26 Mar 95 12:05:36 -0500
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Coya <scoya@CNRI.Reston.VA.US>
Message-ID: <9503261205.aa03994@IETF.CNRI.Reston.VA.US>

John,

>> I think the first step in dealing with this -- unless the RFC Editor
>> has heard from NetScape post- the Jeff and Jeff discussion, is for our
>> Jeff to send a note to their Jeff, copying the RFC Editor, indicating
>> that he assumes from the conversation that the request to publish as an
>> Info RFC is withdrawn, pointing to 1id-guidelines.txt, and asking if
>> NetScape needs any help with the I-D formatting and submission
>> process.

I will modify the note to the RFC Editors to reflect this approach. In
fact, I'll start on it right after I post this message. The key is to
make sure the RFC Editors know that if they publish SSL as an
Informational/experimental document, the IESG will want to include
text.


Steve



Steve