XCON Meeting Minutes - Tuesday 29th July 2008
_____________________________________________


Agenda Bash
___________

- One new new RFC - A Framework for Centralized Conferencing (RFC 5239).


CCMP - Mary Barnes
__________________

- Mary has reviewed current status of document including changes + added new 
author (Simon Romano).

- Mary provides information based on implementation from the University of 
Napoli.  Includes example message flows and interface screen shots.

- OPEN ISSUES:

	- If SOAP is to be used we need an .xsd file - either in Data Model OR protocol
	document.  This will make life easier when using many industry tools and 
	wizards.

	- Do we require aditional methods such as allowed user list etc?  
	****ACTION**** - Mary to mail the list.

	- Policies - role based XACML is a potential candidate.
	****ACTION**** - Authors to research and bring the results back to the
	work group.

	- Adam - sounds like work has already been done?

	- Mary - would need adaption for our use.

	- Adam - more analysis needed.

	Notification mechanism - 

	Andrew Allen - Should we not just use SIP?

	Mary Barnes - What about the PSTN user case with a web interface (or other non
	signalling participating member).

	Simon Romano - This is just a side issue - we should separate from the core CCMP protocol and 
	use an appropriate notification mechanism.

	Roni Even - If more than one user - you need a notification mechanism.  YOu have to have 		something that enables you to receive changes.

	Adam Roach - potentially need an ETAG type mechanism to avoid race conditions.

	****ACTION**** - Mary Barnes - Move forward and authors talk to App area directors for
	additional advice and guidance. 

	Unknown participant - Notification mechanism should be defined separately.


Example Call Flow Document - Mary Barnes
________________________________________

- Objectives covered in presentation 

- Initial scenarios from section 9 of XCON Framework + XCON chat draft.

- Provides logical view for implementing protocol - including state diagrams.

- Includes intro text, ladder diagram, text for ladder diagram and call flow.

- Feedback requested on format and content before authors dive into the detailed flows.

	- Add flow?
	- more text upfront? etc.

- Moving forward - complete initial flows - add details as prototype evolve.

- Comments? Questions?

Implementation Demo - Simon Romano
__________________________________

- Simon steps through message flows.

- Unknown - Parent child issue could be got rid of in favor of explicit blueprints.

- Mary - goes against fundamental framework layout.

- Simon - Object is a real existence of a conference while blueprint is really just a description.

MEETING COMPLETE