Re: Status of publication of ESRO Protocol as an Informational RFC

• To: rfc-ed@ISI.EDU (RFC Editor)
• Subject: Re: Status of publication of ESRO Protocol as an Informational RFC
• From: Mohsen Banan <mohsen@rostam.neda.com>
• Date: Thu, 3 Apr 1997 17:00:30 -0800 (PST)
• Cc: mohsen@rostam.neda.com, Jia-Bing Cheng <JBCheng@attws-hq1.nwest.attws.com>, jim.grams@attws.com, Pean Lim-Neda <pean@rostam.neda.com>
• Content-Length: 1495
• Content-Type: text
• In-Reply-To: <199704032357.AA17887@zephyr.isi.edu>
• References: <199704032357.AA17887@zephyr.isi.edu>

>>>>> On Thu, 3 Apr 1997 15:57:01 -0800, rfc-ed@ISI.EDU (RFC Editor) said:

  RFC-Editor> Moshen--

  RFC-Editor> The IESG requested that your document not be published at this time.
  RFC-Editor> They will be in contact with you after their meeting this coming week
  RFC-Editor> in Memphis.

  RFC-Editor> Sincerely,

  RFC-Editor> Mary Kennedy - USC/ISI
  RFC-Editor> Request for Comments Documents

Can you please let us know generally what the reason for the delay is?

That document has been in the draft directory for more than 60 days
and we have heard no comments about it.

Can you tell us who the IESG contact person is for this Informational
RFC?

Non of the ESRO authors were planning to participate in the Memphis
IETF. But, may be we can participate in the IESG meeting and address
relevant questions and issues over the phone. Of course, I'll be happy
to respond to questions/comments through email as well.

Based on my understanding of the process of Informational RFC
publication (RFC-2026 Sections 4.2.2 & 4.2.3), IESG's review relates
to conflicts of the domain of the document with work that is being
done or is expected to be done, within the IETF community. Is there a
conflict?

Sincerely,

--
	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: Status of publication of ESRO Protocol as an Informational RFC, RFC Editor

Re: Status of publication of ESRO Protocol as an Informational RFC, RFC Editor

• Prev by Date: Re: Status of publication of ESRO Protocol as an Informational RFC
• Next by Date: Unexpected and Unreasonable delays in processing of Informational RFC (ESRO Protocol)
• Prev by thread: Re: Status of publication of ESRO Protocol as an Informational RFC
• Next by thread: Unexpected and Unreasonable delays in processing of Informational RFC (ESRO Protocol)
• Index(es):
  • Date
  • Thread