Re: Status of the CALSCH working group (CALID vs CU time)

Doug Royer <[email protected]>
Newsgroups gmane.ietf.calendar
Organization http://INET-Consulting.com
Message-ID <[email protected]>
------------------------------------------------------------------------

    * To: "ietf-calendar@xxxxxxx <mailto:[email protected]>"
      <ietf-calendar@xxxxxxx <mailto:[email protected]>>
    * Subject: Re: Status of the CALSCH working group
    * From: Bruce_Kahn@xxxxxxxxxxxxxxxx <mailto:[email protected]>
    * Date: Mon, 10 Nov 2003 12:02:28 -0500
    * In-reply-to: <>
    * List-archive: <http://www.imc.org/ietf-calendar/mail-archive/>
    * List-id: <ietf-calendar.imc.org>
    * List-unsubscribe:
      <mailto:[email protected]?body=unsubscribe>
    * Sender: owner-ietf-calendar@xxxxxxxxxxxx
      <mailto:[email protected]>

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

 >> Because some want and expect the CU (user) VFREEBUSY and others want the
 >> CALID (calendar) VFREEBUSY. Currently the iTIP method gets the CU 
VFREEBUSY
 >> that just might be the same as the CALID VFREEBUSY.

 > We have never drawn a distinction between a CUs availability or a 
calendars before.  Are you saying you have > some proposal in mind for 
drawing a distinction?  Something like hierarchical calendars with 
busytime / content > rollup or "calendar bundling"?  Please say no...

If I spend the time and go find the instances where we have talked about 
it, will you change your mind?

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
[email protected]                 | Office: (208)520-4044
http://Royer.com/People/Doug   |    Fax: (866)594-8574
                               |   Cell: (208)520-4044

               We Do Standards - You Need Standards
smime.p7s (application/x-pkcs7-signature, 4.6 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.