W3C XKMS Workshop B2B Requirements

W3C XKMS WorkshopB2B Requirements

Mark Curtis, CTO RSGV0.3 19th July 2001

CTO Research & Standards Group

Agenda

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


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

~ >50% 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


What do we mean by B2B?

FOCUS ACCOUNTS

‘Customer Intimacy’

CONSULTATIVE ACCOUNTS

BUSINESS DIRECT

CHANNEL PARTNER

INDIVIDUALS DIRECT

eg Merrill Lynch

B2B

eg Cazenove & Co

B2B

eg Vodafone

B2B

eg via Charles Schwab

B2B2BB2B2C

eg Reuters PF

B2C

Global Strategic Partnerships

Package SolutionsLeadership

Operational Efficiency Distribution

Partner Driven

Mass Operational Efficiency

Future Business Models based on Customer Segmentation


B2B/XKMS Activities

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


B2B/XKMS Activities

Business Integration with Customers– Procurement, payment, service etc

Information Supply Chain Integration– Digital rights/obligations management

Contributors Reuters Systems

and Products

Distributors and

Channel Partners

Network Services

and Providers

Consumers


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


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


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


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


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


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….


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


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

W3C XKMS WorkshopB2B Requirements

Mark Curtis, CTO RSGV0.2 11th July 2001

W3C XKMS Workshop B2B Requirements

Documents

Transcript of W3C XKMS Workshop B2B Requirements