-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 09:56 PM 6/11/2003 -0700, Carl Ellison wrote: >It's also almost exclusively for a closed authorization >infrastructure, rather than an open naming infrastructure. Because of its predominant use in closed, often proprietary systems, standardization is of questionable value. As long as each closed system's vendors (usually 1) agree among themselves on structure format, they're happy. Most of the fielded implementations I have seen would not interoperate with each other, because the vendor took some shortcuts -- following RFC2693 faithfully, but getting creative with the structure (the draft). It worked for them - didn't cause any trouble. - Carl -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQA/AwUBPuitqnPxfjyW5ytxEQIfOQCdH0i9hgUOOdDMmoqX/calR7cjsmUAn1Ox oY/IR2+CmgZlsyvxM9zzaAQx =dWd7 -----END PGP SIGNATURE----- +------------------------------------------------------------------+ |Carl M. Ellison cme@acm.org http://world.std.com/~cme | | PGP: 75C5 1814 C3E3 AAA7 3F31 47B9 73F1 7E3C 96E7 2B71 | +---Officer, arrest that man. He's whistling a copyrighted song.---+