From: “Perry E. Metzger” <perry@piermont.com>
To: Rick Johnson <rickj@microsoft.com>
Message Hash: e6671a47487a61d706390a5974d67ee94f7e513665e80de966565a09e9536f2c
Message ID: <199510051855.OAA05477@frankenstein.piermont.com>
Reply To: <9510040519.AA05397@netmail2.microsoft.com>
UTC Datetime: 1995-10-05 18:56:37 UTC
Raw Date: Thu, 5 Oct 95 11:56:37 PDT
From: "Perry E. Metzger" <perry@piermont.com>
Date: Thu, 5 Oct 95 11:56:37 PDT
To: Rick Johnson <rickj@microsoft.com>
Subject: Re: Comments on STT Spec Implementation Details
In-Reply-To: <9510040519.AA05397@netmail2.microsoft.com>
Message-ID: <199510051855.OAA05477@frankenstein.piermont.com>
MIME-Version: 1.0
Content-Type: text/plain
Rick Johnson writes:
> We're very interested in feedback and specifics on this. We worked to
> keep _only_ the detail we felt required to implement STT -- the
> language is intentionally terse. However, it is in everyone's best
> interest that the STT spec is completely understood and implementable.
My suggestion, which I made when Microsoft made a presentation at the
IETF meeting in Stockholm and then had the gall to say "oh, no, we
don't intend to publish an internet draft" is that you publish this as
an internet draft and try to shepard it through the IETF's
standardization process. You will, of course, be savaged, but that is
in the interests of everyone, including you.
The belief that companies can make more money by following proprietary
solutions and imposing them on the world as standards is falling
away. It is in Microsoft's interest that the standard that is adopted
for commerce be open, publically discussed at length, and brutally
critiqued. Losing a bit of control in exchange for actually getting
something that works out for you and your customers is in your interest.
Perry
Return to October 1995
Return to “Rick Johnson <rickj@microsoft.com>”