[emergency-comment] RE: [CAP] RE: CAP-list digest, Vol 1 #60 - 3msgs

[Rex Brooks <rexb@starbourne.com>]

You should remember if you continue to post to the public comment 
list, that we have constrained ourselves from responding officially, 
but I definitely object to this characterization, because it gives a 
wholly wrong impression to anyone who has not already taken the time 
and effort to understand the TC process that a specification COULD be 
accepted as a valid submission for OASIS-wide approval as a standard 
without having demonstrated interoperability by having at least three 
member companies vouch for having used the specification 
successfully. As I said before, I am postponing responding to the 
public comment list until after our next TC meeting, so please don't 
expect an answer from this list. I have joined the CAP list, and I 
may or may not respond there.

Ciao,
Rex

At 12:21 PM -0500 3/5/04, Bob Wyman wrote:
>Rex Buddenberg wrote:
>>  The technical authenticity hooks are all in CAP, but
>>  that doesn't prohibit a hoaxter (but it may make him
>>  less anonymous than predecessor systems). 
>	I can't see the "hooks" that you say are in CAP. CAP seems to
>provide only a single, optional, clear-text password field as a means
>for authentication and although it mentions WS-Security, there is no
>discussion in the specification of how WS Security would be used in
>CAP. There is certainly not enough information here to produce
>independent interoperable solutions.
>	Could you please be more specific about where the "hooks" for
>authentication are? Also, can you present an example of a CAP message
>that uses any of these "hooks"?
>
>		bob wyman
>
>
>To unsubscribe from this list, send a post to 
>emergency-comment-unsubscribe@lists.oasis-open.org, or visit 
>http://www.oasis-open.org/mlmanage/.


-- 
Rex Brooks
GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email: rexb@starbourne.com
Tel: 510-849-2309
Fax: By Request