Re: Informational RFC-to-be: draft-rfced-info-banan-00.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Informational RFC-to-be: draft-rfced-info-banan-00.txt
- To: RFC Editor <rfc-ed@ISI.EDU>
- Subject: Re: Informational RFC-to-be: draft-rfced-info-banan-00.txt
- From: Mohsen BANAN <mohsen@neda.com>
- Date: Thu, 19 Nov 1998 11:18:04 -0800 (PST)
- CC: records@neda.com
- Content-Length: 1857
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: <199811031947.LAA25704@jet.isi.edu>
- References: <199811031947.LAA25704@jet.isi.edu>
>>>>> On Tue, 3 Nov 1998 11:47:09 -0800 (PST), RFC Editor <rfc-ed@ISI.EDU> said:
RFC-Editor> ...
RFC-Editor> Two week timeout is initiated (17 November 1998).
RFC-Editor> ...
Aside from the comments from Keith Moore, I have
not received any other comments related to
draft-rfced-info-banan-00.txt.
While Keith Moore's comments may be relevant and
applicable to a standard's track document, they
do not apply to an Informational/Experimental
RFC. I have already responded to those comments
and am willing to supply you additional
information with respect to any of those
comments.
It is my understanding that
draft-rfced-info-banan-00.txt easily meets and
exceeds the requirements for publication as an
Informational/Experimental RFC because:
- It is extremely relevant to today's Internet
activity.
- Meets the technical standard for RFCs,
because in addition to having gone through
extensive verification steps, it has already
been used to produce independent
interoperable implementations.
- Meets the editorial standard for RFCs.
If the RFC Editor for any reason is considering
not to publish EMSD as an Informational RFC, I
request that you let me know immediately so that
I can either correct the problems or persuade
you of its fitness.
As you know I am quite anxious to see
draft-rfced-info-banan-00.txt progress towards
its publication as an Informational RFC in a
timely manner.
Can you please let me know in what time frame
you expect to publish this Informational RFC?
Respectfully Yours,
--
Mohsen Banan
Neda Communications, Inc. tel: +1-425-644-8026
17005 S.E. 31st Place fax: +1-425-562-9591
Bellevue, Wa 98008 E-Mail: mohsen@neda.com
U.S.A. URL: http://www.neda.com/
- Replies
- Informational RFC-to-be: draft-rfced-info-banan-00.txt, RFC Editor
- Informational RFC-to-be: draft-rfced-info-banan-00.txt, RFC Editor
- Prev by Date: Re: Informational RFC-to-be: draft-rfced-info-banan-00.txt
- Next by Date: Re: Informational RFC-to-bes
- Prev by thread: Re: Informational RFC-to-be: draft-rfced-info-banan-00.txt
- Next by thread: draft-rfced-info-banan-00.txt
- Index(es):





