MS did not really distort "an agreed upon standard," by which I take it you mean RFC1510. RFC1510 has provisions that allow implementors to come up with, require and use their own authorization data extensions. MS did; and they're just not sharing the details.
It's their right, really, though arguably it's not nice, particularly since they're using a protocol that they did not invent in the first place and which fits their security model much better than the old NT domain protocols ever did and so they are benefitting from the fact that others have shared ideas but they are not sharing back. But this isn't kindergarten you know. Cheers, Nico On Fri, Jan 18, 2002 at 04:29:52AM -0800, hot ice wrote: > Hi David > > No offense and nothing personal, and I would be sorry to see this > thread degenerate into an MS vs. non-MS slanging match. I like > MS-products and I have been a Microsoft programmer through and > through. But one thing I don't like about MS, is the way they distort > an agreed upon standard, and throw their weight around to shove it > down others' throats - that is unpleasant. I don't need give you > examples do I? > > BTW Thanks to all who responded. > H/I -- -DISCLAIMER: an automatically appended disclaimer may follow. By posting- -to a public e-mail mailing list I hereby grant permission to distribute- -and copy this message.- Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
