Status of publication of ESRO Protocol as an Informational RFC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Status of publication of ESRO Protocol as an Informational RFC
- To: rfc-ed@ISI.EDU
 - Subject: Status of publication of ESRO Protocol as an Informational RFC
 - From: Mohsen Banan <mohsen@rostam.neda.com>
 - Date: Mon, 31 Mar 1997 17:28:47 -0800 (PST)
 - Cc: mohsen@rostam.neda.com, jcheng@airdata.com, Jia-Bing Cheng <JBCheng@attws-hq1.nwest.attws.com>, rfc-editor@ISI.EDU
 - Content-Length: 2042
 - Content-Type: text
 - In-Reply-To: <199701231743.AA10376@zen.isi.edu>
 - References: <199701231743.AA10376@zen.isi.edu>
 
>>>>> On Thu, 23 Jan 1997 09:43:49 -0800, rfc-ed@ISI.EDU said:
  rfc-ed> Mohsen-
  rfc-ed> We have received your RFC-to-be and have placed it in the publication
  rfc-ed> queue. We have forwarded it to the IETF for their review.
  rfc-ed> Sincerely,
  rfc-ed> Mary Kennedy - USC/ISI
  rfc-ed> Request for Comments Documents
Can you please let us know what the status of publication of ESRO
Protocol as an Informational RFC is?
When do you expect to publish it as an RFC?
The initial Submission of this RFC was January 11, 1997.
It was made available in the on-line Internet-Drafts directories 
on Jan 29, 97.
       Title     : AT&T/Neda's Efficient Short Remote Operations (ESRO) 
                   Protocol Specification Version 1.2                      
       Author(s) : M. Banan, M. Taylor, J. Cheng
       Filename  : draft-rfced-info-banan-esro-00.txt
       Pages     : 47
       Date      : 01/29/1997
We have received no feed-back on it since (neither from IETF, nor from
the RFC Editor, nor from anybody else).
My understanding of the publication process based on BCP-9/RFC-2029
"The Internet Standards Process -- Revision 3" Section 4.2.3 is that:
   "... The RFC Editor will wait two weeks after this publication [in
   the I-D directory] for comments before proceeding further. ...."
draft-rfced-info-banan-esro-00.txt has been in the I-D directory for
more then 2 months now.
The Informational designation is intended to provide for timely
publication. That is one of the reasons why we submitted ESRO with
Informational designation.
We would like to refer to ESRO Protocol as an RFC in the near future.
Please let us know how we can help expedite the publication of ESRO as
an Information RFC.
Thank you in advance.
Regards,
--
	Mohsen Banan
        Neda Communications, Inc.               tel: +1-206-644-8026
        17005 S.E. 31st Place                   fax: +1-206-562-9591
        Bellevue, Wa 98008                      E-Mail: mohsen@neda.com
            U.S.A. 				URL: http://www.neda.com/
- Replies
 - Re: Update: Informational RFC Submission Request -- ESRO Protocol, rfc-ed
 - Re: Update: Informational RFC Submission Request -- ESRO Protocol, rfc-ed
 
- Prev by Date: Re: Update: Informational RFC Submission Request -- ESRO Protocol
 - Next by Date: Re: Status of publication of ESRO Protocol as an Informational RFC
 - Prev by thread: Re: Update: Informational RFC Submission Request -- ESRO Protocol
 - Next by thread: Re: Status of publication of ESRO Protocol as an Informational RFC
 - Index(es):
 

