IETF 61
XCON WG
XCON Framework
Status, Issues and Plans
Editors: Mary Barnes (mary.barnes@nortelnetworks.com)
Chris Boulton (cboulton@ubiquity.net)
Overview
 Current status of XCON framework document
 Summary of issues
 Proposed Data Model
 Way Forward
Nov 8th, 2004
XCON Framework
1
Status
 Basic content of the framework:
 Borrowed basic format from SIPPING Conferencing Framework
(deltas in the SIPPING doc to be discussed in SIPPING session on
Tues. am)
 Terminology and descriptions are protocol agnostic (with SIP
examples)
 Incorporates more complex functionality than provided by SIPPING
conferencing (at this point).
 First pass at this doc intended to provide the foundation for filling in
the gaps and providing the glue for the work items in the XCON
WG.
 Recognize that there are some inconsistencies and additional
content required.
Nov 8th, 2004
XCON Framework
2
Issues
 Editorial clarifications:
 There are inconsistencies in the text that need tidying (e.g.
relationship between focus and conference policy)
 Need clarification of relationship between conference
and media policy:
 Some WG documents have them explicitly separate (e.g. CPCP)
 Others have them being aspects of the same common data (i.e. FW
defines conference policy to consist of membership policy and
media policy and e.g. CCCP)
 Need further detail around the media policy:
 Based on feedback and conclusions of media policy design team.
Nov 8th, 2004
XCON Framework
3
Issues
 Need further detail on floor control:
 E.g. new ‘floor-id’ parameter as defined in draft-camarillo-mmusicsdp-bfcp-00.txt
 Conf anncs and recordings:
 Section 5.9 needs more updating and clarification as it currently
lends the appearance of a single (monolithic) application server for
the conference rather than participant specific interfaces (e.g. an
application instance per participant interacting)
 Whisper:
 Is there a difference between this and a sidebar (current text
suggests that whisper is logically part of same context) ? For
announcements only?
 How will whisper mode be set? In media policy?
 Baseline protocol references:
 RFC 2327 or sdp-new?
Nov 8th, 2004
XCON Framework
4
Additional work items to incorporate
 Need an agreed data model as there should be a
common basis for all the XCON work.
 Need scenarios/flows to highlight how the XCON
functional elements work together and more
importantly how a UA interfaces to the elements to
achieve the desired functionality.
 Add some full physical realization EXAMPLES with a
mix of XCON functions and existing protocols ?
Nov 8th, 2004
XCON Framework
5
Basic Data model
Conf Policy
Conf Policy
Server
Membership Policy:
Floor Control
Server
Participant
1
Participant
2
Participant
3
Media Policy
Control Server
Floor Control Policy:
Media Policy:
Focus
Conf Notification
Server
Conference State (Focus and Conf
Policy State)
•Members
•Media details
Signaling I/F – not defined by XCON
Data I/F
Signaling I/F - defined by XCON
Nov 8th, 2004
XCON Framework
XCON DATA
6
Basic Scenario – Simple 3 SIP parties with dialout list
P1
P2
P3
Focus
CNS
PUT (..<conference-uri>sip:myconf@example.com...<dialout-list>..
…..<media-streams> <audio/>)
REFER
•Update Conf State
CPS
•Create Conf Policy instance
•Media policy
•Membership policy
•Floor control policy
•Create Focus instance
•Initialize Conf State
REFER
•Update Conf State
REFER
Nov 8th, 2004
•Update Conf State
XCON Framework
7
Way Forward
 More list discussion:
 Need additional feedback from primes for other XCON WG
items.
 XCON FW editors need to carefully review updated XCON docs
to ensure consistency in the FW doc (and flag any concerns).
 However, need more general WG feedback as this document
should help provide an overview of all the WG activities and fill
in the gaps on how things should be working together.
 Should this be a WG document?
 Plans are for a more solid document available by year
end..
Nov 8th, 2004
XCON Framework
8