[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unexpected and Unreasonable delays in processing of Informational RFC (ESRO Protocol)
Steve:
Can you please look into this situation?
Thanks,
Mary Kennedy
Request for Comments Documents
-------------------------------------
> From mohsen@xxxxxxxxxxxxxxxx Tue Jul 29 00:02:17 1997
> Date: Mon, 28 Jul 1997 23:58:46 -0700 (PDT)
> Mime-Version: 1.0
> From: Mohsen Banan <mohsen@xxxxxxxx>
> To: rfc-editor@xxxxxxx, rfc-ed@xxxxxxx, Jon Postel <postel@xxxxxxx>
> Cc: "Mark S. Taylor" <mtaylor@xxxxxxxxxxxxx>,
> Jia-Bing Cheng <JBCheng@xxxxxxxxxxxxxxxxxxxxxxxxx>,
> Pean Lim-Neda <pean@xxxxxxxx>, Mohsen Banan-neda <mohsen@xxxxxxxx>
> Subject: Unexpected and Unreasonable delays in processing of Informational RFC (ESRO Protocol)
> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid
> Content-Type> : > text/plain> ; > charset=US-ASCII>
> Content-Length: 18230
>
>
>
> More than 6 month ago we submitted the ESRO protcol for publication as
> an Informational RFC. It has not been published yet. Our requests to
> find out what the reason for the delays are, remain unanswered.
>
> This is unreasonable!
>
> We expect to see the ESRO protocol published as an Informational RFC as
> soon as possible.
>
>
>
> More than 6 months ago (on 1/11/97) Mark Taylor (then of AT&T)
> submitted the ESRO protocol for publication as an Informational RFC.
> (Message-Id: <32D7FFCA@xxxxxxxxxxxxxxxxxxxxxxxxxxx>)
>
> Shortly after that (on 1/15/97) I incorporated IANA's port assignment
> for the ESRO protocol and resubmitted it to the RFC-Editor.
> (Message-Id: <199701160714.XAA29795@xxxxxxxxxxxxxxxx>)
>
> On January 23rd, the RFC editor acknowledged receipt and placed
> it in the publication queue and forwarded it to the IETF for their review.
> (Message-Id: <199701231743.AA10376@xxxxxxxxxxx>)
>
> The ESRO protocol was put in the internet drafts directory on January
> 29th. (Message-Id: <9701300942.aa02647@xxxxxxxx>)
>
> On March 31st I checked on the current status of this RFC and
> expressed our desire to see it published
> soon. (<199704010128.RAA26066@xxxxxxxxxxxxxxxx>)
>
> On April 3th we were told that The IESG had requested that the ESRO
> document not be published at this time and that they would be in
> contact with us after their meeting that coming week in Memphis.
> (Message-Id: <199704032357.AA17887@xxxxxxxxxxxxxx>)
>
> I immediately replied requesting an explanation of this delay and the
> name of the relevant IESG contact person. I again offered to discuss
> and respond to questions/comments regarding the ESRO protocol.
> (Message-Id: <199704040100.RAA07041@xxxxxxxxxxxxxxxx>)
>
> The above mentioned 7 messages are attached to the end of this
> message.
>
> Since April 3rd, we have not heard back from the RFC-Editor or the
> IESG regarding this Informational RFC.
>
> The Informational designation is intended to provide for timely
> publication. That is one of the reasons why we submitted ESRO with
> Informational designation.
>
> Considering that there has been adequate time (nearly 6 months) for
> the RFC Editor, the IESG, the IETF and the technical Internet
> community at large to review and comment on this document and that
> there has been no comments, again I request that the document be
> promptly published as an Informational RFC.
>
> It is my understanding that it is the responsibility of the RFC Editor
> to over see publication of Informational RFC according to the process
> described in BCP-9/RFC-2026 in a timely manner. It is unreasonable and
> unprofessional for IESG (or anybody else) to delay publication of an
> Informational RFC without providing any reason or explanation. I don't
> understand the reason for the RFC Editor and the IESG's failure of
> following the process defined for publication of Informational RFCs in
> the case of this document.
>
> We have done a significant amount of work on the specification and
> implementation of this useful protocol. We want to make it easy for
> others who wish to implement this protocol to access this document.
> Publication of this document as an Informational RFC accomplishes
> that.
>
> To the best of our knowledge there is nothing in the document that
> proposes something that conflicts with, or is actually inimical to, an
> established IETF effort.
>
>
> In short, this document has been in the queue for publication long
> enough. There has been ample time for through reviews. Since there has
> been no comments, I insist that RFC Editor publish it as an
> Informational RFC without any further delay.
>
> 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@xxxxxxxx
> U.S.A. URL: http://www.neda.com/
>
>
> ------- start of digest (7 messages) (RFC 934 encapsulation) -------
> From: Mark Taylor <mtaylor@xxxxxxxxxxx> To: rfc editor
> <rfc-editor@xxxxxxx> Cc: JiaBing Cheng <jcheng@xxxxxxxxxxx>,
> "Jim Grams (Corporate)" <jim.grams@xxxxxxxxx>,
> mst <mark.taylor@xxxxxxxxxxx>,
> "'Mohsen Banan (Neda)'" <mohsen@xxxxxxxxxxxxxxx>,
> "'Murat Divringi (Neda)'" <muratd@xxxxxxxxxxxxxxx>
> Subject: Informational RFC Submission Request -- ESRO Protocol
> Date: Sat, 11 Jan 97 13:00:00 PST
> Message-Id: <32D7FFCA@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>
>
> Please accept this informational RFC for Efficient Short Remote Operations
> (ESRO), a protocol we have developed over the past two years. In this
> context, "we" refers to AT&T Wireless Services, Inc., and Neda
> Communications, Inc. (under contract to AT&T). I am the Director of
> Strategic Engineering in the Wireless Data Division of AT&T Wireless
> Services.
>
> The purpose of the ESRO protocol is to better support applications such as
> Email over low-bandwidth media, such as Cellular Digital Packet Data or
> other wireless services. The editor for this informational RFC is Mohsen
> Banan, of Neda Communications (who can be reached at mohsen@xxxxxxxx).
>
> We have requested a port number assignment from IANA for this protocol on
> January 9, 1997; the RFC editor was sent a copy of this request. Following
> the assignment of a port number, section 4.6.3 will require a corresponding
> modification. Mr. Banan can provide a LaTeX-revisable version of this RFC.
>
> Please direct all future correspondence regarding this RFC to Mr. Banan at
> mohsen@xxxxxxxx with a courtesy copy to Mr. Jia-bing Cheng of AT&T at
> jcheng@xxxxxxxxxxxx Thank-you in advance for your assistance in the
> publication of this RFC.
>
> Regards,
>
> Mark Taylor
> Director of Strategic Engineering
> AT&T Wireless Services
> 10230 NE Points Dr.
> Kirkland, WA 98033
> mark.taylor@xxxxxxxxxxx
>
> ------The RFC is a text file attached below -------
> [[ ESROS.TXT : 3408 in ESROS.TXT ]]
>
> The following binary file has been uuencoded to ensure successful
> transmission. Use UUDECODE to extract.
>
> begin 600 ESROS.TXT
> ...
>
> end
> ------------------------------
> From: Mohsen Banan <mohsen@xxxxxxxxxxxxxxx>
> To: rfc-editor@xxxxxxx
> Cc: JiaBing Cheng <jcheng@xxxxxxxxxxx>, jim.grams@xxxxxxxxxxx,
> "Mark S. Taylor" <mark.taylor@xxxxxxxxxxx>,
> Murat Divringi-neda <muratd@xxxxxxxxxxxxxxx>,
> Mohsen Banan-neda <mohsen@xxxxxxxxxxxxxxx>
> Subject: Update: Informational RFC Submission Request -- ESRO Protocol
> Date: Wed, 15 Jan 1997 23:14:42 -0800 (PST)
> Message-Id: <199701160714.XAA29795@xxxxxxxxxxxxxxxx>
>
>
> Following through with Mark Taylor's email of January 11, 97, I have
> incorporated IANA's port assignment for the ESRO protocol in section
> 4.6.3. I have also made other minor editorial changes to other
> sections. The attached updated Informational RFC is now ready for your
> review and publication.
>
> If you want to also have the LaTeX revisable form of
> this RFC, please drop me -- Mohsen Banan <mohsen@xxxxxxxx> -- a note.
>
> Let me know if you have any questions or if you want us to modify the
> document in any specific way.
>
> Thank you in advance.
>
> ...Mohsen.
>
>
> - ---
>
>
>
>
>
>
> Network Working Group M. Banan, Neda
> Request for Comments: 2XXX M. Taylor, AWS
> Category: Informational J. Cheng, AWS
> January 1997
>
>
> AT&T/Neda's Efficient Short Remote Operations (ESRO)
> Protocol Specification Version 1.2
>
>
>
>
>
>
> Status of this Memo:
>
> This memo provides information for the Internet community. This memo
> does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
>
> Abstract:
>
> This document specifies the service model, the notation and protocol
> for Efficient Short Remote Operations (ESRO). The ESRO service is
> similar to and is consistent with other Remote Procedure Call
> services. The emphasis of ESRO service definition and the ESRO
> protocol is on efficiency. ESRO is designed specifically with
> wireless network (e.g., CDPD) usage in mind.
>
> ESRO protocol provides reliable connectionless remote operation
>
> ............
>
>
>
> Banan, et. al. Informational [Page 56]
> ------------------------------
> From: rfc-ed@xxxxxxx
> To: mohsen@xxxxxxxxxxxxxxx
> Cc: jcheng@xxxxxxxxxxx, jim.grams@xxxxxxxxxxx, mark.taylor@xxxxxxxxxxx,
> muratd@xxxxxxxxxxxxxxx, rfc-editor@xxxxxxx
> Subject: Re: Update: Informational RFC Submission Request -- ESRO Protocol
> Date: Thu, 23 Jan 1997 09:43:49 -0800
> Message-Id: <199701231743.AA10376@xxxxxxxxxxx>
>
>
> Mohsen-
>
>
> We have received your RFC-to-be and have placed it in the publication
> queue. We have forwarded it to the IETF for their review.
>
> Sincerely,
>
> Mary Kennedy - USC/ISI
> Request for Comments Documents
>
>
> ------------------------------
> From: Internet-Drafts@xxxxxxxx
> Sender: ietf-announce-request@xxxxxxxx
> To: IETF-Announce: ;
> Subject: I-D ACTION:draft-rfced-info-banan-esro-00.txt
> Date: Thu, 30 Jan 1997 09:42:10 -0500
> Message-Id: <9701300942.aa02647@xxxxxxxx>
>
> - --NextPart
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> 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
>
> This document specifies the service model, the notation and protocol for
> Efficient Short Remote Operations (ESRO). The ESRO service is similar to
> and is consistent with other Remote Procedure Call services. The emphasis
> of ESRO service definition and the ESRO protocol is on efficiency. ESRO is
> designed specifically with wireless network (e.g., CDPD) usage in mind.
>
> ESRO protocol provides reliable connectionless remote operation services on
> top of UDP (or any other non-reliable connectionless transport service)
> with minimum overhead. ESRO protocol supports segmentation and reassembly,
> concatenation and separation as well as multiplexing for service users
> (applications).
>
> ESRO allows for trade-offs between efficiency and reliability
> by specifying both 2-way hand-shake and 3-way hand-shake
> based protocols.
>
> Encoding mechanisms for presentation of the parameters of remote
> operations are outside the scope of this document. But,
> identification (tagging) of the encoding mechanism in use (e.g., XDR, BER,
> PER) is supported by ESRO protocol.
>
> A variety of applications can use the ESRO protocol. Some early
> applications using ESRO include efficient short message submission
> and delivery, credit card authorization and white pages lookup.
>
> Internet-Drafts are available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-rfced-info-banan-esro-00.txt".
> A URL for the Internet-Draft is:
> ftp://ds.internic.net/internet-drafts/draft-rfced-info-banan-esro-00.txt
>
> Internet-Drafts directories are located at:
>
> o Africa: ftp.is.co.za
>
> o Europe: ftp.nordu.net
> ftp.nis.garr.it
>
> o Pacific Rim: munnari.oz.au
>
> o US East Coast: ds.internic.net
>
> o US West Coast: ftp.isi.edu
>
> Internet-Drafts are also available by mail.
>
> Send a message to: mailserv@xxxxxxxxxxxxxxxx In the body type:
> "FILE /internet-drafts/draft-rfced-info-banan-esro-00.txt".
>
> NOTE: The mail server at ds.internic.net can return the document in
> MIME-encoded form by using the "mpack" utility. To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command. To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader. Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e., documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version
> of the Internet-Draft.
>
> - --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
>
> - --OtherAccess
> Content-Type: Message/External-body;
> access-type="mail-server";
> server="mailserv@xxxxxxxxxxxxxxx"
>
> Content-Type: text/plain
> Content-ID: <19970129105127.I-D@xxxxxxxx>
>
> ENCODING mime
> FILE /internet-drafts/draft-rfced-info-banan-esro-00.txt
>
> - --OtherAccess
> Content-Type: Message/External-body;
> name="draft-rfced-info-banan-esro-00.txt";
> site="ds.internic.net";
> access-type="anon-ftp";
> directory="internet-drafts"
>
> Content-Type: text/plain
> Content-ID: <19970129105127.I-D@xxxxxxxx>
>
> - --OtherAccess--
>
> - --NextPart--
>
> ------------------------------
> From: Mohsen Banan <mohsen@xxxxxxxxxxxxxxx>
> To: rfc-ed@xxxxxxx
> Cc: mohsen@xxxxxxxxxxxxxxx, jcheng@xxxxxxxxxxx,
> Jia-Bing Cheng <JBCheng@xxxxxxxxxxxxxxxxxxxxxxxxx>, rfc-editor@xxxxxxx
> Subject: Status of publication of ESRO Protocol as an Informational RFC
> Date: Mon, 31 Mar 1997 17:28:47 -0800 (PST)
> Message-Id: <199704010128.RAA26066@xxxxxxxxxxxxxxxx>
>
>
> >>>>> On Thu, 23 Jan 1997 09:43:49 -0800, rfc-ed@xxxxxxx 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@xxxxxxxx
> U.S.A. URL: http://www.neda.com/
>
>
> ------------------------------
> From: rfc-ed@xxxxxxx (RFC Editor)
> To: mohsen@xxxxxxxxxxxxxxx
> Cc: rfc-ed@xxxxxxx
> Subject: Re: Status of publication of ESRO Protocol as an Informational RFC
> Date: Thu, 3 Apr 1997 15:57:01 -0800
> Message-Id: <199704032357.AA17887@xxxxxxxxxxxxxx>
>
>
> Moshen--
>
> The IESG requested that your document not be published at this time.
> They will be in contact with you after their meeting this coming week
> in Memphis.
>
> Sincerely,
>
> Mary Kennedy - USC/ISI
> Request for Comments Documents
>
>
> ------------------------------
> From: Mohsen Banan <mohsen@xxxxxxxxxxxxxxx>
> To: rfc-ed@xxxxxxx (RFC Editor)
> Cc: mohsen@xxxxxxxxxxxxxxx, Jia-Bing Cheng <JBCheng@xxxxxxxxxxxxxxxxxxxxxxxxx>,
> jim.grams@xxxxxxxxx, Pean Lim-Neda <pean@xxxxxxxxxxxxxxx>
> Subject: Re: Status of publication of ESRO Protocol as an Informational RFC
> Date: Thu, 3 Apr 1997 17:00:30 -0800 (PST)
> Message-Id: <199704040100.RAA07041@xxxxxxxxxxxxxxxx>
>
>
> >>>>> On Thu, 3 Apr 1997 15:57:01 -0800, rfc-ed@xxxxxxx (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@xxxxxxxx
> U.S.A. URL: http://www.neda.com/
>
>
> ------- end -------
>
>