RE: [XCON] CPCP Requirement: Repeat times

[petri.koskelainen at nokia.com]

I think the current requirements (as written in -02 draft) 
fulfill all the issues raised here. For example, extending conference duration
is possible (just modify stop time anytime).

I'm not sure about the "keep this conference running as long as there are users,
then stop the conference" issue. You could easily set the stop time to be next year.
I guess this covers the use case.


--
Petri


> -----Original Message-----
> From: xcon-admin@ietf.org [mailto:xcon-admin@ietf.org]On Behalf Of ext
> Keith Lantz
> Sent: 05 February, 2004 22:34
> To: Bieselin, David
> Cc: Lantz, Keith; Rosen, Brian; Even, Roni; Drage, Keith (Keith);
> xcon@ietf.org
> Subject: RE: [XCON] CPCP Requirement: Repeat times 
> 
> 
> Good point. OK then, I agree with MOST of what Brian was 
> saying, and agree 
> with you that an additional "allow to extend if resources are 
> available" 
> option is desirable (as an optimization for the user).
> 
> Cheers, Keith
> 
> At 12:19 PM 2/5/2004, Bieselin, David wrote:
> >I have to disagree .. How many of you leave the conference room you
> >reserved just because the end time came?  Why would you?   If you are
> >having a useful meeting (do not laugh) then you should be allowed to
> >continue should there be no reservations behind you.
> >
> >If you forced people to manually do this you would have to stop the
> >meeting and say, "Hold it Jim, we need to extend this room 
> for time is
> >running out!".  You want that to happen based on the policy of the
> >conference service.  Therefore one room can be set up for 
> allow meeting
> >to continue for as long as the people are in there and productive and
> >the next for only the time allotted.  On the other hand, if 
> you wanted
> >to guarantee it, you can certainly do it manually before. 
> However, this
> >is also subject to policy constraints as Brian mentions below.
> >
> >Dave
> >
> >-----Original Message-----
> >From: Lantz, Keith
> >Sent: Thursday, February 05, 2004 8:42 AM
> >To: Rosen, Brian
> >Cc: 'Even, Roni'; 'Drage, Keith (Keith)'; xcon@ietf.org; 
> Bieselin, David
> >Subject: RE: [XCON] CPCP Requirement: Repeat times
> >
> >I agree.
> >
> >At 07:26 AM 2/5/2004, Rosen, Brian wrote:
> > >I think the protocol should let you change it at any time.
> > >I think a particular implementation might have policy issues (for
> > >example, it may not be able to reserve the resources), so 
> the attempt
> > >may fail.
> > >
> > >I don't see why you need an explicit choice or "allowed to extend".
> > >The choice you would select is "end at stop time", and you 
> can change
> > >stop time (policy permitting).
> > >
> > >Brian
> > >
> > > > -----Original Message-----
> > > > From: Even, Roni [mailto:roni.even@polycom.co.il]
> > > > Sent: Thursday, February 05, 2004 9:19 AM
> > > > To: 'Rosen, Brian'; 'Drage, Keith (Keith)'
> > > > Cc: xcon@ietf.org
> > > > Subject: RE: [XCON] CPCP Requirement: Repeat times
> > > >
> > > >
> > > > Brian,
> > > >
> > > > When is the stop time get set, before the conference? 
> can you change
> >
> > > > it once the conference has started or after an event 
> announcing that
> >
> > > > the conference will end soon.
> > > >
> > > > Since this is a way to extend then a choice of "allowed 
> to change
> > > > stop time after conference started" may also be needed.
> > > >
> > > > About your choices I assume that logical operators 
> between them are
> > > > allowed.
> > > > e.g "end when convener leaves" OR "end when stop time 
> is reached"
> > > >
> > > > Roni Even
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > > > Sent: Thursday, February 05, 2004 4:02 PM
> > > > To: 'Drage, Keith (Keith)'; Keith Lantz
> > > > Cc: xcon@ietf.org; Dave Bieselin
> > > > Subject: RE: [XCON] CPCP Requirement: Repeat times
> > > >
> > > >
> > > > I formally propose a requirement that states
> > > >
> > > > There shall be a method for specifying when the conference ends,
> > > > with choices for at least: "end when last person 
> leaves", "end when
> > > > convener leaves"
> > > > and "end when stop time is reached".  It is not be a requirement
> > > > that all CPCP servers implement all such options.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----

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