1
|
- Blair Dillaway
- Software Architect
- Microsoft Corp.
|
2
|
|
3
|
|
4
|
- Same approach works for radically different architectures
- Client-Server
- Peer-to-peer
- Multi-tier
- Dynamic adaptation
- Re-direct amongst services with same ‘contract’
- Standard publication and discovery
|
5
|
- Programming Model
- One paradigm
- Uniform messaging model
- Rich tools support rapidly emerging
- Single supporting infrastructure to deploy
|
6
|
- .NET apps require security
- Internet scale, dynamic relationships
- Privacy, potentially high value transactions
- PK-based security will play a significant role
- Strength of mechanism
- Dynamic relationships
- XKMS defines required key-based trust services
- Registration, Discovery, Validation
- It’s a Web Service – same tools, application model, deployment
- Recognizes off-loading trust evaluation may be critical for many
applications and/or classes of devices
|
7
|
- A natural extension to XKMS 1.1 that can benefit many applications
- Leverages Web Services infrastructure
- Exchange richer types of data
- Relationship is fluid, Trust Service and Relying party may be peers
- Support for N-party decision making
- What’s needed
- Support Registration, and updates, of valid key ‘contexts’
- Ability to communicate context with validation requests
- Return of qualified validation, possibly from multiple trust agents
- Msg level security: XKMS defined vs. XML-P defined
|