RE: [XCON] CPCP Requirement: Repeat times

["Even, Roni" <roni.even@polycom.co.il>]

Hi Petri,
The CPS is a data storage that is used by the focus, so the focus will have
to handle the reservation
Roni

-----Original Message-----
From: petri.koskelainen@nokia.com
To: roni.even@polycom.co.il; hisham.khartabil@nokia.com; xcon@ietf.org
Sent: 06/01/2004 18:50
Subject: RE: [XCON] CPCP Requirement: Repeat times 

Hi Roni,

> My opinion is that the conference policy needs only a 
> conference duration parameter if any. 
> I think that reservation is an external 
> application to the focus. According to the conference 
> framework the focus is using the information in the 
> conference policy server and the focus is 
> not the right place for reservation.

The reservation is sent to CPS, not to focus.
I think it makes sense to have this (repeat time) capability in protocol
since we need the feature anyway in real-world (either in CPCP
or in some new mystery protocol between the user and the reservation
application).



--
Petri


> Regards
> Roni Even
> 
> -----Original Message-----
> From: hisham.khartabil@nokia.com [mailto:hisham.khartabil@nokia.com]
> Sent: Monday, December 15, 2003 4:57 PM
> To: xcon@ietf.org
> Subject: [XCON] CPCP Requirement: Repeat times
> 
> 
> A conference has start and stop times. Although the current proposed
> solution has repeat times (eg: meeting repeats weekly), there is no
> requirement for such.
> 
> Do we see a need for such capability using CPCP? If so, then 
> we need to add
> a requirement.

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