Intra-Domain Presence Federation draft-ietf-simple-intradomain-federation

1
Intra-Domain Presence Federationdraft-ietf-simple
-intradomain-federation

• Jonathan Rosenberg, Cisco
• Avshalom Houri, IBM

2
Problem Statement

• Many cases where there are multiple independent
  presence servers in a single domain
• This implies intra-domain federation
• What that means has been completely undefined

3
Intra-Domain Models
Partitioned
Unioned
Exclusive
Peer
Hierarchical
4
Partitioned
bob_at_example.com
alice_at_example.com
Server 2
Server 1
Looks like interdomain Federation BUT Cannot use
RFC 3263 to route
Alice UA
Bob UA
5
Unioned
alice_at_example.com
alice_at_example.com
Server 2
Server 1
Presence for alice exists In multiple places
Alices Softphone
Alices Cellphone
6
Exclusive
alice_at_example.com
alice_at_example.com
Server 2
Server 1
Presence for alice exists In multiple places, but
onlyone at a time
Alices Softphone 2
Alices Softphone 1
7
Document Goals

• Define each of these models
• Describe applicability of each model
• For each model, discuss issues around
• Identity and policy
• Routing
• Presence composition
• Describe pros and cons of each model

8
Changes since previous draft

• Added Exclusive model
• Clearer distinction with clustering
• Applicability and use cases moved up top

9
Open Issues

• Recommend a routing mechanism as baseline?
• Include sub-domaining as a fourth model?
• Related problems
• IM in each model
• Data federation sharing of buddy lists, etc.
  for unioned and exclusive