Bill Parducci asked whether Sun is planning to attest to successfully using XACML 1.0. Yes, we are. Our implementation currently passes all but four of the conformance tests. We expect to pass IIC170 as soon as the "map" vs. "<type>-map" issue is settled, and the remaining 3 as soon as the TC clarifies whether tests IIA002, IIE001, and IIE002 are actually required for conformance and for successfully using. Anne Anderson On 28 November, bill parducci writes: Re: [xacml] FW: ContentGuard IPR Declaration for OASIS re. XACML > From: "bill parducci" <
bill@parducci.net> > To: <
Anne.Anderson@sun.com> > Subject: Re: [xacml] FW: ContentGuard IPR Declaration for OASIS re. XACML > Date: Thu, 28 Nov 2002 06:35:12 -0800 (PST) > > Actually there is significant difference and that is--as pointed out-- > ContentGuard has decided to formally declare a position of IPR in terms are > ambiguous as the verbal mumblings heretofore. This is an *active* response. > It is possible that this is just a misguided attempt to generate revenue via > FUD, but it is also possible that this foretells an [equally misguided] > attempt to reduce competition via litigation. While not a threat to Sun > perhaps, those of us on the bleeding edge cannot withstand even those legal > proceedings without technical merit because of the costs involved ($40,000 > will buy you an *opinion*, not a decision). > > Furthermore, I am not suggest that we “run away” but rather meet this thing > head on while the *technical* people still have some leverage > (pre-approval). By pulling back the submission and stating the reasons why I > think that others will draw similar conclusions. In addition to the official > OASIS statement that will accompany the announcement, many companies in the > TC have access to the various announcement lists to discuss their position > on XACML in the format of PR releases, etc. This can be very powerful (so > far, only those people privy to this thread know of Sun's intents). > > Even if ContentGuard does not recognize the error of its ways, it will at > least draw attention to the fact that XACML comes with potentially litigious > baggage and will encourage OASIS to seek the resolution—or at least, further > prevention of—such occurring again. I think that as a standards group it > falls to us to make such a stand, even if it risks the standard we have > cooperatively created. > > Finally, as to Sun’s “moving forward”, is this an official offer for > attestation? > > b > > Anne Anderson - Sun Microsystems wrote: > > [This is a response from my manager, Steve Hanna. Rather than > reword it as if it came from me, I am passing it on verbatim. > I completely agree with Steve. -Anne] > > I suggest that you respond to Bill, pointing out that > there is little difference between the current situation > and the situation before this letter was received. CG > already said they thought their patents might apply to > XACML. The only change here is that they have now made > an official statement on this topic and they're offering > RAND licensing on those patents for the purposes of > implementing XACML. > > Bill and anyone else who's considering implementing or > using XACML should review the CG patents carefully. We > have already done so and we are proceeding with our > implementation. Several other groups are also doing the > same. Bill can draw his own conclusions. > > Asserting patent claims (valid or not) with respect to > a standard is one way to slow down deployment of that > standard. I would encourage people to review the claims > carefully and not just run away. > > > > -- Anne H. Anderson Email:
Anne.Anderson@Sun.COM Sun Microsystems Laboratories 1 Network Drive,UBUR02-311 Tel: 781/442-0928 Burlington, MA 01803-0902 USA Fax: 781/442-1692