W3C XKMS Workshop B2B Requirements

1
W3C XKMS WorkshopB2B Requirements
Mark Curtis, CTO RSG V0.3 19th July 2001
2
Agenda

• Reuters B2B Overview
• Dimensions of B2B Commerce
• XKMS Trust Requirements/Issues
• Recommendations

3
Reuters Business Operations

• Not just a News Agency
• Information Company
• Financial Markets
• Corporate Treasurers and Bond Managers
• Newspaper, Broadcasters, News Agencies
• Transactions
• Foreign Exchange Dealing
• gt50 of world spot fx transactions
• Instinet, worlds leading agency broker

From knowing to doing
Fortunately, there is a model for the future
shape of B2B the financial service
industry Beyond the Exchange The Future of B2B,
Harvard Business Review Nov-Dec 2000
4
What do we mean by B2B?
5
B2B/XKMS Activities

• Business Process Integration with Customers
• Procurement, payment, service etc

6
B2B/XKMS Activities

• Business Integration with Customers
• Procurement, payment, service etc
• Information Supply Chain Integration
• Digital rights/obligations management

7
B2B/XKMS Activities

• Business Process Integration with Customers
• Procurement, payment, service etc
• Information Supply Chain Integration
• Digital rights/obligations management
• Aggregation of Business Venues/Exchanges
• Publish offers
• Indication of interest (IOI)
• Price vs. Value
• Trade
• Range of different trading models

8
Aggregation of Business Venues

• Registration
• Portable registration attributes e.g. FSA money
  laundering checks
• Common authentication framework
• View offer in one channel, select the offer and
  automate execution in another e.g. SSO
• Internal status of trader
• Role, responsibilities
• External position status of trader
• Credit allocation to particular organisation
• Market credit position
• Dynamic status services
• Dispute Resolution
• Who did what, when, and why

9
What does XKMS give us?

• Low tier service
• Certificate resolution
• In a B2B world we know who we are dealing with-we
  can already resolve certs
• Good to move to standard model
• Higher level interface into PKI services
• We have already developed these internally
• Map our interfaces to those of XKMS
• Higher tier services
• More consumable application level trust services
• Easier to map to business models and requirements

10
B2B Issues

• Operability across multiple domains
• User centric key registration service vs.
  application level centric key registration
  service
• Interoperability between domains
• Trust relationship
• User defined
• Service defined
• Business relevant trust attributes
• Context of business
• Meta data for acceptance

11
B2B Issues

• Service association
• Information may be distributed
• Third party attribute and service association
• Rules for association
• Privacy
• Conditions for disclosure of information
• User defined
• Administration

12
XKMS Adoption

• Technical Framework
• High level interfaces
• SDKs tend to be clunky
• Packaging is important
• Service integration
• Policy Framework
• Aligned to business verticals?
• Privacy
• Standards Framework
• XKMS (XKISS,XKRSS, XTASS), SAML, XACML, MPEG21
• ebXML, UDDI, LDAP.

13
Challenges

• Acceptance
• Solve problems not just package them
• Usability
• High level interfaces
• Configuration vs. coding
• Interoperability
• Relevant business context
• Architectural consistency
• Clearly identified boundaries and relationships
  between standards

14
Recommendations

• Push ahead with definition of lower tier service
  levels
• Test against real business driven scenarios
• Outline scope and requirements for the provision
  of higher tier services
• Map out relationships and interfaces to other
  standard activities operating in this space
• Remove confusion, provide focus and prevent
  duplication

15
W3C XKMS WorkshopB2B Requirements
Mark Curtis, CTO RSG V0.2 11th July 2001