XCON

IETF 64November 8th – 9th, 2005Vancouver, BC, Canada

Note Well• Any submission to the IETF intended by the Contributor for publication

as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an “IETF Contribution”. Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:

– the IETF plenary session, – any IETF working group or portion thereof, – the IESG, or any member thereof on behalf of the IESG, – the IAB or any member thereof on behalf of the IAB, – any IETF mailing list, including the IETF list itself, any working group or

design team list, or any other list functioning under IETF auspices, – the RFC Editor or the Internet-Drafts function

• All IETF Contributions are subject to the rules of RFC 3978 and RFC 3979. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.

• Please consult RFC 3978 for details.

Administrative Tasks• Minute Taker?

• XMPP Scribe?

• Blue Sheets

• New Area by IETF 65: Realtime Applications and Infrastructure (RAI)

• Ad-hoc mode: even if you know what you’re doing, check your settings. If you don’t know what you’re doing, remove your wireless card.

Agenda: Tuesday

Time LengthDiscussion Leader

Topic

0900 – 0905

5 minutes

Chairs Agenda Bash

0905 – 0915

10 minutes

Chairs Status Update

0915 – 0925

10 minutes

ChairsCharter: Updating Milestones

0925 – 0940

15 minutes

Gonzalo Camarillo

Floor Control: Epilogue

0940 – 1025

45 minutes

Mary Barnes XCON Framework

1025 – 1035

10 minutes

Oscar NovoXCON Common Data Model

1035 – 1055

15 minutes

Orit Levin Conference Package

1055 – 1110

20 minutes

Dave MorganRole Denitions for Common Conferencing

1110 – 1120

10 minutes

Chris BoultonMSRP Centralized Conferencing

1120 – 1130

10 minutes

Roni EvenPeople and Content Video Streams

Agenda: Wednesday

Time LengthDiscussion Leader

Topic

1510 - 1520

10 minutes

ChairsProtocol Selection Discussion

1520 - 1530

10 minutes

Orit Levin CCCP

1530 - 1545

15 minutes

Chris Boulton Media Templates

1545 - 1610

25 minutes

ChairsProtocol Selection Open Discussion

Status

• Floor Control Requirements in RFC Editor’s Queue

• Conferencing Scenarios in RFC Editor’s Queue

• BFCP has gone through IESG review; sent back with some security comments

• Framework document has gone through substantial detailed review from dedicated reviewers

Status (Continued)

• Still need to nalize framework and data model

• Need to complete work around media manipulation (including quite probably media sent to a subset of participants)

• Must identify (and maybe dene) protocol for conference state manipulation

Charter Discussion

• Milestones need resetting• Original plans included different

protocols for media control and membership control

• Current thinking seems to be that protocols for performing such manipulations should, in fact, be a single protocol

Proposed Charter Milestones• Jul 06 – Submit Framework and Data Model for

publication as PS• Aug 06 – Submit Event Notication Package for

publication as PS• Oct 06 – Submit Common Conference Information

Denition for publication as PS• Nov 06 – Submit Conference Template Denition

for publication as PS• Dec 06 – Submit Conference Control Protocol for

publication as PS• Any IM-related work can begin discussion after

Conference Control Protocol is in the IESG’s hands (e.g. MSRP conferencing BCP)

XCON: Session 2

IETF 64November 9th, 2005

Vancouver, BC, Canada

Protocol Selection: Don’t Make Me Stop This Car

• CCCP, CPCP, and CSCP have actual proposed specications• Several other ideas have been oated informally, but no

one has invested cycles in documenting them in a draft– Some are very general; e.g. proposals to “use SOAP” is about

as well-specified as saying “use IP”.• We need to decide on a way forward.

– Anyone with a proposal that has not been documented in a draft needs to either produce a draft or stop making proposals. Deadline is December 31st.

– Between now and December 31st, interested parties should discuss criteria for evaluating protocols on the mailing list.

– We will be taking volunteers to author a document to formally evaluate the proposals against the criteria and make a recommendation before March.

• Goal is to have protocol specication in IESG’s hands by end of 2006.