Re: ESRO ID

• To: Scott Bradner <sob@harvard.edu>
• Subject: Re: ESRO ID
• From: Mohsen Banan <mohsen@neda.com>
• Date: Fri, 8 Aug 1997 15:19:37 -0700 (PDT)
• Cc: allyn@eng.sun.com, iesg-secretary@ietf.org, JBCheng@attws-hq1.nwest.attws.com, mtaylor@teledesic.com, pean@neda.com, Mohsen Banan-neda <mohsen@neda.com>
• Content-Length: -873
• Content-Type: text/plain; charset=US-ASCII
• In-Reply-To: <199708082046.QAA01197@newdev.harvard.edu>
• References: <199708082046.QAA01197@newdev.harvard.edu>

>>>>> On Fri, 8 Aug 1997 16:46:35 -0400 (EDT), Scott Bradner <sob@harvard.edu> said:

  Mohsen> --
  Mohsen> The urgency for publication in this case outweighs our interest in
  Mohsen> getting this document on the standards track.
  Mohsen> --

  Scott> for my information, what is causing this feeling of urgency?

For the past several months we have been telling our partners and
customers that the protocols our products use will soon be available
via the Informational RFC mechanism. Our credibility goes down as time
go by ...

Our business strategy hinges on the openness of our solution which in
turn hinges on the availability of ESRO protocol specification as an
RFC. The absence of the RFC is delaying our marketing efforts.

Other closed efficient transports for wireless applications exist.
The value of an open alternative declines as time goes by ...


...Mohsen.

Replies

Re: ESRO ID, Scott Bradner

Re: ESRO ID, Scott Bradner

• Prev by Date: Re: ESRO ID
• Next by Date: Re: ESRO ID
• Prev by thread: Re: ESRO ID
• Next by thread: Re: ESRO ID
• Index(es):
  • Date
  • Thread