IETF 69  XCON working group meeting notes by Brian Rosen

1. Agenda Bash

----------------------------------------------------------------------

2. Work Item status - BFCP in RFC Ed queue, Framework request pub
   soon, data model in review, WGLC soon,

   Conf event pkg need more eyes

----------------------------------------------------------------------

3. Status - behind schedule, change dates, what else is new?  AD
   wants to close WG, get the work done

RS: Who was not in SIMPLE?  Answer - almost no one 

RS: Who of those wants xcon to complete?  Answer - everyone

Need data model review; Volunteers for dedicated reviews are Ben
  Campbell, Brian Rosen, Srivatsa Srinivasan, Matt Lepinski, Avashalom
  Houri, Miguel Garcia.  Robert asks for others who would be willing
  to review a section to volunteer.

----------------------------------------------------------------------

4. Data Model discussion - Oscar Novo

Open Issues: floor notification

PSTN-ISDN may include long list of phone numers

Chair: can we have one element type, look at scheme to figure out

  *** Consensus - yes, do that ***

PK: Do we have a problem with SIP connections and PSTN connections
    given a tel: scheme?

BR: No, clients will use SIP or PSTN as they would for any TN,
    server will get it via SIP or PSTN as with any call

SR: Do we need two ways to do this (BFCP and data model)?

AR: Leave as is, reflects decision made several years ago

<phone number>
  do we need a country code?
  chairs: tel uri settles this

Next Step: WGLC

??: Problem with schema name "conference-info", lots of common elements

ON: will check the schema, should be new schema only for new elements

GC: Nov 2004 sipping, need for alternative mechanism to get floor
    control info.

----------------------------------------------------------------------


5. Srivatsa - Conference Event Package

Option-1 from last meeting survives, New media type extends existing schema

Question: Is the new schema a MUST support or a SHOULD?

BR: If you have a new event package, and a new extended mime type,
    then it has to be a MUST

AR: Not clear if its really a new package, so thats the confusion

Chair: need advise from mime experts

ON: Has to be a MUST

Chairs: agree but need advice on how to designate the old thing
        from the new thing

Some edits needed, but then WG document?

Chairs: ask for who read it: several, not a whole lot.  

Chairs: will ask more people to look before asking for WG item on list

SR: Draft has to little info, needs more meat

Chairs: submit text

Chairs: probably want a new rev before asking for WG item, hopefully
        before Vancouver
----------------------------------------------------------------------

6. Text Chat

SIMPLE has protocol specific work (MSRP Chat).  Will reference XCON
chat document for more advanced features, XCON chat will update
with specific protocol ops as XCON evolves.  Adam will produce gap
analysis.

RS: When gap analysis

AR: Within 3 weeks

LM: Data model doesn't reflect what is needed

MB: At one point are we changing data model?  Are we holding up data model?

AR: Thats why 3 weeks, we can see what is needed

BR: Work on Nicknames progressed in an ad-hoc meeting, a mechanism
    proposal is forthcoming

----------------------------------------------------------------------

Speaker Key:

  AR=Adam Roach
  BR=Brian Rosen
  GC=Gonzalo Camarillo
  LM=Lorenzo Miniero
  MB=Mary Barnes
  ON=Oscar Novo
  PK=Paul Kyzviat
  RS=Robert Sparks
  SR=Simon Romano