Re: [XCON] Topic#1 Reservation and Conference[Was: Terminology:Pollfor Consensus]

[Yaron Reinharts <YARONR at il.ibm.com>]

I agree with Henning

I find it obvious that a reservation and a conference are two different
things
Trying to handle reservations on the Conference server just complicates the
model,
no wonder this argument lasts so long
What about moving the reservation part from the XCON server to another
entity,
 lets call it the 'Reservations server"

So now we have two servers, the XCON server and the Reservations server
The Reservations server will be used to create and manipulate scheduled
meetings,
this can be done using a protocol design just for this (and only for this)
A meeting which were scheduled on a Reservations server is called a
"Reservation"
and a record for it exist on the Reservations server
All manipulations on reservations are handled by this server
When the reservation time of a Reservation arrives the reservations server
would
create the conference on the Conference server and the Reservation record
will be
deleted (updated for recurring conference)  from the Reservations server

The XCON server will handle the conference itself
It is not aware of reservations (of course, it's a conference server)
The protocol which will be used to create Conferences on the XCON server
will be used by the XCON clients to create ad hoc Conferences

/Yaron


_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon