RE: requirements - 4-corner wording

Since the "4-corner" model is only one type of server chaining, couldn't we
take a stab at addressing the wider context.  I'm not suggesting that we
provide a model for server chaining, I think that should probably be dealt
with as part of the model that arises for the aggregation of web services.
There might be, however, necessary protocol within XKMS to support such a
model.  Two things that come to mind are service location and
request/response IDs.. both of which have been a problem, at least for
Identrus, in respect to OCSP chaining.  
 
Anyhow, I understand we want to get an initial version out there in a timely
fashion.. I'm just not sure that there's anything we can say about the
"4-corner" model that doesn't also apply to other types of server chaining
(except perhaps the trust model, which we're certainly not going to deal
with).  I think it's sensible to use the '4-corner' as an example of server
chaining, though. 
 
I should have been on the call to speak about this.. but couldn't make it
yesterday.  
 
-dan

 
 -----Original Message-----
From: Frederick Hirsch [mailto:hirsch@zolera.com]
Sent: Thursday, January 24, 2002 12:57 PM
To: www-xkms@w3.org
Cc: Frederick Hirsch
Subject: requirements - 4-corner wording



Based on yesterday's discussion I drafted a requirement for 4-corner
support. How is this:
 
"XKMS MUST be usable in a 4-corner application model. Specifically, an XKMS
server should be able to pass requests to another XKMS server for processing
without excessive overhead. Although the definition of server chaining and
referral mechanisms are out of scope for the first XKMS
requirements, such mechanisms should not be precluded by the XKMS protocol
or processing specifications"
 
Also for a definition of 4-corner in the definitions section:
 
4-corner model
A model where clients interact with a single point of contact, such as a
local bank for example, submitting requests and obtaining responses. This
point of contact may interact through a backend mechanism with the point of
contact for another participant in the system, enabling a consistent and
simple interface for interactions across a large system population. For more
information see the Identrus documentation (http://www.identrus.com/").
 
---
Frederick Hirsch
Zolera Systems, http://www.zolera.com/ <http://www.zolera.com/>  
Information Integrity, XML Security