Freetime Lookup

[Denis BIGORGNE <Denis.Bigorgne@xxxxxxx>]

In the C&S Overview document, the Freetime Lookup function  
seems adapted to corporate environments, where calendar 
sharing is a fair rule. Im not sure that extensive request of 21 
days freetime map could be accepted for automated 
appointment scheduling made outside the enterprise ; there 
could be too many indiscretions opportunities, like trying to 
know who is busy at the same time...

Instead of a one-shot ORing of freetime maps, the appointment 
scheduling could use a multi-round negotiation algorithm 
controlling the exchange of a list of time-slots (or ranges) 
arranged by preference order. At each step, the list should be 
narrowed, discarding the impossibilities ; if the list is reduced 
to null, an extension should be proposed... For two-parts 
meeting, a simple round may be sufficient ; for numerous 
invitee, many rounds could be required, with a succession of 
narrowing and extension phases. At SEPT, we developed a PC 
conference appointment scheduling demo using list of ten time-
slots ; I have been told that in some corporation, the directive 
for non-automated scheduling requires an initial list of  only 
three time-slots.

Another item seems problematic to me : the ressource 
caracterisation. In Petes document, a ressource is simply 
another agenda which must be inquired. This is certainly true 
for common ones, like network reservation. But  :

- some ressources are private : if you are trying to schedule a 
videoconference, the networks ressources are (more or less) 
common, but the terminal equipments are private and 
external requesters are probably not allowed to make 
reservations - it is a task to be done by each invitee calendar 
agent (or user himself).

- the disponibilities of the ressources are dependant of the 
time. By instance, an user may be present at some location 
at some time, and can only be call by phone at another time.
A solution could be that the items of the negotiation list (or of 
the freetime map) should not be simple time-slots but consist in  
a time-slot plus acceptable media (physical location, phone, 
videoconferencing protocol,...). Note that the  
videoconferencing descrition is not trivial - see IETF mmusic 
WG.

I understand my comments goes beyond the capabilities of the 
majority of the current calendar products ; this is explainable - I 
dont speak from a technology provider point of view, but from 
an user one, and more, an user interested in teleconferencing in 
a general environment (not corporate). If we are to establish an 
interoperability standard on the Internet, these aspects should 
not be forgotten.

Regards,
	Denis

Denis Bigorgne
France Telecom / CNET / SEPT
bigorgne@sept.fr
phone : +33 31 75 92 29      fax : +33 31 75 06 31