From owner-ietf-calendar@imc.org  Thu Apr  1 11:51:19 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25732
	for <calsch-archive@odin.ietf.org>; Thu, 1 Apr 1999 11:51:19 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id IAA00590
	for ietf-calendar-bks; Thu, 1 Apr 1999 08:13:07 -0800 (PST)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id IAA00586
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 08:13:05 -0800 (PST)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id IAA29581
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 08:13:13 -0800 (PST)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id LAA06093
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 11:15:21 -0500
Message-ID: <37039B98.87D8115E@ecal.com>
Date: Thu, 01 Apr 1999 16:15:20 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Some Text on Security
References: <01D6C7224936D211BA450000F805D53805421378@TOTO>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Larry Osterman (Exchange)" wrote:

> It's my understanding that a
> bunch of the IETF protocols are moving to DIGEST as their must-implement
> authentication mechanism.

When I was at Netscape, Everyone Knew that http-digest was insufficiently
secure.  I don't know details, unfortunately; it was something that everyone
said our security people had said, but I never heard it from our security
people.  Anybody know more?

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Thu Apr  1 11:56:26 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25943
	for <calsch-archive@odin.ietf.org>; Thu, 1 Apr 1999 11:56:25 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id IAA00640
	for ietf-calendar-bks; Thu, 1 Apr 1999 08:18:25 -0800 (PST)
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id IAA00636
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 08:18:24 -0800 (PST)
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
	id AA01026; Thu, 1 Apr 99 11:19:28 EST
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
	by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id LAA09496;
	Thu, 1 Apr 1999 11:18:35 -0500 (EST)
Received: from [18.162.2.188] (BLUEBOX-371.MIT.EDU [18.162.2.188])
	by melbourne-city-street.MIT.EDU (8.9.2/8.9.2) with ESMTP id LAA07017;
	Thu, 1 Apr 1999 11:18:34 -0500 (EST)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Sender: bobmah@po10.mit.edu
Message-Id: <v04204d04b3294c85a5fe@[18.162.2.188]>
In-Reply-To: <37039B98.87D8115E@ecal.com>
References: <01D6C7224936D211BA450000F805D53805421378@TOTO>
 <37039B98.87D8115E@ecal.com>
Date: Thu, 1 Apr 1999 11:19:06 -0500
To: John Stracke <francis@ecal.com>
From: Bob Mahoney <bobmah@mit.edu>
Subject: Re: Some Text on Security
Cc: ietf-calendar@imc.org
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

At 4:15 PM +0000 4/1/99, John Stracke wrote:
>
>When I was at Netscape, Everyone Knew that http-digest was insufficiently
>secure.  I don't know details, unfortunately; it was something that everyone
>said our security people had said, but I never heard it from our security
>people.  Anybody know more?

One snippet from Keith & Patrik's document:

----
2.3 Security

     Although HTTP appears at first glance to be one of the few "mature"
Internet protocols that  can  provide  good  security,  there  are  many
applications  for which neither HTTP's digest authentication nor TLS are
sufficient by themselves.

     Digest authentication requires a secret (e.g.  a  password)  to  be
shared  between  client  and  server.   This  further requires that each
client know the secret to be used with each  server,  but  it  does  not
provide  any  means  of  securely  transmitting such secrets between the
parties.  Shared secrets can work fine for small groups  where  everyone
is physically co-located; they don't work as well for large or dispersed
communities of users.  Further, if the server  is  compromised  a  large
number  of  secrets may be exposed, which is especially dangerous if the
same secret (or password) is used for several applications.

     TLS is  descended  from  SSL,  which  was  originally  designed  to
authenticate servers to clients - not the other way around.  Even though
TLS now provides mutual authentication, a client that needs to  talk  to
multiple  servers  must  still know which credentials to present to each
server before establishing a secure connection to  the  server.   Client
and  server  must  each  use  private keys that are trusted by the other
party - typically because they are signed  by  a  certificate  authority
(CA)  known  to  the  other.  As in the digest authentication case, both
client and server need  ways  to  protect  their  private  keys  against
exposure.
----



From owner-ietf-calendar@imc.org  Thu Apr  1 14:12:48 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00308
	for <calsch-archive@odin.ietf.org>; Thu, 1 Apr 1999 14:12:46 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id KAA01946
	for ietf-calendar-bks; Thu, 1 Apr 1999 10:27:46 -0800 (PST)
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id KAA01942
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 10:27:45 -0800 (PST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54])
	by netscape.com (8.8.5/8.8.5) with ESMTP id KAA02225
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 10:27:28 -0800 (PST)
Received: from netscape.com ([208.12.60.179]) by dredd.mcom.com
          (Netscape Messaging Server 4.01) with ESMTP id F9IWLS01.J8J;
          Thu, 1 Apr 1999 10:27:28 -0800 
Message-ID: <3703BADB.B5791D59@netscape.com>
Date: Thu, 01 Apr 1999 10:28:43 -0800
From: jsun@netscape.com (John Sun)
Organization: Netscape Communications
X-Mailer: Mozilla 4.5 [en]C-NSCP  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Steve Mansour <sman@netscape.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        Richard Shusterman <rans@netscape.com>
Subject: Re: Delimiter characters in relativeCalUID
References: <FD7A762E588AD211A7BC00805FFEA54BE8060C@HYDRANT> <36FFE5F1.14A9FF52@netscape.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

There are many problems with using a '/' were used to represent a
calendar hierarchy.
In fact, imposing any semantic definition to unique identifier has many
problems.

Here are some problems using a '/' to represent calendar hierarchy:

1) Force the server designer to use a specific calendar hierarchy.

It imposes a folder like hierarchy of calendars similar to file
diretories.
If the designer used a database for storing calendars, there is no
meaning to the slashes.  Calendar hierarchy should be specified ONLY
through the parent and child-list properties.

2) Exposes the calendar hierarchy to clients.

The server may not want to expose the calendar store's hierarchy just to
allow access to a calendar.  However, if a '/' was used to meaning a
level of hierarchy, then I would have to expose the entire path to allow
access to a calendar.

Suppose calendar "ghi" is a child of calendar "def",
which is a child of calendar "abc".

Thus the URL to access calendar "ghi" would be

    http://calendar.x.com/abc/def/ghi.

The URL exposes the hierarchy of calendar "ghi" to the user.
A user should NOT know the hierarchy of a calendar just to access it.


Steve Mansour wrote:

> OK. Let's put this point to the test. Should we introduce one or more
> delimiter
> characters into relativeCalUID or should it be an opaque string?
> Speak up.
>
> -Steve
>
> "Lisa Lippert (Dusseault) (Exchange)" wrote:
>
> > I haven't been at the CAP authors meetings lately, but that
> shouldn't matter
> > -- I don't recall seeing a consensus on the list or in the WG
> meeting that
> > the delimiters should not be defined.
> >
> > Undefined strings are very scary for later versions of the protocol
> -- we
> > will hamstring ourselves for CAP 2 (or later) if we can't easily
> enhance
> > hierarchical functionality in calendaring.  Furthermore,
> interoperability is
> > threatened if different implementations understand different things
> from
> > different characters.  I'd like to see a character defined as a
> hierarchical
> > delimiter, even if implementations are not required to support
> hierarchies.
> > It will be much less painful in the long run if we define the
> character now.
> >
> > We should also be very explicit about other possibly "special"
> characters
> > such as spaces, tildes, and whether they are meaningful,
> meaningless,
> > reserved, must be supported, etc.
> >
> > Lisa
> >
> > -----Original Message-----
> > From: sman@netscape.com [mailto:sman@netscape.com]
> > Sent: Monday, March 29, 1999 12:21 PM
> > To: John Stracke
> > Cc: calsch WG
> > Subject: Re: IRIP version 4 (Part 1) c
> >
> > John Stracke wrote:
> >
> > > Steve Mansour wrote:
> > >
> > > > Bruce_Kahn@iris.com wrote:
> > > >
> > > >> Good choice until that last part.  You should preclude some
> > > >> characters like
> > > >> '/' or <CR>, etc.
> > > >
> > > > Why?  You aren't suggesting a delimiter character are you? That
> would
> > > > imply some sort of structure. :-)
> > >
> > > Even if we don't have structure today, a delimiter permits us to
> *add*
> > > structure later if it turns out to be useful.
> >
> > We went through that discussion a two of the editors meetings. The
> general
> > feeling is that it's a bad idea to put *any* sort of meaning into
> these
> > strings. Even a delimiter character.
> >
> > -Steve



From owner-ietf-calendar@imc.org  Thu Apr  1 14:13:00 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00324
	for <calsch-archive@odin.ietf.org>; Thu, 1 Apr 1999 14:13:00 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id KAA01920
	for ietf-calendar-bks; Thu, 1 Apr 1999 10:26:16 -0800 (PST)
Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id KAA01915
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 10:26:15 -0800 (PST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54])
	by netscape.com (8.8.5/8.8.5) with ESMTP id KAA02011
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 10:26:10 -0800 (PST)
Received: from netscape.com ([208.12.60.179]) by dredd.mcom.com
          (Netscape Messaging Server 4.01) with ESMTP id F9IWJN00.B8D;
          Thu, 1 Apr 1999 10:26:11 -0800 
Message-ID: <3703BA86.245332F5@netscape.com>
Date: Thu, 01 Apr 1999 10:27:18 -0800
From: jsun@netscape.com (John Sun)
Organization: Netscape Communications
X-Mailer: Mozilla 4.5 [en]C-NSCP  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Steve Mansour <sman@netscape.com>,
        "ietf-calendar@imc.org" <ietf-calendar@imc.org>,
        Richard Shusterman <rans@netscape.com>
Subject: Re: Delimiter characters in relativeCalUID
References: <FD7A762E588AD211A7BC00805FFEA54BE8060C@HYDRANT> <36FFE5F1.14A9FF52@netscape.com>
Content-Type: multipart/alternative;
 boundary="------------262ED3946247751288C3F010"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


--------------262ED3946247751288C3F010
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

There are many problems with using a '/' were used to represent a calendar
hierarchy.
In fact, imposing any semantic definition to unique identifier has many problems.

Here are some problems using a '/' to represent calendar hierarchy:

1) Force the server designer to use a specific calendar hierarchy.

It imposes a folder like hierarchy of calendars similar to file diretories.
If the designer used a database for storing calendars, there is no meaning to the
slashes.  Calendar hierarchy should be specified ONLY through the parent and
child-list properties.

2) Exposes the calendar hierarchy to clients.

The server may not want to expose the calendar store's hierarchy just to allow
access to a calendar.  However, if a '/' was used to meaning a level of hierarchy,
then I would have to expose the entire path to allow access to a calendar.

Suppose calendar "ghi" is a child of calendar "def",
which is a child of calendar "abc".

Thus the URL to access calendar "ghi" would be

    http://calendar.x.com/abc/def/ghi.

The URL exposes the hierarchy of calendar "ghi" to the user.
A user should NOT know the hierarchy of a calendar just to access it.


Steve Mansour wrote:

> OK. Let's put this point to the test. Should we introduce one or more delimiter
> characters into relativeCalUID or should it be an opaque string?  Speak up.
>
> -Steve
>
> "Lisa Lippert (Dusseault) (Exchange)" wrote:
>
> > I haven't been at the CAP authors meetings lately, but that shouldn't matter
> > -- I don't recall seeing a consensus on the list or in the WG meeting that
> > the delimiters should not be defined.
> >
> > Undefined strings are very scary for later versions of the protocol -- we
> > will hamstring ourselves for CAP 2 (or later) if we can't easily enhance
> > hierarchical functionality in calendaring.  Furthermore, interoperability is
> > threatened if different implementations understand different things from
> > different characters.  I'd like to see a character defined as a hierarchical
> > delimiter, even if implementations are not required to support hierarchies.
> > It will be much less painful in the long run if we define the character now.
> >
> > We should also be very explicit about other possibly "special" characters
> > such as spaces, tildes, and whether they are meaningful, meaningless,
> > reserved, must be supported, etc.
> >
> > Lisa
> >
> > -----Original Message-----
> > From: sman@netscape.com [mailto:sman@netscape.com]
> > Sent: Monday, March 29, 1999 12:21 PM
> > To: John Stracke
> > Cc: calsch WG
> > Subject: Re: IRIP version 4 (Part 1) c
> >
> > John Stracke wrote:
> >
> > > Steve Mansour wrote:
> > >
> > > > Bruce_Kahn@iris.com wrote:
> > > >
> > > >> Good choice until that last part.  You should preclude some
> > > >> characters like
> > > >> '/' or <CR>, etc.
> > > >
> > > > Why?  You aren't suggesting a delimiter character are you? That would
> > > > imply some sort of structure. :-)
> > >
> > > Even if we don't have structure today, a delimiter permits us to *add*
> > > structure later if it turns out to be useful.
> >
> > We went through that discussion a two of the editors meetings. The general
> > feeling is that it's a bad idea to put *any* sort of meaning into these
> > strings. Even a delimiter character.
> >
> > -Steve

--------------262ED3946247751288C3F010
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<tt>There are many problems with using a '/' were used to represent a calendar
hierarchy.</tt>
<br><tt>In fact, imposing any semantic definition to unique identifier
has many problems.</tt><tt></tt>
<p><tt>Here are some problems using a '/' to represent calendar hierarchy:</tt><tt></tt>
<p><tt>1) Force the server designer to use a specific calendar hierarchy.</tt><tt></tt>
<p><tt>It imposes a folder like hierarchy of calendars similar to file
diretories.</tt>
<br><tt>If the designer used a database for storing calendars, there is
no meaning to the slashes.&nbsp; Calendar hierarchy should be specified
ONLY through the parent and child-list properties.</tt><tt></tt>
<p><tt>2) Exposes the calendar hierarchy to clients.</tt><tt></tt>
<p><tt>The server may not want to expose the calendar store's hierarchy
just to allow access to a calendar.&nbsp; However, if a '/' was used to
meaning a level of hierarchy, then I would have to expose the entire path
to allow access to a calendar.</tt><tt></tt>
<p><tt>Suppose calendar "ghi" is a child of calendar "def",</tt>
<br><tt>which is a child of calendar "abc".</tt><tt></tt>
<p><tt>Thus the URL to access calendar "ghi" would be</tt><tt></tt>
<p><tt>&nbsp;&nbsp;&nbsp; <A HREF="http://calendar.x.com/abc/def/ghi">http://calendar.x.com/abc/def/ghi</A>.</tt><tt></tt>
<p><tt>The URL exposes the hierarchy of calendar "ghi" to the user.</tt>
<br><tt>A user should NOT know the hierarchy of a calendar just to access
it.</tt>
<br>&nbsp;
<p>Steve Mansour wrote:
<blockquote TYPE=CITE>OK. Let's put this point to the test. Should we introduce
one or more delimiter
<br>characters into relativeCalUID or should it be an opaque string?&nbsp;
Speak up.
<p>-Steve
<p>"Lisa Lippert (Dusseault) (Exchange)" wrote:
<p>> I haven't been at the CAP authors meetings lately, but that shouldn't
matter
<br>> -- I don't recall seeing a consensus on the list or in the WG meeting
that
<br>> the delimiters should not be defined.
<br>>
<br>> Undefined strings are very scary for later versions of the protocol
-- we
<br>> will hamstring ourselves for CAP 2 (or later) if we can't easily
enhance
<br>> hierarchical functionality in calendaring.&nbsp; Furthermore, interoperability
is
<br>> threatened if different implementations understand different things
from
<br>> different characters.&nbsp; I'd like to see a character defined as
a hierarchical
<br>> delimiter, even if implementations are not required to support hierarchies.
<br>> It will be much less painful in the long run if we define the character
now.
<br>>
<br>> We should also be very explicit about other possibly "special" characters
<br>> such as spaces, tildes, and whether they are meaningful, meaningless,
<br>> reserved, must be supported, etc.
<br>>
<br>> Lisa
<br>>
<br>> -----Original Message-----
<br>> From: sman@netscape.com [<a href="mailto:sman@netscape.com">mailto:sman@netscape.com</a>]
<br>> Sent: Monday, March 29, 1999 12:21 PM
<br>> To: John Stracke
<br>> Cc: calsch WG
<br>> Subject: Re: IRIP version 4 (Part 1) c
<br>>
<br>> John Stracke wrote:
<br>>
<br>> > Steve Mansour wrote:
<br>> >
<br>> > > Bruce_Kahn@iris.com wrote:
<br>> > >
<br>> > >> Good choice until that last part.&nbsp; You should preclude
some
<br>> > >> characters like
<br>> > >> '/' or &lt;CR>, etc.
<br>> > >
<br>> > > Why?&nbsp; You aren't suggesting a delimiter character are you?
That would
<br>> > > imply some sort of structure. :-)
<br>> >
<br>> > Even if we don't have structure today, a delimiter permits us to
*add*
<br>> > structure later if it turns out to be useful.
<br>>
<br>> We went through that discussion a two of the editors meetings. The
general
<br>> feeling is that it's a bad idea to put *any* sort of meaning into
these
<br>> strings. Even a delimiter character.
<br>>
<br>> -Steve</blockquote>
</html>

--------------262ED3946247751288C3F010--



From owner-ietf-calendar@imc.org  Thu Apr  1 14:37:30 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01067
	for <calsch-archive@odin.ietf.org>; Thu, 1 Apr 1999 14:37:30 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id KAA02337
	for ietf-calendar-bks; Thu, 1 Apr 1999 10:57:37 -0800 (PST)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id KAA02332
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 10:57:37 -0800 (PST)
Received: by dfssl with Internet Mail Service (5.5.2580.0)
	id <HY5JK5BP>; Thu, 1 Apr 1999 10:57:15 -0800
Message-ID: <01D6C7224936D211BA450000F805D5380542138D@TOTO>
From: "Larry Osterman (Exchange)" <larryo@Exchange.Microsoft.com>
To: "'Bob Mahoney'" <bobmah@mit.edu>, John Stracke <francis@ecal.com>
Cc: ietf-calendar@imc.org
Subject: RE: Some Text on Security
Date: Thu, 1 Apr 1999 10:57:14 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

However the same statements made below can be made about ANY of the MTI
authentication mechanisms that have been discussed, and in general are the
same for every shared secret authentication mechanism.

I don't think that it is appropriate to discard http-digest simply because
it's a shared secret authentication mechanism, it's "good enough" to pass
IESG muster, and that should be sufficient.  HTTP-DIGEST does have
vulnerabilities, however the vulnerabilities derive directly from the fact
that it's simple to implement, and in reality the simple to implement
criteria is overwhelming in a MTI authentication mechanism.

There is nothing that prevents a more secure SASL mechanism from being
deployed by a vendor, neither is there a requirement that a CUSTOMER not be
allowed to turn off the MTI mechanism (if the customer percieves it as being
insufficiently secure).  The customer SHOULD be notified that disabling the
MTI mechanism may cause interoperability issues, however that's ultimately
the customers decision.

Larry Osterman
Sent from larryo-laptop.dns.microsoft.com running NT5 and Outlook 2000
and Exchange Server 5.5.  Please notify the sender of any difficulties



-----Original Message-----
From: Bob Mahoney [mailto:bobmah@mit.edu]
Sent: Thursday, April 01, 1999 8:19 AM
To: John Stracke
Cc: ietf-calendar@imc.org
Subject: Re: Some Text on Security


At 4:15 PM +0000 4/1/99, John Stracke wrote:
>
>When I was at Netscape, Everyone Knew that http-digest was insufficiently
>secure.  I don't know details, unfortunately; it was something that
everyone
>said our security people had said, but I never heard it from our security
>people.  Anybody know more?

One snippet from Keith & Patrik's document:

----
2.3 Security

     Although HTTP appears at first glance to be one of the few "mature"
Internet protocols that  can  provide  good  security,  there  are  many
applications  for which neither HTTP's digest authentication nor TLS are
sufficient by themselves.

     Digest authentication requires a secret (e.g.  a  password)  to  be
shared  between  client  and  server.   This  further requires that each
client know the secret to be used with each  server,  but  it  does  not
provide  any  means  of  securely  transmitting such secrets between the
parties.  Shared secrets can work fine for small groups  where  everyone
is physically co-located; they don't work as well for large or dispersed
communities of users.  Further, if the server  is  compromised  a  large
number  of  secrets may be exposed, which is especially dangerous if the
same secret (or password) is used for several applications.

     TLS is  descended  from  SSL,  which  was  originally  designed  to
authenticate servers to clients - not the other way around.  Even though
TLS now provides mutual authentication, a client that needs to  talk  to
multiple  servers  must  still know which credentials to present to each
server before establishing a secure connection to  the  server.   Client
and  server  must  each  use  private keys that are trusted by the other
party - typically because they are signed  by  a  certificate  authority
(CA)  known  to  the  other.  As in the digest authentication case, both
client and server need  ways  to  protect  their  private  keys  against
exposure.
----


From owner-ietf-calendar@imc.org  Thu Apr  1 16:57:04 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04165
	for <calsch-archive@odin.ietf.org>; Thu, 1 Apr 1999 16:56:55 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA03388
	for ietf-calendar-bks; Thu, 1 Apr 1999 13:09:36 -0800 (PST)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id NAA03384
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 13:09:35 -0800 (PST)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id NAA27576
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 13:09:43 -0800 (PST)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id QAA06360
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 16:11:51 -0500
Message-ID: <3703E117.43433D97@ecal.com>
Date: Thu, 01 Apr 1999 21:11:51 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: Delimiter characters in relativeCalUID
References: <FD7A762E588AD211A7BC00805FFEA54BE8060C@HYDRANT> <36FFE5F1.14A9FF52@netscape.com> <3703BA86.245332F5@netscape.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

John Sun wrote:

> Here are some problems using a '/' to represent calendar hierarchy:
>
> 1) Force the server designer to use a specific calendar hierarchy.

No, it doesn't.  If you don't want a heirarchy, you just make sure you
don't have any '/'s in your calendar IDs.

> 2) Exposes the calendar hierarchy to clients.

Aliases.

Again, I am not saying we should *use* the '/' in CAP1; I just want to
reserve it (or some other character) for use in a hypothetical future
version.  Otherwise, CAP1's calendar IDs will gobble up the entire
namespace, and there won't be any safe way to build a string that
delimits them.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Thu Apr  1 19:46:42 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06537
	for <calsch-archive@odin.ietf.org>; Thu, 1 Apr 1999 19:46:41 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id QAA05176
	for ietf-calendar-bks; Thu, 1 Apr 1999 16:08:22 -0800 (PST)
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id QAA05172
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 16:08:22 -0800 (PST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54])
	by netscape.com (8.8.5/8.8.5) with ESMTP id QAA23951
	for <ietf-calendar@imc.org>; Thu, 1 Apr 1999 16:08:06 -0800 (PST)
Received: from netscape.com ([208.12.60.170]) by dredd.mcom.com
          (Netscape Messaging Server 4.01) with ESMTP id F9JCDI01.MDT;
          Thu, 1 Apr 1999 16:08:06 -0800 
Message-ID: <37040A25.E10383E@netscape.com>
Date: Thu, 01 Apr 1999 16:07:01 -0800
From: sman@netscape.com (Steve Mansour)
Organization: Netscape
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John Stracke <francis@ecal.com>
CC: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: Delimiter characters in relativeCalUID
References: <FD7A762E588AD211A7BC00805FFEA54BE8060C@HYDRANT> <36FFE5F1.14A9FF52@netscape.com> <3703BA86.245332F5@netscape.com> <3703E117.43433D97@ecal.com>
Content-Type: multipart/mixed;
 boundary="------------E984A506F847919F277B2208"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------E984A506F847919F277B2208
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

John Stracke wrote:

> John Sun wrote:
>
> > Here are some problems using a '/' to represent calendar hierarchy:
> >
> > 1) Force the server designer to use a specific calendar hierarchy.
>
> No, it doesn't.  If you don't want a heirarchy, you just make sure you
> don't have any '/'s in your calendar IDs.

The only concern I would have about making that sort of a claim is that it
will cause interoperability problems for mixing and matching clients and
servers. For example, one client thinks that the '/' means hierarchy. The
server it talks to assigns no special meaning to '/'.

> > 2) Exposes the calendar hierarchy to clients.
>
> Aliases.
>
> Again, I am not saying we should *use* the '/' in CAP1; I just want to
> reserve it (or some other character) for use in a hypothetical future
> version.  Otherwise, CAP1's calendar IDs will gobble up the entire
> namespace, and there won't be any safe way to build a string that
> delimits them.

This is a slippery slope. Either they are an opaque string or they are
not.  If we start by making it an opaque string and add semantics later we
will almost certainly encounter problems.

-Steve

--------------E984A506F847919F277B2208
Content-Type: text/x-vcard; charset=us-ascii;
 name="sman.vcf"
Content-Description: Card for Steve Mansour
Content-Disposition: attachment;
 filename="sman.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Mansour;Steve
tel;fax:650.937.2103
tel;work:650.937.2378
x-mozilla-html:FALSE
org:Netscape
adr:version:2.1;;;;;;
version:2.1
email;internet:sman@netscape.com
title:Judge, Jury, and Executioner
fn:Steve Mansour
end:vcard

--------------E984A506F847919F277B2208--



From owner-ietf-calendar@imc.org  Fri Apr  2 14:14:10 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01989
	for <calsch-archive@odin.ietf.org>; Fri, 2 Apr 1999 14:14:09 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id KAA13078
	for ietf-calendar-bks; Fri, 2 Apr 1999 10:32:38 -0800 (PST)
Received: from mail1.microsoft.com (mail1.microsoft.com [131.107.3.125])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id KAA13074
	for <ietf-calendar@imc.org>; Fri, 2 Apr 1999 10:32:37 -0800 (PST)
Received: by INET-IMC-01 with Internet Mail Service (5.5.2524.0)
	id <2AH85GCF>; Wed, 31 Mar 1999 14:09:13 -0800
Message-ID: <CB6657D3A5E0D111A97700805FFE65870B48E02F@RED-MSG-51>
From: Paul Leach <paulle@microsoft.com>
To: "Larry Osterman (Exchange)" <larryo@Exchange.Microsoft.com>,
        "'Doug Royer'" <Doug.Royer@Sun.COM>, ietf-calendar@imc.org
Subject: RE: Some Text on Security
Date: Wed, 31 Mar 1999 14:09:08 -0800
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

Digest/SASL is the MTI for LDAP and DAV, and is getting wide use in mail
protocols -- there were three independent implementations that interop
tested at the last IMC interop-a-thon.

The combination of mail (SMTP, IMAP, POP, NNTP, IMSP, ACAP), directory
(LDAP) and WEB (HTTP, DAV) use of Digest gives it powerful momentum.

For those who have to administer environments that support all three
families, and all 9 protocols, the attraction of not having 9 different
authentication protocol databases to administer should be obvious.

Today, the only authentication protocol that seems to have that potential is
Digest.

It's also easy to implement, and a public implementation exists. See
<ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/>.

> -----Original Message-----
> From: Larry Osterman (Exchange) 
> Sent: Wednesday, March 31, 1999 12:19 PM
> To: 'Doug Royer'; ietf-calendar@imc.org
> Cc: Paul Leach
> Subject: RE: Some Text on Security
> 
> 
> Ok, I'll try sell it.  HTTP-DIGEST is a SASL-ized version of 
> the HTTP DIGEST authentication mechanism.  As such, any 
> server/client software that has support for HTTP 
> authentication will already have logic in it that's suitable 
> for packaging up for HTTP-DIGEST.  It's my understanding that 
> a bunch of the IETF protocols are moving to DIGEST as their 
> must-implement authentication mechanism.  The only other 
> competing mechanisms that I'm aware of are:
> 
> 	PLAIN (but only under TLS due to IESG no plaintext rules)
> 	CRAM-MD5 (plain text equivilant, but cannot requires a 
> server-side authentication database that is NOT interoperable 
> with other server side databases)
> 	GSS-SPNEGO - Requires that the client and server use GSSAPI.
> 
> Paul's the author, he can speak much more eloquently than I 
> could about it.
> 
> -----Original Message-----
> From: Doug Royer [mailto:Doug.Royer@Sun.COM]
> Sent: Monday, March 29, 1999 6:46 PM
> To: ietf-calendar@imc.org
> Subject: RE: Some Text on Security
> 
> 
> 
> > From: "Larry Osterman (Exchange)" <larryo@Exchange.Microsoft.com>
> > Date: Mon, 29 Mar 1999 18:29:38 -0800
> > 
> > I suspect that SASL is a MUST implement for the calendering 
> protocols, the
> > only issue is really what SASL mechanisms are mandated as manditory,
> 
> I agree 'I' think that SASL is a MUST.
> 
> >    and I'd
> > guess that the HTTP-DIGEST authentication mechanism is the 
> most likely
> > choice for a must-implement mechanism.
> 
> Why? - as in "Sell it"
> 
> -Doug
> -------------------------------------------------------------------
> Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
> 801 W. El Camino #131		Work:   (650)786-7599
> Mountain View, CA 94040		Ham Radio: N6AAW, 
> Aviation: PP-ASEL
> 


From owner-ietf-calendar@imc.org  Fri Apr  2 17:55:05 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08041
	for <calsch-archive@odin.ietf.org>; Fri, 2 Apr 1999 17:55:04 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id MAA13763
	for ietf-calendar-bks; Fri, 2 Apr 1999 12:07:31 -0800 (PST)
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id MAA13751
	for <ietf-calendar@imc.org>; Fri, 2 Apr 1999 12:06:48 -0800 (PST)
Received: from tintin.mcom.com (tintin.mcom.com [205.217.233.42])
	by netscape.com (8.8.5/8.8.5) with ESMTP id MAA05108
	for <ietf-calendar@imc.org>; Fri, 2 Apr 1999 12:06:27 -0800 (PST)
Received: from netscape.com ([208.12.61.78]) by tintin.mcom.com
          (Netscape Messaging Server 4.03) with ESMTP id F9KVV300.LWL for
          <ietf-calendar@imc.org>; Fri, 2 Apr 1999 12:06:39 -0800 
Message-ID: <3705237F.9BA012CD@netscape.com>
Date: Fri, 02 Apr 1999 12:07:27 -0800
From: rans@netscape.com (Richard Shusterman)
Organization: Netscape Communications Corp.
X-Mailer: Mozilla 4.5 [en]C-NSCP  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: calsch WG <ietf-calendar@imc.org>
Subject: Re: Delimiter characters in relativeCalUID
References: <FD7A762E588AD211A7BC00805FFEA54BE8060C@HYDRANT> <36FFE5F1.14A9FF52@netscape.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Steve Mansour wrote:

> OK. Let's put this point to the test. Should we introduce one or more delimiter
> characters into relativeCalUID or should it be an opaque string?  Speak up.
>

Maybe I'll get the last word on this subject :)

I looked over rfc 2396 (defines URI) and it already recommends the following:

- Reserved Characters (see section 2.2)
- Unreserved Characters (see section 2.3)
- Excluded US-ASCII Characters (see section 2.4.3)

Note that "/" is in the list of recommended reserved characters and <CR><LF> in
excluded characters. It also mentions that these lists of reserved characters,
unreserved characters, and excluded characters as well as hierarchy and case
sensitivity are left up to the definition of the URI schemes.

As Bruce pointed out, I think there is a good argument for definining this grouping
of characters (reserved, unreserved, and excluded) for both iRIP and CAP. This will
allow for simpler URI parsers and avoid interoperability problems between
implementations. As for charset, this rfc says "in the simplest case, the original
character sequence contains only characters that are defined in US-ASCII" and that
"it is expected that a systematic treatment of character encoding within URI will
be developed as a future modification of this specification. Using the KISS
philosophy, we should stick to the US-ASCII charset for our URI schemes.

As for delimiter characters, this is not needed since we already have parent/child
properties of a calendar. As Doug pointed out, it is a security hole to allow
parent/child relationships in URI names, which bypasses the security checks that
protect the parent/child properties of a calendar.

We should not confuse the publishing of calendars as documents (or files) with
referencing calendars in iRIP or CAP. In a document URI scheme like http://, it
makes sense to navigate a file system using the URI name. However, it would be a
mistake to imply that an iRIP or CAP server implements a file system hierarchy for
navigating it's calendars. More than likely, these servers will use databases to
store these calendars. If a client needs to discover it's children or parent, it
should request and receive (subject to access control) the calendar properties
associated with the URI.

I propose that the iRIP and CAP editors tighten up their definitions of
relativeCALID to include a list of reserved characters, unreserved characters, and
excluded characters, to specify US-ASCII as the only charset for relativeCALID, and
that no hierarchy or case sensitivity is required in a relativeCALID.

Richard



From owner-ietf-calendar@imc.org  Fri Apr  2 21:37:47 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18062
	for <calsch-archive@odin.ietf.org>; Fri, 2 Apr 1999 21:37:47 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id SAA16185
	for ietf-calendar-bks; Fri, 2 Apr 1999 18:03:49 -0800 (PST)
Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id SAA16180
	for <ietf-calendar@imc.org>; Fri, 2 Apr 1999 18:03:44 -0800 (PST)
Received: from tintin.mcom.com (tintin.mcom.com [205.217.233.42])
	by netscape.com (8.8.5/8.8.5) with ESMTP id SAA26694
	for <ietf-calendar@imc.org>; Fri, 2 Apr 1999 18:03:34 -0800 (PST)
Received: from netscape.com ([208.12.61.78]) by tintin.mcom.com
          (Netscape Messaging Server 4.03) with ESMTP id F9LCEA00.PY1 for
          <ietf-calendar@imc.org>; Fri, 2 Apr 1999 18:03:46 -0800 
Message-ID: <3705772F.5FD716EE@netscape.com>
Date: Fri, 02 Apr 1999 18:04:31 -0800
From: rans@netscape.com (Richard Shusterman)
Organization: Netscape Communications Corp.
X-Mailer: Mozilla 4.5 [en]C-NSCP  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: CalSched IETF <ietf-calendar@imc.org>
Subject: Re: Latest CAP examples available on IMC Website
References: <36F80B09.7D577677@netscape.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

As Steve points out, examples are a good way to flush out issues. If this WG
hopes to have a useable draft of CAP by the next IETF meeting, we need to
flush out more issues and create more examples. Here is a partial list of
examples that I think we (as a WG) need to post:

- AUTHENTICATE anonymously
- AUTHENTICATE as a specific user
- Get CAPABILITY of a CS
- (already posted) CREATE VCALENDARs with RELCALUIDs
- (already posted) CREATE VCALENDARs without RELCALUIDs
- CREATE VEVENT across multiple VCALENDARs
- CREATE a VCAR in a VCALENDAR
- DELETE VCALENDAR
- DELETE VEVENT
- DELETE VEVENT properties
- READ VCALENDAR to obtain a list of all top level VCALENDARs
- READ VCALENDAR properties for a VCALENDAR
- READ VTIMEZONEs for a VCALENDAR
- READ VCARs for a VCALENDAR
- READ the parent and all the children of a VCALENDAR
- (already posted) READ VEVENTs for a specific time range
- READ VEVENT for a specific UID
- READ VEVENTs that have a VALARM for a specified time range
- MODIFY VCALENDAR properties
- MODIFY the ATTENDEE properties in a VEVENT
- MODIFY the DTSTART and DTEND properties of a VEVENT
- MODIFY an inline ATTACH property
- MODIFY a single recurring VEVENT
- CANCEL, ABORT, and DISCONNECT

Sometime next week, I hope to post my attempts at some of these examples.
Any other volunteers?

Steve Mansour wrote:

> Folks,
>
> Thanks to Paul Hoffman, we now have a repository for our CAP examples:
> http://www.imc.org/ietf-calendar/cap-examples/
>
> The latest versions of the examples are posted. Alex Taler helped with
> adding comments and cleaning them up. I'll update this site
> periodically.
>
> I hope we can add a lot more soon. It seems like this is a good way to
> flush out issues with everyone's involvement.
>
> If you have any examples you'd like to propose (or better yet, type up),
> please send them to the list.
>
> -Steve



From owner-ietf-calendar@imc.org  Sat Apr  3 16:33:44 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05047
	for <calsch-archive@odin.ietf.org>; Sat, 3 Apr 1999 16:33:44 -0500 (EST)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA27113
	for ietf-calendar-bks; Sat, 3 Apr 1999 13:04:25 -0800 (PST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id NAA27109
	for <ietf-calendar@imc.org>; Sat, 3 Apr 1999 13:04:23 -0800 (PST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA21032;
	Sat, 3 Apr 1999 13:04:49 -0800 (PST)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id NAA12348;
	Sat, 3 Apr 1999 13:04:40 -0800 (PST)
Message-Id: <199904032104.NAA12348@engmail2.Eng.Sun.COM>
Date: Sat, 3 Apr 1999 13:04:41 -0800 (PST)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: RE: Some Text on Security
To: ietf-calendar@imc.org
Cc: paulle@microsoft.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: kA1C0hAcTrvWiwE1bKfCRg==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


Thanks.

> From: "Larry Osterman (Exchange)" <larryo@exchange.microsoft.com>
> Date: Wed, 31 Mar 1999 12:18:55 -0800
> 
> Ok, I'll try sell it.  HTTP-DIGEST is a SASL-ized version of the HTTP DIGEST
> authentication mechanism.  As such, any server/client software that has
> support for HTTP authentication will already have logic in it that's
> suitable for packaging up for HTTP-DIGEST.  It's my understanding that a
> bunch of the IETF protocols are moving to DIGEST as their must-implement
> authentication mechanism.

Which ones ? - I'll read up on it.
 
> The only other competing mechanisms that I'm
> aware of are:
> 
> 	PLAIN (but only under TLS due to IESG no plaintext rules)
> 	CRAM-MD5 (plain text equivilant, but cannot requires a server-side
> authentication database that is NOT interoperable with other server side
> databases)
> 	GSS-SPNEGO - Requires that the client and server use GSSAPI.

> Paul's the author, he can speak much more eloquently than I could about it.
> 
> -----Original Message-----
> From: Doug Royer [mailto:Doug.Royer@Sun.COM]
> Sent: Monday, March 29, 1999 6:46 PM
> To: ietf-calendar@imc.org
> Subject: RE: Some Text on Security
> 
> 
> 
> > From: "Larry Osterman (Exchange)" <larryo@Exchange.Microsoft.com>
> > Date: Mon, 29 Mar 1999 18:29:38 -0800
> > 
> > I suspect that SASL is a MUST implement for the calendering protocols, the
> > only issue is really what SASL mechanisms are mandated as manditory,
> 
> I agree 'I' think that SASL is a MUST.
> 
> >    and I'd
> > guess that the HTTP-DIGEST authentication mechanism is the most likely
> > choice for a must-implement mechanism.
> 
> Why? - as in "Sell it"
> 
> -Doug
> -------------------------------------------------------------------
> Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
> 801 W. El Camino #131		Work:   (650)786-7599
> Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Sun Apr  4 11:25:32 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12333
	for <calsch-archive@odin.ietf.org>; Sun, 4 Apr 1999 11:25:31 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id HAA27498
	for ietf-calendar-bks; Sun, 4 Apr 1999 07:50:30 -0700 (PDT)
Received: from komarr.local.thibault.org (adsl-151-197-16-76.bellatlantic.net [151.197.16.76])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id HAA27490
	for <ietf-calendar@imc.org>; Sun, 4 Apr 1999 07:50:28 -0700 (PDT)
Received: from ariel.local.thibault.org (ariel.local.thibault.org [192.168.10.18])
	by komarr.local.thibault.org (8.8.7/8.8.7) with ESMTP id KAA19912
	for <ietf-calendar@imc.org>; Sun, 4 Apr 1999 10:50:38 -0400
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.local.thibault.org (8.8.7/8.8.7) with ESMTP id KAA29965
	for <ietf-calendar@imc.org>; Sun, 4 Apr 1999 10:52:35 -0400
Message-ID: <37077CB3.A54ED86F@ecal.com>
Date: Sun, 04 Apr 1999 14:52:35 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Heirarchical error codes
References: <199903292249.OAA21325@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer wrote:

> > Date: Mon, 29 Mar 1999 19:44:43 +0000
> > From: John Stracke <francis@ecal.com>
> >
> > Frank Dawson wrote:
> >
> > > What scenario did you have in mind that necessitated the CUA to also specify
> > > it's capabilities?
> >
> > "I cannot render non-Latin1 text"?
>
> As there were not any Latin1 text messages defined,
> I am not sure what your need is.

There's human-composed, user-visible text in the message, which means that the CUA
needs to consider whether the user is going to be able to read the incoming
message.  An advanced CS might be capable of storing multiple versions of the text,
and picking out the one to send to the CUA--but only if it can find out what
languages the user can read, and what character sets the CUA can display.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Sun Apr  4 17:42:13 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14023
	for <calsch-archive@odin.ietf.org>; Sun, 4 Apr 1999 17:42:12 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA01843
	for ietf-calendar-bks; Sun, 4 Apr 1999 14:09:51 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id OAA01839
	for <ietf-calendar@imc.org>; Sun, 4 Apr 1999 14:09:50 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA01487
	for <ietf-calendar@imc.org>; Sun, 4 Apr 1999 14:10:24 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id OAA11043
	for <ietf-calendar@imc.org>; Sun, 4 Apr 1999 14:10:10 -0700 (PDT)
Message-Id: <199904042110.OAA11043@engmail2.Eng.Sun.COM>
Date: Sun, 4 Apr 1999 14:10:12 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: Heirarchical error codes
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: gFYSqxa7gBf1GBLnk8eUbA==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> Date: Sun, 04 Apr 1999 14:52:35 +0000
> From: John Stracke <francis@ecal.com>
> 
> Doug Royer wrote:
> 
> > > Date: Mon, 29 Mar 1999 19:44:43 +0000
> > > From: John Stracke <francis@ecal.com>
> > >
> > > Frank Dawson wrote:
> > >
> > > > What scenario did you have in mind that necessitated the CUA to also 
specify
> > > > it's capabilities?
> > >
> > > "I cannot render non-Latin1 text"?
> >
> > As there were not any Latin1 text messages defined,
> > I am not sure what your need is.
> 
> There's human-composed, user-visible text in the message, which means that
> the CUA needs to consider whether the user is going to be able to read the
> incoming message.  An advanced CS might be capable of storing multiple
> versions of the text, and picking out the one to send to the CUA--but only
> if it can find out what languages the user can read, and what character
> sets the CUA can display.

The iCalendar object default charset is UTF-8. 

I would hope that a CS should be able to charset convert to UTF-8 on
the way in or out of the CS. I would also hope that all CUAs MUST be
able to handle UTF-8.

As for languages, there is no way to store multiple LANG 'DESCRIPTION'
or 'SUMMARY'.

I think the best that can occur is if all CUAs MUST be able to handle
UTF-8, and they must ask for anything other than UTF-8. A user might
not be able to understand the text as sent to the CS, but the CUA MUST
be able to understand the UTF-8 text.


-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Mon Apr  5 12:38:26 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10169
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 12:38:26 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id JAA27708
	for ietf-calendar-bks; Mon, 5 Apr 1999 09:02:35 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id JAA27702
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 09:02:32 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id JAA08516
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 09:03:00 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id MAA00728
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 12:05:18 -0400
Message-ID: <3708DF3E.E554F8AA@ecal.com>
Date: Mon, 05 Apr 1999 16:05:18 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
Subject: Re: Delimiter characters in relativeCalUID
References: <FD7A762E588AD211A7BC00805FFEA54BE8060C@HYDRANT> <36FFE5F1.14A9FF52@netscape.com> <3703BA86.245332F5@netscape.com> <3703E117.43433D97@ecal.com> <37040A25.E10383E@netscape.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Steve Mansour wrote:

> John Stracke wrote:
>
> > No, it doesn't.  If you don't want a heirarchy, you just make sure you
> > don't have any '/'s in your calendar IDs.
>
> The only concern I would have about making that sort of a claim is that it
> will cause interoperability problems for mixing and matching clients and
> servers. For example, one client thinks that the '/' means hierarchy. The
> server it talks to assigns no special meaning to '/'.

That is exactly the kind of interop problem that I'm trying to *prevent*.  At
some time in the future, somebody will want to have an ID string with
heirarchy in it, and it's going to be easier if we don't grab the entire
namespace now.

> This is a slippery slope. Either they are an opaque string or they are
> not.  If we start by making it an opaque string and add semantics later we
> will almost certainly encounter problems.

My point exactly.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Mon Apr  5 12:43:04 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10283
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 12:43:04 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id JAA27922
	for ietf-calendar-bks; Mon, 5 Apr 1999 09:07:27 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id JAA27917
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 09:07:26 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id JAA09165
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 09:07:54 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id MAA00738
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 12:10:12 -0400
Message-ID: <3708E063.641C5379@ecal.com>
Date: Mon, 05 Apr 1999 16:10:11 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: CUA capabilities (was Re: Heirarchical error codes)
References: <199904042110.OAA11043@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

(Clarification: when I referred to Latin1 text, I didn't mean the encoding, I
meant the characters themselves, regardless of how they're encoded.)

Doug Royer wrote:

> As for languages, there is no way to store multiple LANG 'DESCRIPTION'
> or 'SUMMARY'.

(a) Sure there is--the protocol may not specify a way to transport them, but
you can store whatever you want.

(b) I suspect that iMIP might be able to express it with multipart/alternative
(you wouldn't necessarily want to send it to someone unless you know they can
handle it, since m/a isn't a mandatory part of MIME; but it can be done).

> A user might
> not be able to understand the text as sent to the CS, but the CUA MUST
> be able to understand the UTF-8 text.

Not going to happen--the CUA can handle it internally, sure, but most of the
computers in the world simply do not have the fonts to render every single
character in Unicode.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Mon Apr  5 14:57:40 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13454
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 14:57:39 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id LAA03784
	for ietf-calendar-bks; Mon, 5 Apr 1999 11:14:29 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id LAA03778
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 11:14:29 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA03229
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 11:15:00 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id LAA11841
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 11:14:56 -0700 (PDT)
Message-Id: <199904051814.LAA11841@engmail2.Eng.Sun.COM>
Date: Mon, 5 Apr 1999 11:14:57 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: CUA capabilities (was Re: Heirarchical error codes)
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Am1ekpf1Z55EhtVQsTwPMA==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> Date: Mon, 05 Apr 1999 16:10:11 +0000
> From: John Stracke <francis@ecal.com>
> 
> (Clarification: when I referred to Latin1 text, I didn't mean the encoding, I
> meant the characters themselves, regardless of how they're encoded.)
> 
> Doug Royer wrote:
> 
> > As for languages, there is no way to store multiple LANG 'DESCRIPTION'
> > or 'SUMMARY'.
> 
> (a) Sure there is--the protocol may not specify a way to transport them, but
> you can store whatever you want.

True - but that vendor specific extension is not part of a CAP.

> (b) I suspect that iMIP might be able to express it with multipart/alternative
> (you wouldn't necessarily want to send it to someone unless you know they can
> handle it, since m/a isn't a mandatory part of MIME; but it can be done).

They better not have the same UID, or I might keep replacing the
last one found as the newest one.

> > A user might
> > not be able to understand the text as sent to the CS, but the CUA MUST
> > be able to understand the UTF-8 text.
> 
> Not going to happen--the CUA can handle it internally, sure, but most of the
> computers in the world simply do not have the fonts to render every single
> character in Unicode.

True - but there is no other better choice? And RFC-2445, 2446, and
2447 were written with UTF-8 in mind. A not yet written soon to be 'CAP'
CUA would have to deal with this anyway.

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Mon Apr  5 15:48:35 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14276
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 15:48:34 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id LAA03653
	for ietf-calendar-bks; Mon, 5 Apr 1999 11:11:45 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id LAA03648
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 11:11:45 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA00703
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 11:12:17 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id LAA10974
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 11:12:10 -0700 (PDT)
Message-Id: <199904051812.LAA10974@engmail2.Eng.Sun.COM>
Date: Mon, 5 Apr 1999 11:12:04 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: Delimiter characters in relativeCalUID
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: T2jkvtaPoA9bKN+xpC+Hnw==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> Date: Mon, 05 Apr 1999 16:05:18 +0000
> From: John Stracke <francis@ecal.com>
> >
> > The only concern I would have about making that sort of a claim is that it
> > will cause interoperability problems for mixing and matching clients and
> > servers. For example, one client thinks that the '/' means  The
> > server it talks to assigns no special meaning to '/'.
> 
> That is exactly the kind of interop problem that I'm trying to *prevent*.  At
> some time in the future, somebody will want to have an ID string with
> heirarchy in it, and it's going to be easier if we don't grab the entire
> namespace now.

There is no such namespace. It just looks as if there is one.

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Mon Apr  5 16:32:02 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15109
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 16:32:02 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA07639
	for ietf-calendar-bks; Mon, 5 Apr 1999 13:03:09 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id NAA07635
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 13:03:08 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id NAA03504
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 13:03:37 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id QAA00921
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 16:05:55 -0400
Message-ID: <370917A3.B0B97D92@ecal.com>
Date: Mon, 05 Apr 1999 20:05:55 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Delimiter characters in relativeCalUID
References: <199904051812.LAA10974@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer wrote:

> > That is exactly the kind of interop problem that I'm trying to *prevent*.  At
> > some time in the future, somebody will want to have an ID string with
> > heirarchy in it, and it's going to be easier if we don't grab the entire
> > namespace now.
>
> There is no such namespace. It just looks as if there is one.

How can there be names without a namespace?

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Mon Apr  5 16:38:44 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15215
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 16:38:44 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA07627
	for ietf-calendar-bks; Mon, 5 Apr 1999 13:02:30 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id NAA07623
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 13:02:29 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id NAA03449
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 13:02:57 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id QAA00917
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 16:05:15 -0400
Message-ID: <3709177A.29C5774A@ecal.com>
Date: Mon, 05 Apr 1999 20:05:15 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: CUA capabilities (was Re: Heirarchical error codes)
References: <199904051814.LAA11841@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer wrote:

> > > As for languages, there is no way to store multiple LANG 'DESCRIPTION'
> > > or 'SUMMARY'.
> >
> > (a) Sure there is--the protocol may not specify a way to transport them, but
> > you can store whatever you want.
>
> True - but that vendor specific extension is not part of a CAP.

Storage is not a vendor-specific extension; it's an implementation detail,
orthogonal to the protocol.  The only extension being discussed is the capability
negotiation that would enable the CS to figure out which language variant to
present.

> > (b) I suspect that iMIP might be able to express it with multipart/alternative
> > (you wouldn't necessarily want to send it to someone unless you know they can
> > handle it, since m/a isn't a mandatory part of MIME; but it can be done).
>
> They better not have the same UID, or I might keep replacing the
> last one found as the newest one.

If you don't understand the extension, then that's more or less fine; they're all
equivalent.

> > > A user might
> > > not be able to understand the text as sent to the CS, but the CUA MUST
> > > be able to understand the UTF-8 text.
> >
> > Not going to happen--the CUA can handle it internally, sure, but most of the
> > computers in the world simply do not have the fonts to render every single
> > character in Unicode.
>
> True - but there is no other better choice?

No, there isn't--everything in the world needs to handle Unicode; every iCal-based
solution needs to handle UTF-8--but we should attempt to provide some form of
content negotiation so that users can see languages they understand.

In fact, in some countries, it's probably going to be a requirement.  Consider a CS
that contains a public calendar of music events at Ontario Place.  That information
needs to be available in English and French, and it would be a pain if people had
to configure their CAP client to know which calendar to use to pick the right
language.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Mon Apr  5 17:27:38 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16010
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 17:27:37 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA07951
	for ietf-calendar-bks; Mon, 5 Apr 1999 13:45:38 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id NAA07947
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 13:45:37 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA15712
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 13:46:00 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id NAA17543
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 13:45:48 -0700 (PDT)
Message-Id: <199904052045.NAA17543@engmail2.Eng.Sun.COM>
Date: Mon, 5 Apr 1999 13:45:50 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: Delimiter characters in relativeCalUID
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 17OgEvJ+2Ug5Pr8xhvo+cQ==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> Date: Mon, 05 Apr 1999 20:05:55 +0000
> From: John Stracke <francis@ecal.com>
> 
> Doug Royer wrote:
> 
> > > That is exactly the kind of interop problem that I'm trying to *prevent*.  
At
> > > some time in the future, somebody will want to have an ID string with
> > > heirarchy in it, and it's going to be easier if we don't grab the entire
> > > namespace now.
> >
> > There is no such namespace. It just looks as if there is one.
> 
> How can there be names without a namespace?

My name is Doug Royer, My Calendar name is "Doug Royer" whats the namespace
for that?

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Mon Apr  5 17:55:54 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16445
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 17:55:53 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA08086
	for ietf-calendar-bks; Mon, 5 Apr 1999 14:01:38 -0700 (PDT)
Received: from cdc.net (server1.cdc.net [207.244.0.12])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id OAA08082
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 14:01:37 -0700 (PDT)
Received: (qmail 3357 invoked from network); 5 Apr 1999 21:02:08 -0000
Received: from unknown (HELO egenconsulting.com) (207.244.42.65)
  by server1.cdc.net with SMTP; 5 Apr 1999 21:02:08 -0000
Message-ID: <370924EC.85DA61CB@egenconsulting.com>
Date: Mon, 05 Apr 1999 17:02:37 -0400
From: Pat Egen <pregen@egenconsulting.com>
Reply-To: pregen@egenconsulting.com
Organization: Egen Consulting
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: IETF Calendaring & Scheduling Mail List <ietf-calendar@imc.org>
Subject: Minutes of 44th IETF CALSCH sessions
Content-Type: multipart/mixed; boundary="------------FBB944EA4F66A5BDF51FD6EF"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------FBB944EA4F66A5BDF51FD6EF
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

CALSCH Working Group minutes:
Session on 15-Mar-99, 3:30PM - 5:30PM

Agenda:
   Assign Volunteer Scribe: Alex Taler of CS&T and Bruce Kahn of Iris
   CAP Requirements: WG last call status
   XML/ICAL syntax resolution
   iRIP Update
   iTIP Identified issues/defects
   CAP Design Group status update

As of now, rough consensus on XML vs iCal is to stick w/iCal for
syntax.  In the future we may consider moving to XML.
After delta changes to CAP Requirements are in, it will not go to RFC
but kept for historical reasons
IRIP discussion: Steve Manseur & Andre Courtemanche.
Issues from IETF 43:
- Resolved queuing issues in new draft
- Editorial fixes
- Revised draft to list

Remaining issues:
- Overlap between iRIP and CAP:
- Keep similar syntaxes so can sub/super set features.  Uses are still
semi-disparate. Need to get feedback from Steve M on how to best
differentiate them!
- Request & responses are now tagged so can do > 1 request/response at a
time
- Fan out response in multiple MIME blocks so data won’t have to be
merged into 1 block.  Now each CalID will return separate MIME block(s)

Authentication/security Issues:
- Trusted relationship between iRIP servers not sufficient. Will want to
borrow CAP authentication info/schema to reuse it.
- May need to authenticate users as opposed to calendars; a new concept
for us.
- Others to be posted to the list

New Editorial issues based on new draft
- Will try to keep CAP and iRIP similar features in sync as they
progress

Next steps:
- New draft by next IETF and one by 15-Apr-99.
- Track CAP progress

iTIP & iMIP Defects:  Steve M. & Frank Dawson
- These solutions will be submitted to revise iTIP drafts.

Overloading iTIP REQUEST:
- Current method used for invite, reschedule, update, confirm, reply to
refresh.  A reschedule and/or update are semantically different than
confirm or Reply to REFRESH
- Propose: New CONFIRM method to be used to (a) reply to a REFRESH and
(b) notify participants of any changes to ATTENDEE or ORGANIZER.  All
other “reschedule” or “update” changes MUST use REQUEST method.

Identify sender of iTIP COUNTER:
- Can’t identify who COUNTER came from because all of the ATTENDEEs will
appear in the method.
- Propose: Only specify ORGANIZER and countering ATTENDEE in method.
- Caveat: Can still forward or delegate a REQUEST to change
participants. However, only the ORGANIZER can remove a participant.;
This removes functionality and can be done w/an iMIP header but won’t
work for all iTIP.  Will revisit how to best do this on the list.

Intolerant iMIP receiver:
- iMIP specifies numerous MIME encapsulations for iCal/iTIP msgs.  It
doesn’t   require that an implementation MUST be able to receive each of
them.  This is leading to interop problems w/different CUAs.
- Propose: A conforming iMIP implementation MUST be able to receive each
of the MIME encapsulations shown in the iMIP examples.;  It does not
have to GENERATE them, just RECEIVE them!  Why not just use multipart
alternative instead of multipart mixed.  A minimal MIME compliant mailer
must grok multipart mime so this may be moot.

Adding/deleting ATTENDEE:
- If ORGANIZER adds or deletes an ATTENDEE, do they really have to send
the reschedule to all of the other ATTENDEEs?
- Propose: No, they can send the REQUEST w/the new ATTENDEE info to just
the new ATTENDEE.  It is up to the CUA.  It is an implementation
dependent issue if the SEQUENCE number needs to be incremented when you
add/delete an ATTENDEE.;  iCal does not require SEQUENCE rev if a new
ATTENDEE is added so this wont break iCal or cause a revision there.

CAP Design Group: Frank Dawson

Tomorrows session will be tutorial on what the design group and the list
have been working on.

Topics:
     Status of interim work
     Proposed schedule for work in 99
     CAP design summary (Continued tomorrow)
Design Goals:
     Leverage iCal and iTIP work
     Design to CAP Reqs doc
     Validate reqs wherever possible;
     Some deferred stuff was pulled in (ie VCARs) based on WG list
feedback.
     Keep list active in providing feedback and consensus (instead of
“telling”
      them what the WG will accept)
     Submit draft for July IETF mtg

Activities:
- 2 interim meetings: NYC 2/99 @ Morgan Stanley & Menlo Park 3/99 @ Sun
- Identified design approach for CAP data model, addressing, system
model, state diagram, query, calendar access rights and command set
- Changes to reqs doc (moving in access rights, server fan out, the
concept of a ‘user’)
- Need to gain closure on transport
- Poll of audience shows about 25% to 33% of the folks are new to
CalSched so we went over the data and system model.

Data Model:
     CS (calendar Store):
        vTZs (timezones)
        Properties (CS owners authids, CS’s local time or time info,
etc)
        vCARs (access rights)
        Calendar(s):
          Calendar(s)
          Calendar Properties ()
          vCARs
          vEvents
             vAlarms
          vTodos
             vAlarms
          vJournals

Questions from the floor and answers:
Calendars can have Calendars within them and the “parent” of the ‘top’
one has the CS as its parent. CS is what the CUA connects to. What is
meaning of “sub calendars”?:  Use inheritance of vCARs from parents, etc
to see what access a user has.

Does naming imply hierarchy (ie: subcalendars vs parents):  Calendars
addresses) have opaque names and hierarchy is NOT based on any schema of
the CALID format so no, no implications!  Names are just pretty human
readable indicators for reference.

What is use of “sub calendars”: To emulate how people organize their
time, or other info.  For example, my “soccer” calendar and my “work”
calendar can be subcalendars of my main calendar.  Other examples are
parent calendar of a building and then subcalendars of resources in it.
This model is a relationship model, not a storage model for data.

vCARs are inherited down but info is NOT inherited up!!  There are lots
of client side and undiscovered issues to consider still. Needs to be
thought out more and covered on the list!

Should multi-value PARENT properties be allowed?  There are inheritance
issues to consider WRT vCARs before just saying yes.  There are also
issues of having ‘split’ or disparate stores that contain the sub
calendars (ie: Kids store on the ISP and my store at work!)

Would aliases for calendars be useful?  What about mulitple personas?
This can have/require multiple authIDs and names, etc to pull together.

Can CAP be used by 1 CUA to access > 1 CS at a time?  Yep.

Is Group calendar support something to pull into initial release too? Is
it necessary in the protocol or can it be done by CUA?  Group Calendar =
aggregate > 1 calendar into 1.  VCARs could be used to emulate this but
its ugly!  An aggregate calendar could be an actual calendar instead of
just an aggregate one... This needs to be taken to the list too.

CAP Addressing Model:
     A CalUID conforming to RFC 1738:
        caluid = [<scheme>://[csid][:<port]/]<relativeCalUID>
        <scheme> = “cap”
        <relativeCalUID> = < any 7bit UIS-ASCII identifier>
     Examples:
        cap://calendar.example.com/user1
        user1 (relative to the CS; equivalent to the one above)
        cap://calendar.example.com/conferenceRoomA
        cap://calendar.example.com/923345346-foo
     RFC 1738 obsoleted by ~RFC 2368 CAP System Model:

Internet SMTP/MIME + iTIP is really CUA <-> CUA but it could be CS->CUA
as well. iMIP could be used between CS1 and CS2 but then its addressing
CS2, not CUA 2 Need to clarify what is mandatory and what is not in the
model.

Fan out IS a requirement of CAP now.

CAP between CS1 and CS2: If CS acts as CUA then is it Fan out or not?
Isn't this just a requirement for a fatter CS?  If iMIP is a requirement
then why is CAP between CS’s of any use (if there is no authentication
between all CS’s)?

There was lots of discussion on this that will be brought up on the
list.

The State Diagram was drawn.

Questions from the floor and answers:

What good is CAPABILITY in RTS state?  Why not...  Its nonsensical in
this mode as a CUA should have up front checks not ‘spur of the moment’.

What is the use of CONTINUEs?  To handled bounded latency issues.
Latency is not that bad on low latency intranets but can be larger on
internet due to routers, etc.  Clients on high latency connections will
want to avoid the RTS state.

Missing assorted links in diagram from last revision.  Frank to revise
based on notes from last 2 interim meetings.

Need comment on how to handle tagging and multithreading, etc. Could be
problems w/queued requests and reauthentcation, etc.

Next, there was a description of a Query:

     Based on SQL clause/statements
     Specified in a VQUERY component
     Example:
        BEGIN:VQUERY
        QUERYID:Read today’s event
        QUERY: Select=UID,DTSTAT,DTEND,SUMMARY;FROM=VEVENT;Where=DTEND
>=
          19990315T143000Z and DTSTART <= 19990315233000Z;
orderby=dtstart
          asc, dtend, summary, uid
        END:vQUERY

Question/Answers:

Why is it not just SQL?  We already have concept of name=value so use
it.  Still, why just not use SQL?? Don't want to get raw SQL data that
doesn't map 100% to iCal.  Stuff in SQL may not be desirable now (ie:
weighting of results) but may want later.  If we use SQL syntax then we
gain an already understood behavior;  We just didn't want to get the
mods that we’d have to make to avoid non-doable stuff (ie: “today”);
There could be problems w/vendor extensions of SQL that dont interop so
a strict separate syntax prevents that. Revisit on the list (did in Dec
98 but no responses). Pat asked for feedback on the list.

Calendar Access Rights:

Need to decide on the granularity of the CARs; property level, entry
level, etc.

Specified calendar access for: Given authenticated calendar user
(PRINCIPAL) and either: Particular calendar access policy (POLICY) or;
Particular set of calendar operations (ACTION), Relation to a set of
calendar components, calendar properties, component properties, property
parameters (OBJECT), Particular property or parameter values (VALUE).

Specified in vCAR calendar component
No rights assumed; must be given them!  There is no way to revoke rights
(yet?)  Need feedback on  how to manage this.

Can I set VCARs that say “Frank can only edit my calendar between 3/15
and 3/19”?  You can filter based on property values but not for this
case in particular.  Suggestion was it could be attempted using ROLEs.

Example:
        BEGIN:VCAR
        CARID:Read public events
        GRANT: PRINCIPAL=foo;ACTION=READ;OBJECT=VEVENT
        DENY:PRINCIPAL=foo;ACTION=READ;OBJECT=CLASS;VALUE=Private,
        Confidential
        END:VCAR

This example grants public R access to all docs and revokes access to
Private or Confidential CLASS valued items How can I create a VCAR that
prevents FOO from reading the CLASS: property?

How about: DENY:PRINCIPAL=foo;ACTION=*;OBJECT=CLASS

Can a properties value be used to govern a vCAR?  Yes.  Unclear how this
is
different from above except the missing VALUE=;

What about adding a new SCOPE parameter to target the scale to filter
out: property, doc, etc

How about a SCOPE property for the right (all components, etc)??

Do we want to add expressions to build “Give Frank Access from 3/15/to
3/19” to the VCARs?  What about adding ranges of values, etc.??.. Take
to list as we need more input on this.  This will be done by Tony Small.


Policy support is mandatory, Grammar is optional. Assorted proposals
will be posted to list with indicator as to status within the WG (ie:
draft, proposed for CAP v1, etc).

CAP Command Format:
     CUA command request format:
        <label> <command> [<command data>]
     CS command response format:
        <label> <response code> [<response data>]
     Example
        C: 10 Create VCALENDAR cap://cal.foo.com/
        S: 10 2.0

Are labels required??  Take to list about tagging.

Proposed Sched of Work for 1999:
     2 final interim mtgs (will be announced on the list)
        4/27 & 28 Lotus (Atlanta)
        6/8 & 9 CS&T (Montreal)

Produce CAP draft by 45th IETF cut off date Next IETF mtg and later.
Review/comment on CAP v1

The Area Director informed us to be careful with our interim meetings.
All discussions should also be on the list.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Tuesday, 16-Mar-1999, 1:15PM - 2:15 PM

Agenda:
   CAP Design Status continuation
   Transport issues

Recap of yesterday: Frank D. & Pat Egen

Several design examples were presented. The command list was shown:
abort, authenticate, capability, continue, create, delete (permanent
(tombstone properties are available)) disconnect, generatedUID (server
generates (globally?) unique id for a client), modify, move (optional)
move a calendar,      NOOP, READ, senddata

There are lots of latent issues w/tombstones and/or not...  Need to
request additional feedback from list on their use or not.

CREATE Sample (on cal.example.com):
     Example #1:
     C: 10 CREATE VCALENDAR cap://cal.example.com/ relcal4
://bobo.ex.com
     relcalBoo
     S: 10 6.0 cap://cal.example.com/
     S: 10 2.0 cap://cal.example.com/relcal4
     S: 10 3.1.4 cap://bobo.ex.com/
     S: 10 6.2 cap://cal.example.com/relcalBoo
     C: 10 CREATE VCALENDAR cap://cal.example.com/relcal8 relcal9
     S: 10 3.1.5 cap://cal.example.com/relcal8
     S: 2.0 cap://cal.example.com/relcal9
     C: 10 SENDATA
     S: 10 2.0.1
     C: Content-Type: text/calendar; method=create; component=vCommand
C: Content-Transfer-Encoding: 7bit C:
     C: BEGIN: vCalendar
     C: VERSION:2.1
     C: METHOD: CREATE
     C: BEGIN:vCommand
     C: BEGIN:vCalendar
     C: RELCALUID:relcalZ
     C: NAME;CHARSET=US-ascii;Language=en-us:Bill’s Soccer Team
     C: OWNER:CAPCAR:bill
     C: OWNER:CAPCAR:mary
     C: CALMASTER:mailto:bill@example.com
     C: PREFERRED-TZID: US_PST
     C: BEGIN:VCAR
     C: CARID:12345
     C: GRANT;cn=”Bill
Jones”:principal=capcar:bill;action=all;object=all
     C: GRANT;cn=”Mary
Jones”:principal=capcar:mary;action=read;object=all
     C: END:VCAR
     C: END:VCOMMAND
     C: END:VCALENDAR
     C: .
     S: 10 6.0 cap://cal.example.com/
     S: 10 2.0 cap://cal.example.com/relcal4
cap://cal.example.com/recalZ
     S: 10 3.1.4 cap://bobo.ex.com
     S: 10 6.2 cap://cal.example.com/relcalBoo
     S: 10 3.1.5 cap://cal.example.com/relcal8
     S: 10 7.0 cap://cal.example.com/relcal9

Questions:

Is there a problem w/a variable length entry line (ie: denial of service
attacks)?  Not really if you use CRLF delimitation.  However this
approach is not condusive to tagged data and multithreading in some
ways.

Are numeric response codes good or bad?  The dot notation is good for
expansion but not good for users.  Then again what does 3.6.1.2.6.2.2
mean if I don't grok it??   Using character strings avoids < or >
comparison of values that DRUMS had hassles with.  Some like human
readable formats ie: forbidden.no_auth.  This can be useful for some but
iTIP has a code;explain text;opt arg text format.  Perhaps the response
needs to be more iTIPish.  Use of numbers is consistant w/RFCs for iCal,
iTIP, iMIP.  Take back to list for continued dialog.

Why have tagged commands?  To allow pipelining or batching further down
the line in case we want to add it some day.  There are still some
issues (like w/SWITCH) to be worked out.  Also, the tag is used to match
data w/prior commands (ie SENDATA to all CREATEs).

What about problems like C: 10 CREATE and then C: 10 DELETE and then
C: 10 SENDATA?  Its a problem w/tagging and will revisit.  (Its not IMAP
like tagging, its different!). There are concerns about SENDATA being
atomic and not allowing tagged data to be sent.  Tagging data (unlike
IMAP) could be a performance issue/boost.  Also avoid CRLF.CRLF for data
deliniation so tagging wont crash something else.

The new OWNER property is a TBD propety for handling naming of users.
Paul Hill will be sending draft to list on naming users.

Why use MIME headers that duplicate the actions encoded in the SENDATA?
Its duplication of info so why do it?  Design is just like iTIP that has
info in MIME header and in the data.

The CREATE command does not do the actual creation; its just a probe to
see if it is possible so the CUA can do it or not.  The actual create is
done in the iCal data.  Is this iTIP overhead necessary?  What worked
for iTIP may not be necessary now.  Perhaps rename CREATE to something
more apropo.  Let the list discuss further.

Second BEGIN: VCALENDAR is to indicate what we are creating...  Will
this toss base iCal parsers that do parsing before parameter matching,
checking etc??  Why not use a simple new property like ITEM-TYPE:...??
(Otherwise we violate iCal RFC!)

The reply codes do not jive before and after for some cases like it now
exists when it didnt before.  The intent was to do this.  Add mandatory
“S: final msg” line so client knows when server is done.

What about having a SIZE indicator of some time for the SENDATA command
so CUA can tell CS what is coming so it can allow/reject w/o wasting
time/bandwidth.  Good idea.

What about a different EOD than CRLF.CRLF??  Possible. Ask the list.

Example #2: (Same as #1 but no RELCALID)
     C: 10 CREATE VCALENDAR cap://cal.example.com/ relcal4
://bobo.ex.com
     relcalBoo
     S: 10 6.0 cap://cal.example.com/
     S: 10 2.0 cap://cal.example.com/relcal4
     S: 10 3.1.4 cap://bobo.ex.com/
     S: 10 6.2 cap://cal.example.com/relcalBoo
     C: 10 CREATE VCALENDAR cap://cal.example.com/relcal8 relcal9
     S: 10 3.1.5 cap://cal.example.com/relcal8
     S: 2.0 cap://cal.example.com/relcal9
     C: 10 SENDATA
     S: 10 2.0.1
     C: Content-Type: text/calendar; method=create; component=vCommand
C: Content-Transfer-Encoding: 7bit C:
     C: BEGIN: vCalendar
     C: VERSION:2.1
     C: METHOD: CREATE
     C: BEGIN:vCommand
     C: BEGIN:vCalendar
     C: NAME;CHARSET=US-ascii;Language=en-us:Bill’s Soccer Team
     C: OWNER:CAPCAR:bill
     C: OWNER:CAPCAR:mary
     C: CALMASTER:mailto:bill@example.com
     C: PREFERRED-TZID: US_PST
     C: BEGIN:VCAR
     C: CARID:12345
     C: GRANT;cn=”bill
jones”:principal=capcar:bill;action=all;object=all
     C: GRANT;cn=”Mary
Jones”:principal=capcar:mary;action=read;object=all
     C: END:VCAR
     C: END:VCOMMAND
     C: END:VCALENDAR
     C: .
     S: 10 6.0 cap://cal.example.com/
     S: 10 2.0 cap://cal.example.com/relcal4
     S: 10 3.1.4 cap://bobo.ex.com
     S: 10 6.2 cap://cal.example.com/relcalBoo
     S: 10 3.1.5 cap://cal.example.com/relcal8
     S: 10 7.0 cap://cal.example.com/relcal9
        cap://cal.example.com/rand1234
   READ Command:
     C: 10 READ VEVENT relcal2 ://bobo.ex.com/relcal3
     S: 10 2.0 cap://cal.example.com/relcal2
     S: 10 2.2 cap://bobo.ex.com/relcal3
     C: 10 SENDATA
     S: 10 2.0.1
     C: Content-Type: text/calendar; method=read; compoent=vcommand C:
     C: BEGIN:V
     C: VERISON:2.1
     C: METHOD:READ
     C: BEGIN:VCOMMAND
     C: BEGIN:VQUERY
     C: MAXRESULTS:20
     C: MAXSIZE:17000000
     C: QUERYNAME:MyViewRange
     C: QUERY:SELECT (DTSTART,DTEND,SUMMARY,UID);
     C:  FROM VEVENT;
     C:  WHERE (DTEND >=1999-310T080000Z AND DTSTART <=
19993010T190000Z);
     C:  ORDERBY (DTSTART ASC, DTEND, UID, SUMMARY)
     C: END:VQUERY
     C: END:VCOMMAND
     C: END:VCALENDAR
     C: .
     S: 10 2.0 cap://cal.example.com/relcal2
     S: Content-Type: text/calendar; method=response; component=vdata;
        optinfo=version 2.1 S: C-T-E: 7bit S:
     S: BEGIN:vCalendar
     S:..
     S: end:VCALENDAR
     S: .
     S: 10 2.0 cap://bobo.ex.com/relcal3
     S: Content-Type: text/calendar; method=response; component=vdata;
        optinfo=version 2.1 S: C-T-E: 7bit S:
     S: <MIME data from relcal3>
     S: .

Questions:

Need suggestion on how to get “next 20” if just get 1st 20.  Could add
FIRSTRESULT: to the query and then resubmit it.  Send suggestions to
list (ie LDAPs ways, etc).

Can use same QUERYNAME to reissue w/o resending the QUERY info.  Need to
be careful about namespace collision and possbible security holes.
There are also QUERY permanance issues to consider like how to keep
them.  Are the values persistent or not?  Will follow-up to list.

Is the MAXSIZE per component or for the entire data?  TBD, poll the
list.

The QUERY mechanism is SQL like but not SQL-92.  They are not 100%
interchangeable and SQL is not appropriate so its a mishmash.

Searchings are parametric, not content search.;  Will raise the query
mechanism on the list.  Need to look at the LDAP searching.

Is content searching a requirement of CAP or not?  No but perhaps we
should consider adding it as its an existing feature in C&S apps.

Need to add some way to indicate end of all responses.  Will add
something

Access Rights Notes (Proposal):

Access to some requested properties of an event but not all.  For
example, requestor does not have access to VEVENT.SUMMARY: ... Query
SELECT (DTSTART, DTEND, SUMMARY, UID); ... Responses: ....
RESPOSE-CODE:3.8

We have no way to differentiate between No access to the prop vs No prop
of that name and also what property it applies to. Isn't the opt arg or
format text parts of the reply code suitable to convey this (using > 1
RESPONSE-CODE in a response then).

Meeting adjourned.

Thanks to Co-scribes: Bruce Kahn (bruce_kahn@iris.com) and Alex Taler
(alext@cst.ca)

Respectfully submitted:
Pat Egen


--------------FBB944EA4F66A5BDF51FD6EF
Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Description: Card for Patricia Berastegui Egen
Content-Disposition: attachment; filename="vcard.vcf"
Content-Transfer-Encoding: 7bit

begin:          vcard
fn:             Patricia Berastegui Egen
n:              Berastegui Egen;Patricia
org:            Patricia Egen Consulting
adr;dom:        803 Creek Overlook;;;Chattanooga;TN;37415;
email;internet: pregen@egenconsulting.com
title:          President and Owner
tel;work:       423.875.2652
tel;fax:        423.875.2017
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
version:        2.1
end:            vcard


--------------FBB944EA4F66A5BDF51FD6EF--



From owner-ietf-calendar@imc.org  Mon Apr  5 17:56:47 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16484
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 17:56:47 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA08322
	for ietf-calendar-bks; Mon, 5 Apr 1999 14:25:49 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id OAA08318
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 14:25:48 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA20842
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 14:26:19 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id OAA27260
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 14:26:15 -0700 (PDT)
Message-Id: <199904052126.OAA27260@engmail2.Eng.Sun.COM>
Date: Mon, 5 Apr 1999 14:26:17 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: CUA capabilities (was Re: Heirarchical error codes)
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: VoVVhqqLfw9xPaiW2wWAcQ==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> Date: Mon, 05 Apr 1999 20:05:15 +0000
> From: John Stracke <francis@ecal.com>
> 
> Doug Royer wrote:
> 
> > > > As for languages, there is no way to store multiple LANG 'DESCRIPTION'
> > > > or 'SUMMARY'.
> > >
> > > (a) Sure there is--the protocol may not specify a way to transport them, 
but
> > > you can store whatever you want.
> >
> > True - but that vendor specific extension is not part of a CAP.
> 
> Storage is not a vendor-specific extension; it's an implementation detail,
> orthogonal to the protocol.  The only extension being discussed is the 
> capability negotiation that would enable the CS to figure out which
> language variant to present.

For a VEVENT for example? If yes - there is no such iCAL object
that can represent multiple languages. This has to be true or
it would mean that the CUA could not forward the message via iMIP.
Which one would it send?

> > > (b) I suspect that iMIP might be able to express it with 
multipart/alternative
> > > (you wouldn't necessarily want to send it to someone unless you know they 
can
> > > handle it, since m/a isn't a mandatory part of MIME; but it can be done).
> >
> > They better not have the same UID, or I might keep replacing the
> > last one found as the newest one.
> 
> If you don't understand the extension, then that's more or less fine;
> they're all equivalent.

Not if they are all marked text/calendar. Then iMIP + iTIP + iCAL says
that if they have the same UID - they are the same object and that I can
assume that the newest one received is the latest update.

> > True - but there is no other better choice?
> 
> No, there isn't--everything in the world needs to handle Unicode; every
> iCal-based solution needs to handle UTF-8--but we should attempt to provide
> some form of content negotiation so that users can see languages they
> understand.
> 
> In fact, in some countries, it's probably going to be a requirement.
> Consider a CS that contains a public calendar of music events at Ontario
> Place.  That information needs to be available in English and French, and
> it would be a pain if people had to configure their CAP client to know
> which calendar to use to pick the right language.

Language and charset are NOT the same thing.

I could make a VEVENT DESCRIPTION in Spanish, French, or English in
the UTF-8 charset.

I could make the same VEVENT DESCRIPTION in Spanish, French, or English
in the iso-8859-1 (and many other) charset.

Any ~new~ component can have a LANG of anything the 'CUA' allows and the
CS would only store the LANG tag, it otherwise does not care.

Charset however MUST be anything the CUA and BOTH CS support. If
not the CS could not even determine the end of line in some charsets.
Some charsets have embedded ZERO bytes in them, ... Example:

--
	content-type ....;charset=klingon
	
	BEGIN:VEVENT
	DESCRIPTION;LANG=empire-starfleet:klsdf^cvs62340\0\01dfkg
	...
	UID:1
	END:VEVENT
 --
 
	content-type ...;charset=iso-8859-1

	END:VEVENT
	DESCRIPTION;LANG=EN-US:Meet me at the water fountain.
	...
	UID:2
	END:VEVENT

--

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Mon Apr  5 18:45:32 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16949
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 18:45:31 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA08486
	for ietf-calendar-bks; Mon, 5 Apr 1999 14:41:16 -0700 (PDT)
Received: from cdc.net (server1.cdc.net [207.244.0.12])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id OAA08481
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 14:41:14 -0700 (PDT)
Received: (qmail 14136 invoked from network); 5 Apr 1999 21:41:46 -0000
Received: from unknown (HELO egenconsulting.com) (207.244.42.65)
  by server1.cdc.net with SMTP; 5 Apr 1999 21:41:46 -0000
Message-ID: <37092E36.BD4DA0FB@egenconsulting.com>
Date: Mon, 05 Apr 1999 17:42:16 -0400
From: Pat Egen <pregen@egenconsulting.com>
Reply-To: pregen@egenconsulting.com
Organization: Egen Consulting
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: IETF Calendaring & Scheduling Mail List <ietf-calendar@imc.org>
Subject: Interim Meeting minutes - warning large doc
Content-Type: multipart/mixed; boundary="------------75D6D8D9280E5F3AB23E9C92"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------75D6D8D9280E5F3AB23E9C92
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

These are the minutes from the Menlo Park interim meeting held right
before the 44th IETF.  Several of the items worked on were discussed at
the Minneapolis meeting and can be found on the minutes previously
submitted.

CAP Editors WG Interim meeting – March 9
Attendees: Frank Dawson(Lotus), John Stracke (ECal), Paul Hill (MIT),
Andre Courtemanche (CS&T), Steve Mansour (Netscape), Alex
Hopmann(Microsoft), Richard Shusterman (Netscape), Issac Roth (?)
Robert Weiler, (Amplitude), Mark  Parmet (On Technology), David Williams
(Acrocon), Pat Egen (Patricia Egen Consulting), Doug Royer (Sun - our
host)

Meeting Agenda

1. Review schedule of work, draft by July, meeting schedules
2. Review state of work
 ICalendar RFC 2445 based
 Data Model
 System Model
 Addressing model
 Past meeting work
      - vcar, vquery,vcommand
 Scenarios for illustration
3. Transport sizing discussion
4. Identify “holes” in draft
   - Assignments for next meeting

Schedule of work, draft by July meeting schedules
--------------------------------------------------------------
Frank gave a brief history of charter, goals, etc.  He explained the
reason for the speed in trying to finish – committee needs to close by
July.  Two more interim meetings will be held before July.  Dates for
the next meeting -  4/27-28 (Atlanta) and 6/7-9 (Montreal)

We went over MN agenda.

XML discussion
--------------
There was a general discussion about the XML draft currently being
worked on by several people on the list. This will be reviewed at a
later date.

Data model
----------
Because of some new faces in the meeting, we decided to spend some time
on the models. Steve put up the CAL store model.  He showed the Calendar
ID scheme://csid/relative CALID.  CSID is a DNS internet standard -
common internet scheme syntax  (compliant to RFC 1738).


               +-----+           +-----+
        CAP    |     |   CAP     |     |   CAP
 CUA1 ---------| CS1 |-----------| CS2 |--------- CUA2
               |     |           |     |            A
               |     |  [IRIP]   |     |            |
               |     |-----------|     |            |
               |     |           |     |            |
               |     |           |     |            |
               |     |           |     |            |
               +-----+           +-----+            |
                  |      IMIP                       |
                  +---------------------------------+


Examples:  cap://cal.example.com/bob

We know it needs to be unique within the cal store – but there is not a
requirement that it be globally unique - friendly names is an issue.
The relative CALID has to be 7 bit ASCII (needs to be a valid URL for
CAP).  The issue that came out last time is how do we indicate the
hierarchy.

One proposal is : cap://cal.example.com/bobsoccar (flat naming space)
A second proposal is we pick a delimiter (like a /)  -  Decision was to
have an opaque relative calid that does not require any semantics
required. An arbitrary  string
Cal props: localized name, parent, children, owner(s)

Alex said the CALID should be a searchable DNS host name.

Inheritance is not in CAP 1. There are no access rights unless you
implement them.
If no VCARS are present then all access is denied.

We need to work through, at some point, the detail of Access control and
inheritance.  It will be harder to add it later.  One potential is we
could define what inheritance means.  If you don’t have it then
everything is denied.

We could go to cal props and pick up localized name.  A calendar can
have more than one owner and an owner can be a user, a process, or an
authentication entity.  Owner is one area where the identification may
be an issue.  It has to be tied into some kind of security mechanism.
It could be whatever the server side says is the security mechanism.
How do we identify who the owner is and what do we use as the underlying
mechanism – LDAP, security.  The term USER is not really a user – it is
an address of a CUA (calendar user agent).  There could be processes
that want to authenticate to a calendar store.  One option is to make an
owner a URI (like a LDAP entry).  If it is a human, use a mailto url.
It should be whatever the server can authenticate.  Alex says if we use
a real URI (rfc 2396) it can be what we need.  It appears that using
SASL would give us what we want on both sides. By using a standard in
place we can at least point them a mandatory CS’s  SASL implementation
and define it.  We may have to prefix something on the front in order to
store it.  Alex used Active Directory as an “example”.

Quite a long discussion ensued regarding URI and LDAP authentication.
Paul put up an example.  Using x.509  Microsoft Server:
vcm:frankRdawson@earthlink.com wants to talk to the Lotus server.  When
Alex wants to grant you access, user will be the same as owner (USER
becomes a new value type), should  we at that point validate security?
You have to be able to resolve the owner at some point. Using the
example where one server is Kerberos and the other X.509, you won’t be
able to establish a security connection.  At that point, you need to
know the “style” of the format and a should would be should you validate
it?

Paul says you won’t be able to validate it at that time.  You won’t have
the certificate.  If it is an LDAP uri, we better go get the data.  A
LDAP url points down to the distinguished name, you may not be able to
go verify the security rights at that time.  The user at some other
point may present an X.509 certificate (like in Active Directory).  You
don’t put the certificate in the URI; just put the LDAP URI in the data
– it is the query URI information.

Alex says you may want to let the Area Directors know that ACL might
prolong the issue.  Everyone else says we need some ACL VCAR stuff
included or the draft won’t fly.  There should be no unpredictable
results generated from security and ACL’s .  We need to make a statement
that we need to identify the major issues regarding security.  We need
to change the draft that we are going to put in ACL controls.  We need
to detail the VCAR.

System Model
------ - - - -
Based on the last meeting and discussion on the list, consensus says
FANOUT is back.

Note: throughout the notes there will be references to CUA1 (calendar
user agent 1), CS1 (calendar store 1), CUA2 (calendar user agent 2) and
CS2 (Calendar store 2).

CUA1 talks via CAP to a Calendar Store (CS1) and it wants to talk to
another Calendar Store (CS2) it can go via CAP or optionally IRIP
(however, can’t do everything) and another mandatory use IMIP to get to
CUA2.  Note. CAP is not server to server

NAT issues are not addressed in CAP.  We do have to deal with proxy
issues in firewalls. Do we want to put in an item in the requirements
that we don’t support NAT.  Alex says it may be required to support
multi-homed servers – you may want to address a server by name.  If you
use IP addresses you may have to let NAT look at addresses.  You fall
back to IMIP if you can’t find a connection.   IRIP addresses some of
the issues.

Alex asked why we have to have something in the protocol to have a CS
talk to a CS.  It was a requirement.  His question was there anything
specific in the requirement that states why this has to be there.  One
way is to have the CS act as another CUA.   CUA authenticates as CS1
when he talks to CS2 and he uses the SASL framework to handle this.

There was a lengthy discussion about server to server authentication and
trusted relationships.  Which credentials are being presented to the
server.  Will SASL handle this as the framework.  It will be determined
by what is running on the calendar store.  What will they allow.  If
there is no trust relationship you go back to ITIP and use whatever
binding is in place.  Paul says you can do “Impersonation” instead of
trusted relationships – some of the implementations in SASL allow. CS1
logs onto CS2.  The VCAR on the CUA on CS2 has something set up that
says what is allowed to be read/etc.  If we use SASL, two companies can
agree to use an “impersonation” or “trust” relationship.  CS2 would have
to be set up to do whatever is required.  If nothing is set up on CS2,
there will be no access.  CS2 would have to be set up to do whatever
CUA1 to do.

Here are the specific points for security.

SASL does not address granularity.  Some of the mechanisms support
impersonations.  For the mandatory SASL spec that CAP specifies it must:
Kerberos V5,

List of security features
-------------------------------
Strong authentication – mandatory
Impersonation – optional or MAY
Authentication and authorization are both mandatory
SASL support authentication not authorization
CRMV5 is a part of SASL (does it support authorization)

Impersonation:

CUA1 wants to talk to CS2.  It can get the credentials (sort of like
caching user id and password).  Impersonation does not show that it is a
different person.  It is the actual person, not “acting on behalf of “

I authenticate as who I am; then the VCAR tells the rights that are set
up.  It has to be a trusted relationship.  It will depend on what the
VCAR on the Calendar Store says is the approved access rights.  The CS
needs to have VCAR status that says update everyone, not everyone, etc.

If we do the trusted relationship, this works.  If we do impersonation,
we may have broken some of the capability we want.

You need to have support for the CAP protocol in your firewall.  If it
is not there, it does not work.   Public, private calendars – don’t
mingle what the access control with CAP.  There are common ACL items
that can be defined common across the line.

We do have a good idea, on an application specific capability, such as
the VCAR proposal.  There are these “nn” at least policies.  There are
some hard ones, some easy ones that can be defined by grammar.

Whatever calendaring goes across the Internet can not be assumed to be
“trusted” – that’s not the Internet or IETF way.  We have to be sure
that our protocol is strong on security.

Paul’s gave a good example of using a travel agency to post my itinerary
back an entry on my calendar. It may be a personal travel agent. Does it
work with our proposal.  Groups are an option.  Can we do “groups” of
entities in our VCAR grammar.  You specify an authenticated user in the
VCAR.  The authentication goes back to a user; a process; a system.  The
authentication is I am Frank, not “Frank, a member of group ..” You
authenticate in as Frank, the process then goes and looks at the
Calendar Store and sees that Frank is a member of  … We would need to
have a “grant” for every user in the VCAR – not very scalable.  We
should be managing the “when” not the “who”.  Frank says we may need to
have “a user” or “a group”.  We let the CS take care of how to handle
the people.

Putting the URI in the VCAR solves the Admin issues, the group listing
issues, etc.

To define an authenticated calendar user that the access rights apply
to. The new VCAR keyword is “userlist”  and is URI .  A Grant or a DENY
should specify one entity.  A URI representing a user or a group of
users.  We need some help on the wording.  Entity, principle, user, or
userlist.  Get verbiage from Frank.  We want to be able to retrieve who
is the owner of the property.  Owner property should be human
readable.   This may end up looking just like an “attendee”.

In the travel agency example, how do I get the information we need to
grant us the permission to use the info in the calendar product.  It
could be a MIME object.  It could be a URL with a certificate
attached.    What is the simple approach.  What we need is the
authentication id from the travel agency.

“Act on my behalf “ on one calendar – how does that interoperate with
another calendar

Further discussion on security (Paul and Issac).  It appears that the
LDAP information does not need to be in the VCAR information.  What do
we do if there is no certificates or LDAP services, you need to hand
them a user id.  CRAMMD5 may be a security vehicle that can be used in
these instances.

What makes us go to a particular VCAR on a CS?  If we have the
authentication ID and it much match the VCAR id.

To get the user to authenticate to your calendar store – you pass them
the CALID and then the server passes back the authentication id or give
them a predefined one.  Then you have the VCAR definitions for the
individual or for the principal (the principal is a one to one mapping
or a group name that expands to a list of authentication ids).  You
specify a URI to a person or to a expanding group.  Do we need a URI
prefix.  Note:  X509 may look different organization to organization.

1. Exchange CAP address
2. Authentication ID or define one
3. You may at this point create a directory entry
4. Set up a VCAR for the individual with principle set to CAP-defined or
generic URI that expands out to a group or a drop down comes up where
you present names to the user for selection.

 We may not be interoperable across different domains.  As LDAP
implementations and deployments become more prevalent, we are doing this
and it may work better in the future.

 You basically have to have a local authentication id (a MUST) or local
user account in order for this to work.  Maybe what we say is we must
implement local – and in the appendix here’s what you do.

 How does the server understand and expand the group.  Get a CERT ID
from the other server  and add it to your directory.   Then you have
access to “look at a directory on the other server?”

 Addressing Model was addressed a little. Somewhere some changes will
need to be made to VCAR.

 Wednesday, March 10, 1999
 ---------------
 Today, we did a lot more work focusing on the draft.

 Set of commands: CS Command and CAL Command

 Commands:
 Abort          Authenticate
 Capability     Continue
 Create**       Delete**
 Disconnect     Generate UID
 Send data**    Modify**
 Move**         NOOP (ECHO data)
 Read**

 ** need to address issues

 Table of Contents of draft:
 -----------------------
 State Diagram
 Command Format/Reply Codes
 Multiple Commands in progress
 Implementation Issues: minimum props for comp

 Examples
 Create calendar
 Create component to multiple cal
 Change partstat
 Read events for a range of time
 Read Calendar (has query internal)
 Read and modify alarms
 Read timezones components

 Cal Store Props
 1. Time (UTC or localtime plus TZID) – this is not a floating time
 2. Max date
 3. Min date
 4. Time Zones (component)
5. Default VCARs
6. Cal Master

Cal Props
1. Children
2. Name
3. Schedulable Hours
4. Owners
5. Parent
6. Relative CalID
7. [Path??]
8. Created
9. Last-modified
10. [Who modified??]
11. Default language
12. Default character set
13. Preferred – TZID
14. Cal Master
15. Tombstone

 Discussion

Steve said he was going to work with John Meir on SASL (John is the
editor of SASL)

Steve said last time we decided to label commands – he wants everyone to
make sure it makes a difference in how you code things.  Paul and Doug
said we must always LABEL.  Do we want to allow commands to get stacked.

Other implementation issues:

What is the minimum set of events we send down?
There are component properties, parameters, calendar properties
What state does CAP take when it gets published and how do you relate it
to ICAL
We may need to modify ICAL in order to implement CAP
Part of CAP needs to say “these are extensions” of ICAL

Version of ICAL needs to say “Version 2.0” if you conform to CAP…

CAP is between client and a server. Do we combine CAP and IRIP?
Frank says it may be a bad technical design to combine CAP and IRIP as
implementation.  Doug said he thought this was the case in Redmond.
Frank says the architecture is you must implement IRIP if you implement
CAP.  This needs to be finalized.

Steve is assuming this will be a “State full, connectionless” process,
it hits the server, disconnects then sends things back.  This may not be
the case, but this is his thinking

General discussion about timezones.  Stationery resource has a location
specific timezone.  The semantics need to be very clear about what are
the preferred timezones for this calendar.

All examples done at this meeting are done specifying TCP (not HTTP) –
the reason was this was the expertise represented at the meeting

State diagram.


 CAPABILITY                                  +-----+
+-------+                                    |     | CAPABILITY
|       |                       +---------------+  |
|   +-----------+ AUTHENTICATE  |               |<-+
+-->| Connected |-------------->| Authenticated |<----+
    +-----------+     +---------|               |     |
         |            |         +---------------+     | command
         | DISCONNECT |                 | address     | completes
         V            |                 V             |
    +--------------+  |         +---------------+     | timed out
    | Disconnected |<-+      +->|  ReadyToSend  |     |
    +--------------+         |  +---------------+     | ABORT
           A                 |    |      |            |
           |                 +----+      | SENDDATA   |
           |              address or     |            |
           |              CAPABILITY     |            |
           |                             V            |
           |     DISCONNECT     +---------------+     |
           +--------------------|    Receive    |-----+
                                |               |<--+
                                +---------------+   |
                                               |    | CONTINUTE
                                               +----+

In the diagram, the items above in parenthesis are process Bubbles.
There is a re-entrant loop using a CS command at the CONNECTED piece.
Going to the AUTHENTICATED bubble, the Authenticate path is in the SASL
cloud.  There is another re-entrant loop using a CS Command on the
AUTHENTICATED portion.  Use a CAL Command or address going to the
READYTOSEND bubble.  If you need to, you can go back and reenter the
READYTOSEND bubble using the Address path.  There is also a re-entrant
loop using a CS Command into the READYTOSEND bubble.  Use caldata across
the senddata path to the RECEIVE process.  There is a re-entrant loop
into this bubble using CONTINUE.  You can go back from RECEIVE to
AUTHENTICATE on a COMPLETE OR ABORT loop.  You can go on an ABORT loop
from READYTOSEND back to AUTHENTICATE and on a DISCONNECT loop back to a
DISCONNECTED bubble or process.   You can also pass from CONNECTED to
DISCONNECTED.

General discussion about a normal State diagram.

After authentication, I get back a session handle.  Later to reconnect I
will pass back the session handle.  You must reauthenticate again.

General discussion about connect/connectionless.  We are doing a
“connected” protocol.

Examples:

Capability and NOOP –

We will treat NOOP as a CAP command

Note: Capability command will/may return different results based upon
whether or not you are authenticated.

Frank says we need to see CAPABILITY on the Send and Authenticate.  This
provides flexibility.  Discussion changed this to be use CSCommands
instead.

General discussion about CS commands and CAL commands.  Need to identify
the specific commands and map them to the diagrams.

NOTE: on section for naming in draft, make a statement that a relative
CALID can not begin with a colon.

EXAMPLES

Create Calendar:

Note: general command format:

Label = 1*8NUMBERIC

Generic command format: label[+] 1sp cmd *arg
Generic Response format: label 1*(response code [arg])

Min: CS is 60 chars (protocol minimum) [MUST] (the CAPABILITY command
must specify what it does – expose it)
Max: 1024

Note: Frank will contact some of the small footprint device
manufacturers to see if there is any limitation requirement on min/max
lengths or buffer limitations.

To keep it generic we need to have the CAP entries as parameters
i.e. Structure: Function/ACTION Object Container (Principle)

Do we want to create multiple VCALENDARS ?? good idea??

Notes: to specify a CS id, you need to enter the fully qualified calid.
Is the root a Calendar Store and that what we say.  The root is really
the calendar store and all other calendars are children of the root.
The VALUE is a CSID and the container is the name of the specific
calendar

We call root calendars “Top level calendars” and the parent of a top
level calendar is the calendar store.

CSID, relative CALID, CALIDs can be in the list of things

Draft Note: We need to step thru hierarchical calendars in the draft and
explain the relationships between individual calendars and calendar
stores.

Need to have a reply code for each

VCOMMANDS are inside an object

Code example: (after the authentication portion)

C: 10+ CREATE VCALENDAR cap://cal.example.com/ bill ://bobo.ex
C: .COM EX.EXAMPLE.COM
S: 10 60 fully qualified container id “cap://cal.example.com/”  Note:
(60 = you do not have permission)
S: 10 2.0 fully qualified container id and will vary
cap://cal.example.com/bill (Success)
S: 10 3.14 cap://bobo.exe.com/ unsupported function (creation of
calendar)
S: 1 6.1 cap://cal.example.com/ex.example.com  could not find the
calendar or calendar does not exist
C: 20 SENDDATA
S: 20 2.0.1
C: CONTENT-TYPE: text/calendar method=create,component=VCALENDAR
Xxxx
Xxx
BEGIN: VCALENDAR
VERSION 2.1
METHOD: CREATE
BEGIN: VCOMMAND
BEGIN: VCALENDAR
RELCALID:SOCCAR **
NAME:CHARSET=xxx;LANGUAGE:XX-XX:Bill’s Soccar Team **
OWNER:capcar:bill
OWNER: capcar:Sally
CALMASTER:mailto:bill@xyz.com **
PREFERRED-TZID:billzone (some new wacky thing)
BEGIN: VCAR
CARID:12345
GRANT;CN=”Mr Bill”:principal=capcar:bill;action=ALL;object=all
GRANT;cn=”Ms Sally”:principal=capcar:sally;action=read;object=all
END:VCAR
BEGIN:VTIMEZONE
XXX TZID:BILLZONE
XXX
XXX
END:VTIMEZONE
END:VCALENDAR
. (placeholder)
20 2.0 (container id) CAP://CAL.EXAMPLE.COM/xyzunreadable1234
20 6.2 (container id) CAP://CAL.EXAMPALE.COM/BILLxyzunreadable5678

** mantatory

Read command (with Query imbedded so Steve says):

Read events from t1 (GREATERTHAN OR EQUAL TO)19990310T08Z to
199903101900Z on two calendars

C: 10 READ VEVENT bill ://bobo.ex.com/sally
S: 10 2.0 cap://cal.example.com/bill (local calendar – good response)
S: 10 2.2 cap://bobo.ex.com/sally (partial success;will attempt after
SENDDATA or redirection referral)
C: 20 SENDDATA
S: 20 2.0.1 (start giving me MIME body and CRLF when done)
C: Content-type:text/calendar;method=read,component:VCOMMAND
XXX
XXX
BEGIN:VCALENDAR
VERSION:2.1
METHOD:READ
BEGIN:VCOMMAND
BEGIN:VQUERY
MAXRESULTS:9730842
MAXSIZE:1700000000
QUERYNAME:MyviewRange
QUERY: SELECT = DTSTART,DTEND,SUMMARY,UID;
FROM = VEVENT;
WHERE (DTEND >= T1 AND DTSTART <= t2);
ORDERBY DTSTART ASC, DTEND, UID, SUMMARY
END:VQUERY
END:VCOMMAND
END:VCALENDAR
.
c: 20 2.0 cap://cal.example.com/bill
content-type:multipart/alternative
(MIME SEPERATOR)
content-type:text/calendar;method:response;component=Vset;optinfo:version:2.1

BEGIN:VCALENDAR
VERSION:2.1
BEGIN:VSET
BEGIN:VEVENT
DTSTART:….
DTEND:…
UID:….
SUMMARY:…
END:VEVENT
END:VSET
..
..
END:VCALENDAR
(MIME SEPERATOR)
content-type:text/xml
blah blah
….
C: 20 2.0 cap://bobo.ex.com/sally
Content-type:text/calendar;method:Response;component:VSET;optinfo:version:2.1

Denied access to properties
BEGIN:VEVENT
RESPONSE-CODE:XX
END:VEVENT

DENIED ACCESS TO FULL EVENTS:
2.0
BEGIN:VCALENDAR
VERSION..
BEGIN:VSET
END:VSET
END:VCALENDAR

 Create an event on several calendars

C: 10 CREATE VEVENT bill ://bobo.ex.com/sally mailto: frank@lotus.com
irip://x.y.com/ralph
S: 10 2.0 cap://cal.example.com/bill
S: 10 2.2 cap://bobo.ex.com/sally
C: 20 SENDDATA
S: 20 2.0.1
C: content-type:text/calendar;method=create;component=COMMAND
BEGIN:VCALENDAR
VERSION:2.1
METHOD:CREATE
BEGIN:VCOMMAND
BEGIN:VEVENT
DTSTART:..
DTEND:..
SUMMARY:..
UID:XYZ1234
END:VEVENT
END:VCALENDAR
UID:XYZ1234
ORGANIZER:ALTREP=”mailto:bill@example.com”;ALTREP=”irip://cal.example.com/bill::cap://cal.example.com/bill

ATTENDEE:”mailto:frank@lotus.com”
ATTENDEE:ALTREP=”mailto.bill@example.com”;...cap://cal.example.com/bill
ATTENDEE:cap://bobo.ex.com/sally
ATTENDEE:irip://x.y.com/ralph
.
.
.
S: 20 2.0 cap://cal.example.com/bill xyz1234
S: 20 2.0.2 cap://bobo.ex.com/sally
S: 20 2.0 mailto: frank@lotus.com
S: 20 6.3 irip://x.y.com/ralph

Note: If there are particular events that should have appeared in the
set that you have been denied access to – they don’t count.  There will
not be a separate error message stated for each event that you do not
have authority for.

Open issue on syntax structure:

Frank discussion on commands:  we need to come back to this later and
ensure that we make the products.

Command = label[lcc] cmd *arg.crlf
        = shortlies/multilines

shortline=lable space cmd space cmdarg crlf

calid multiline = label space lcc cmd space cmdarg crlf  1contline

contline=lcc text crlf

Query return options (what it may look like):

Multipart
Text/cal
Bills cal
Text/cal
Sally’s call

Text/cal
Begin vcalendar
Bill’s cal
End vcalendar

All of these items will be discussed at the Minneapolis meeting and then
re-visited on the list for discussion.

Submitted by Pat Egen.

--------------75D6D8D9280E5F3AB23E9C92
Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Description: Card for Patricia Berastegui Egen
Content-Disposition: attachment; filename="vcard.vcf"
Content-Transfer-Encoding: 7bit

begin:          vcard
fn:             Patricia Berastegui Egen
n:              Berastegui Egen;Patricia
org:            Patricia Egen Consulting
adr;dom:        803 Creek Overlook;;;Chattanooga;TN;37415;
email;internet: pregen@egenconsulting.com
title:          President and Owner
tel;work:       423.875.2652
tel;fax:        423.875.2017
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
version:        2.1
end:            vcard


--------------75D6D8D9280E5F3AB23E9C92--



From owner-ietf-calendar@imc.org  Mon Apr  5 20:40:34 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17851
	for <calsch-archive@odin.ietf.org>; Mon, 5 Apr 1999 20:40:34 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id RAA10151
	for ietf-calendar-bks; Mon, 5 Apr 1999 17:08:56 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id RAA10147
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 17:08:55 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA08340
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 17:09:26 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id RAA04907
	for <ietf-calendar@imc.org>; Mon, 5 Apr 1999 17:09:22 -0700 (PDT)
Message-Id: <199904060009.RAA04907@engmail2.Eng.Sun.COM>
Date: Mon, 5 Apr 1999 17:09:20 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: Interim Meeting minutes - warning large doc
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: tkvHNdFcjpRtM2V9tBTkyw==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


Small fix (I think)

> Date: Mon, 05 Apr 1999 17:42:16 -0400
> From: Pat Egen <pregen@egenconsulting.com>
> 
> These are the minutes from the Menlo Park interim meeting held right
> before the 44th IETF.  Several of the items worked on were discussed at
> the Minneapolis meeting and can be found on the minutes previously
> submitted.
> 
> ...

> Inheritance is not in CAP 1. There are no access rights unless you
> implement them.

Should be?

	 "Inheritance *is* in CAP 1 ..."

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Tue Apr  6 19:01:07 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19875
	for <calsch-archive@odin.ietf.org>; Tue, 6 Apr 1999 19:01:07 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id PAA23121
	for ietf-calendar-bks; Tue, 6 Apr 1999 15:14:49 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id PAA23117
	for <ietf-calendar@imc.org>; Tue, 6 Apr 1999 15:14:48 -0700 (PDT)
Received: by dfssl with Internet Mail Service (5.5.2580.0)
	id <2GFGH6L1>; Tue, 6 Apr 1999 15:14:55 -0700
Message-ID: <01D6C7224936D211BA450000F805D538054213B9@TOTO>
From: "Larry Osterman (Exchange)" <larryo@Exchange.Microsoft.com>
To: "'Doug Royer'" <Doug.Royer@Sun.COM>, ietf-calendar@imc.org
Subject: RE: Hierarchical error codes
Date: Tue, 6 Apr 1999 15:14:53 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

The issue is not what the CHARACTER SET is, but what the LANGUAGE is.  A
character set defines a set of glyphs only, the LANGUAGE defines the
characters to be sent using that character set.

In addition, there is the client LOCALE, which defines what collation order
to use when sorting or searching.  If there is to be any sort of search
functionality in CAP, it MUST contain the ability to specify the locale for
searching/sorting, otherwise it won't fly as an international standard.
There are already too many us-only internet protocols....


Larry Osterman
Sent from larryo-laptop.dns.microsoft.com running NT5 and Outlook 2000
and Exchange Server 5.5.  Please notify the sender of any difficulties



-----Original Message-----
From: Doug Royer [mailto:Doug.Royer@Sun.COM]
Sent: Sunday, April 04, 1999 2:10 PM
To: ietf-calendar@imc.org
Subject: Re: Heirarchical error codes



> Date: Sun, 04 Apr 1999 14:52:35 +0000
> From: John Stracke <francis@ecal.com>
> 
> Doug Royer wrote:
> 
> > > Date: Mon, 29 Mar 1999 19:44:43 +0000
> > > From: John Stracke <francis@ecal.com>
> > >
> > > Frank Dawson wrote:
> > >
> > > > What scenario did you have in mind that necessitated the CUA to also

specify
> > > > it's capabilities?
> > >
> > > "I cannot render non-Latin1 text"?
> >
> > As there were not any Latin1 text messages defined,
> > I am not sure what your need is.
> 
> There's human-composed, user-visible text in the message, which means that
> the CUA needs to consider whether the user is going to be able to read the
> incoming message.  An advanced CS might be capable of storing multiple
> versions of the text, and picking out the one to send to the CUA--but only
> if it can find out what languages the user can read, and what character
> sets the CUA can display.

The iCalendar object default charset is UTF-8. 

I would hope that a CS should be able to charset convert to UTF-8 on
the way in or out of the CS. I would also hope that all CUAs MUST be
able to handle UTF-8.

As for languages, there is no way to store multiple LANG 'DESCRIPTION'
or 'SUMMARY'.

I think the best that can occur is if all CUAs MUST be able to handle
UTF-8, and they must ask for anything other than UTF-8. A user might
not be able to understand the text as sent to the CS, but the CUA MUST
be able to understand the UTF-8 text.


-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL


From owner-ietf-calendar@imc.org  Tue Apr  6 19:30:40 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20122
	for <calsch-archive@odin.ietf.org>; Tue, 6 Apr 1999 19:30:40 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id PAA23437
	for ietf-calendar-bks; Tue, 6 Apr 1999 15:57:10 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id PAA23432
	for <ietf-calendar@imc.org>; Tue, 6 Apr 1999 15:57:10 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA05428
	for <ietf-calendar@imc.org>; Tue, 6 Apr 1999 15:57:49 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id PAA20795
	for <ietf-calendar@imc.org>; Tue, 6 Apr 1999 15:57:21 -0700 (PDT)
Message-Id: <199904062257.PAA20795@engmail2.Eng.Sun.COM>
Date: Tue, 6 Apr 1999 15:57:09 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: RE: error codes
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: +/sIJsEe8tztKvaR2i9reA==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> From: "Larry Osterman (Exchange)" <larryo@exchange.microsoft.com>
> Date: Tue, 6 Apr 1999 15:14:53 -0700 
> 
> The issue is not what the CHARACTER SET is, but what the LANGUAGE is.  A
> character set defines a set of glyphs only, the LANGUAGE defines the
> characters to be sent using that character set.
>
> In addition, there is the client LOCALE, which defines what collation order
> to use when sorting or searching.  If there is to be any sort of search
> functionality in CAP, it MUST contain the ability to specify the locale for
> searching/sorting, otherwise it won't fly as an international standard.
> There are already too many us-only internet protocols....

In iCalendar there is LANG in the iCalendar object and CHARSET in the
MIME header for us to work with.  The default charset for iCalender is
UTF-8 per the existing RFC's.  And in those RFCs a default LANG is not
defined for any 'value'.

The 'iCalendar'-LANG parameter is what many people call LOCALE (as in
'en-us' vs 'en-uk' vs 'fr-ch' vs ...).  And the (ISO?)  ~standard~ for
LOCALE is from the subset of LC_MONETARY, LC_TIME, LC_MESSAGES,
LC_CTYPE, LC_COLLATE, LC_NUMERIC.  Example:

	LC_MONETARY=en-us	What symbol to use for money
	LC_TIME=en-us		Format to display time and time zone to user.
	LC_MESSAGES=en-us	What message catalog to use
	LC_CTYPE=en-us		7bit, 8bit, multibyte, ...
	LC_COLLATE=en-us	How to sort strings
	LC_NUMERIC=en-us	How to display numeric values
	
	(There are probably more ...)

So - back to Hierarchical error codes:

After hearing the debate it would have been nice if the RFCs had not
used hierarchical numbers - but the RFCs do use hierarchical numbers
and that is now the way to do them for iCalendar objects.

As to error messages that are intended to be human readable:

    In order for there to be an error code to include a human readable
    error message, the CS MUST have 2 things:

		1) The iCalendar-LANG (or LOCALE) of the CUA

		2) The charset of the CUA.
	
 -  With human readable error messages and IF the MUST implement for
    CAP is UTF-8, then;  The CS still needs to have a message catalog
    for all of the possible LANGs (LOCALEs) that a CUA might use.

    I think this makes it much harder to interoperate. As in
    no guaranteed interpretability.

 -  If there is no default CHARSET, then the CS and CUA
    MUST agree on the CHARSET, or you can not interoperate at all.

    In other words, no interpretability guaranteed by CAP.
    
-   If however there are NO messages from the CS that are intended
    to be human readable:

    There is now less of a reason to support a large number
    of CHARSETs in the CS. And there may be NO reason to
    support multiple LANGs (LOCALEs) in the CS over CAP.
    
    If the error messages are some kind of string (numeric or not), and
    the data presented in a formatted way (Just an example):

	1.2.3 cap://www.foo.com/abc x-y-z

    The CUA and the CS could both know in any language and locale
    this means something specific. For example:
    
    	If 1.2.3 meant: permission denied
    	And x-y-z meant: CS performing backup - try later
    	
    Any CUA could now construct any human readable message
    and interoperability would be enhanced as everyone knows
    both the meaning to the CS and CUA and next state for both
    the CS and the CUA.

    The CUA could for example know that a retry is might
    work later.

-  If CAP is going to allow other than non-UTF-8 charsets, then
   it is a MUST that the CUA and the CS MUST be able to default
   back to UTF-8. Or there is no guaranteed interpretability.
   
> -----Original Message-----
> From: Doug Royer [mailto:Doug.Royer@Sun.COM]
> 
> > Date: Sun, 04 Apr 1999 14:52:35 +0000
> > From: John Stracke <francis@ecal.com>
> > 
> > Doug Royer wrote:
> > 
> > > > Date: Mon, 29 Mar 1999 19:44:43 +0000
> > > > From: John Stracke <francis@ecal.com>
> > > >
> > > > Frank Dawson wrote:
> > > >
> > > > > What scenario did you have in mind that necessitated the CUA to also
> 
> specify
> > > > > it's capabilities?
> > > >
> > > > "I cannot render non-Latin1 text"?
> > >
> > > As there were not any Latin1 text messages defined,
> > > I am not sure what your need is.
> > 
> > There's human-composed, user-visible text in the message, which means that
> > the CUA needs to consider whether the user is going to be able to read the
> > incoming message.  An advanced CS might be capable of storing multiple
> > versions of the text, and picking out the one to send to the CUA--but only
> > if it can find out what languages the user can read, and what character
> > sets the CUA can display.
> 
> The iCalendar object default charset is UTF-8. 
> 
> I would hope that a CS should be able to charset convert to UTF-8 on
> the way in or out of the CS. I would also hope that all CUAs MUST be
> able to handle UTF-8.
> 
> As for languages, there is no way to store multiple LANG 'DESCRIPTION'
> or 'SUMMARY'.
> 
> I think the best that can occur is if all CUAs MUST be able to handle
> UTF-8, and they must ask for anything other than UTF-8. A user might
> not be able to understand the text as sent to the CS, but the CUA MUST
> be able to understand the UTF-8 text.



From owner-ietf-calendar@imc.org  Wed Apr  7 00:34:22 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24251
	for <calsch-archive@odin.ietf.org>; Wed, 7 Apr 1999 00:34:20 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id UAA07739
	for ietf-calendar-bks; Tue, 6 Apr 1999 20:53:22 -0700 (PDT)
Received: from ixpres.com (AM3-10-53-206.ixpres.com [209.75.53.206])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id UAA07726;
	Tue, 6 Apr 1999 20:53:14 -0700 (PDT)
Date: Tue, 6 Apr 1999 20:53:14 -0700 (PDT)
From: bizusa@ixpres.com
Message-Id: <199904070353.UAA07726@mail.proper.com>
Reply-To: bizusa@ixpres.com
To: bizusa@ixpres.com
Subject: Organize Web Info...
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

This message is sent in compliance of the new Email bill: SECTION 301.
Sender: INFOtrepreneur, 11012 Avenida De Los Lobos, San Diego, 
California, CA 92127 - Fax: (619) 672-1000 Email: webmaster@infotrepreneur.com
Per Section 301, Paragraph (a)(2)(C) of S.1618, further transmissions to you 
by the sender of this email may be stopped at no cost to you by ending a reply 
to this email address with the word "remove" in the subject line.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

NO MORE!  BACKTRACKING OF LOST AND CONFUSING 
WEB BOOKMARKS AND TEXT DATA FILES...

Based upon your Internet interests, I thought that you would be 
interesed in Web Info Catcher which allows you to capture and store 
text data from various sources, index, categorize and edit it instantly on 
screen while online.

Access all your reference and source material instantly at a click of a button,
while you are working, browsing, searching or offline. 

It's the fastest, up-to-date, and most efficient means to "RECALL" your data.
 
  * No need... to bookmark a multitude of web sites 
  * No need... to search for misplaced or lost text files 
  * No need... to print out endless reports 
  * No need... for a web browser to reference data

- Perfect for academics, researchers, business, info junkies, etc. 
- Create your own projects, reports, topics, favorites, research, etc. 
- Open numerous projects and setup your own index references 
- Attach and Capture text information from various sources 
- Edit your projects 
- Effectively organize your information 
- Categorize your information 
- Add custom indexes 
- Automatic alpha indexing 
- Searchable index 
- Scrollable index
- View information on screen while working 
- A Stand alone program 
- Add and delete information 
- Print out data in your own time

WHY BOOKMARK OR SAVE YOUR TEXT FILES?

DON'T DELAY!  Visit INFOtrepreneur today and discover a whole new way to 
capture and store your information sources, we will be happy to assist you.

DOWNLOAD your software demo: ftp://ftp.infotrepreneur.com/pub/wicdemo.exe

OR for more info: http://www.infotrepreneur.com/webcth.htm 

Sincerely
Gail van der Merwe




From owner-ietf-calendar@imc.org  Wed Apr  7 06:39:07 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02938
	for <calsch-archive@odin.ietf.org>; Wed, 7 Apr 1999 06:39:06 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id DAA24560
	for ietf-calendar-bks; Wed, 7 Apr 1999 03:08:25 -0700 (PDT)
Received: from xenia.mc2.renault.fr (root@xenia.renault.fr [193.194.133.5])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id DAA24553
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 03:08:22 -0700 (PDT)
Received: from univers.mc2.renault.fr by xenia.mc2.renault.fr id MAA19118; Wed, 7 Apr 1999 12:09:01 +0200 (MET DST)
Received: from renault.fr by univers.mc2.renault.fr id MAA02316; Wed, 7 Apr 1999 12:09:00 +0200 (MET DST)
Message-ID: <370B2F00.D86674F5@renault.fr>
Date: Wed, 07 Apr 1999 12:10:08 +0200
From: Antoine Leca <Antoine.Leca@renault.fr>
Organization: RENAULT  (mais cette contribution est personnelle et n'engage pas 
 RENAULT)
X-Mailer: Mozilla 4.5 [ca]C- per www.softcatala.org  (Win95; I)
X-Accept-Language: ca,fr
MIME-Version: 1.0
To: Doug Royer <Doug.Royer@Sun.COM>
CC: ietf-calendar@imc.org
Subject: Re: error codes
References: <199904062257.PAA20795@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer wrote:
> 
> The 'iCalendar'-LANG parameter is what many people call LOCALE (as in
> 'en-us' vs 'en-uk' vs 'fr-ch' vs ...).  And the (ISO?)  ~standard~ for
> LOCALE is from the subset of LC_MONETARY, LC_TIME, LC_MESSAGES,
> LC_CTYPE, LC_COLLATE, LC_NUMERIC.  Example:

They are from the C language Standard (ISO/IEC 9899, aka ANSI C), except
LC_MESSAGES which is from ISO/IEC 9915 aka POSIX.

 
>         (There are probably more ...)

Not that I know of.

 
> As to error messages that are intended to be human readable:
> 
>     In order for there to be an error code to include a human readable
>     error message, the CS MUST have 2 things:
> 
>                 1) The iCalendar-LANG (or LOCALE) of the CUA

Agreed.

 
>                 2) The charset of the CUA.

Disagree.  What it needs is the charset used in the interchange.  Then
the CUA should be responsible to present it in the proper way to the user,
and this is completely outside the scope of the job on the server side
(think about GUI CUAs where the effective charset is really arrays of pixels!)


>  -  With human readable error messages and IF the MUST implement for
>     CAP is UTF-8, then;  The CS still needs to have a message catalog
>     for all of the possible LANGs (LOCALEs) that a CUA might use.

I believe this is too large as a requirement: suppose I write a ca-valencia-FR
CUA (Valencian version of Catalan as used in France): should all CS all over
the world have to catter with my very specific LOCALE?  I even do not expect
more than a pinch of CS to have messages in anything except English...

So we need negociation and fallbacks here.  With them, we then can have
a minimum (read: English) functionality.  Far from perfect, but better
than nothing.

 
>  -  If there is no default CHARSET, then the CS and CUA
>     MUST agree on the CHARSET, or you can not interoperate at all.

Agreed.


> -   If however there are NO messages from the CS that are intended
>     to be human readable:
> 
>     There is now less of a reason to support a large number
>     of CHARSETs in the CS. And there may be NO reason to
>     support multiple LANGs (LOCALEs) in the CS over CAP.

Right, but...

 
>     If the error messages are some kind of string (numeric or not), and
>     the data presented in a formatted way (Just an example):
> 
>         1.2.3 cap://www.foo.com/abc x-y-z
> 
>     The CUA and the CS could both know in any language and locale
>     this means something specific. For example:
> 
>         If 1.2.3 meant: permission denied
>         And x-y-z meant: CS performing backup - try later

This one is clear enough (although I doubt we have to be that precise).

But how can a CS express something that was not envisionned in the specs.
Examples might be "disk full", "disagree on TZ settings", "too much users
connected", "please obtain a cookie from www.cake.com before continuing",
"you are blacklisted", "only GTIML supported", "your driver is not compliant,
upgrade to version 2.x.y", etc. (some may be already covered, some are not).

 
> -  If CAP is going to allow other than non-UTF-8 charsets, then
>    it is a MUST that the CUA and the CS MUST be able to default
>    back to UTF-8.

Certainly.  In fact, I do not believe non-UTF8 charsets are to be allowed
(what can be the benefits?)


Antoine


From owner-ietf-calendar@imc.org  Wed Apr  7 10:40:55 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09629
	for <calsch-archive@odin.ietf.org>; Wed, 7 Apr 1999 10:40:54 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id HAA28519
	for ietf-calendar-bks; Wed, 7 Apr 1999 07:00:06 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id HAA28515
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 07:00:05 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id HAA25651
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 07:00:43 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id KAA05493
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 10:03:02 -0400
Message-ID: <370B6596.4CCD7A75@ecal.com>
Date: Wed, 07 Apr 1999 14:03:02 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Delimiter characters in relativeCalUID
References: <199904052045.NAA17543@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer wrote:

> > How can there be names without a namespace?
>
> My name is Doug Royer, My Calendar name is "Doug Royer" whats the namespace
> for that?

Huh? Those are two separate namespaces.  What's the problem?

Any time you have a syntax defining a set of names, that set is a namespace.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Wed Apr  7 11:13:14 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10172
	for <calsch-archive@odin.ietf.org>; Wed, 7 Apr 1999 11:13:14 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id HAA28749
	for ietf-calendar-bks; Wed, 7 Apr 1999 07:26:06 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id HAA28744
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 07:26:04 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id HAA27209
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 07:26:41 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id KAA05502
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 10:29:01 -0400
Message-ID: <370B6BAD.B4C240FA@ecal.com>
Date: Wed, 07 Apr 1999 14:29:01 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: CUA capabilities
References: <199904052126.OAA27260@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

First, a step back to recover context (I think we're talking at cross purposes,
possibly because I keep getting behind in my email and resuming threads that
people have forgotten about): the original question I tried to answer was "why
would a CUA need to send capabilities?".  My off-the-cuff answer was that it might
need to say what subset of Unicode it could handle; but please forget that, it was
clumsy.  I'm now trying to argue that a CUA might need to be able to specify what
languages its user understands, so that a CS can pick out an appropriate
translation of the iCalendar object.

Doug Royer wrote:

> > > > > As for languages, there is no way to store multiple LANG 'DESCRIPTION'
> > > > > or 'SUMMARY'.
> > > >
> > > > (a) Sure there is--the protocol may not specify a way to transport them,
> but
> > > > you can store whatever you want.
> > >
> > > True - but that vendor specific extension is not part of a CAP.
> >
> > Storage is not a vendor-specific extension; it's an implementation detail,
> > orthogonal to the protocol.  The only extension being discussed is the
> > capability negotiation that would enable the CS to figure out which
> > language variant to present.
>
> For a VEVENT for example? If yes - there is no such iCAL object
> that can represent multiple languages. This has to be true or

> it would mean that the CUA could not forward the message via iMIP.
> Which one would it send?

But CAP and iTIP are orthogonal.  A CS that uses CAP to talk to CUAs might use an
extended protocol (iTIP with proprietary extensions, or future standard
extensions) to talk to other CSes.  It would be a Good Thing if CAP1 clients could
get the benefit (or, at least, not be shut out by an incompatible transition to
CAP2).

(For that matter, the alternative renditions of the iCal object might not be sent
from CS to CS at all; a CS might incorporate babelfish technology and translate
the text.  Translation technology is pretty rough today, but it's often
usable--the translated text is more understandable than a language the user
doesn't know, at least--and it'll probably improve in the future.)

> > > > (b) I suspect that iMIP might be able to express it with
> multipart/alternative
> > > > (you wouldn't necessarily want to send it to someone unless you know they
> can
> > > > handle it, since m/a isn't a mandatory part of MIME; but it can be done).
> > >
> > > They better not have the same UID, or I might keep replacing the
> > > last one found as the newest one.
> >
> > If you don't understand the extension, then that's more or less fine;
> > they're all equivalent.
>
> Not if they are all marked text/calendar. Then iMIP + iTIP + iCAL says
> that if they have the same UID - they are the same object and that I can
> assume that the newest one received is the latest update.

As I said, that's fine.  If your MIME stack doesn't support multipart/alternative
(which it should; it's not a mandatory part of MIME, but it's extremely easy) then
your iTIP implementation will get all the iCal objects in sequence, and the last
one it gets will be the most faithful rendition (as per the m/a spec; see
RFC-2046, section 5.1.4), which probably means the one in the sender's native
language, which is the one you would have gotten without this extension anyway, so
you're no worse off.

In any case, even if this example is found to be difficult or invalid, I maintain
it is still the case that CAP must include bidirectional capability exchange.
Without that, we don't get extensibility, and nonextensible protocols die off very
quickly--probably without even getting an RFC out.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Wed Apr  7 17:44:08 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16513
	for <calsch-archive@odin.ietf.org>; Wed, 7 Apr 1999 17:44:08 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA02363
	for ietf-calendar-bks; Wed, 7 Apr 1999 14:05:02 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id OAA02359
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 14:05:01 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA20190
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 14:05:45 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id OAA11998
	for <ietf-calendar@imc.org>; Wed, 7 Apr 1999 14:05:40 -0700 (PDT)
Message-Id: <199904072105.OAA11998@engmail2.Eng.Sun.COM>
Date: Wed, 7 Apr 1999 14:05:42 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: CUA capabilities
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: tl1VWHVCw8m0YQSCUaOmuw==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> Date: Wed, 07 Apr 1999 14:29:01 +0000
> From: John Stracke <francis@ecal.com>
> 
> First, a step back to recover context (I think we're talking at cross
> purposes, possibly because I keep getting behind in my email and resuming
> threads that people have forgotten about): the original question I tried
> to answer was "why would a CUA need to send capabilities?".  My
> off-the-cuff answer was that it might need to say what subset of Unicode
> it could handle; but please forget that, it was clumsy.  I'm now trying
> to argue that a CUA might need to be able to specify what
> languages its user understands, so that a CS can pick out an appropriate
> translation of the iCalendar object.

okay - but it was a nice talk :-)

> Doug Royer wrote:
> 
> > > > > > As for languages, there is no way to store multiple LANG 
'DESCRIPTION'
> > > > > > or 'SUMMARY'.
> > > > >
> > > > > (a) Sure there is--the protocol may not specify a way to transport 
them,
> > but
> > > > > you can store whatever you want.
> > > >
> > > > True - but that vendor specific extension is not part of a CAP.
> > >
> > > Storage is not a vendor-specific extension; it's an implementation detail,
> > > orthogonal to the protocol.  The only extension being discussed is the
> > > capability negotiation that would enable the CS to figure out which
> > > language variant to present.
> >
> > For a VEVENT for example? If yes - there is no such iCAL object
> > that can represent multiple languages. This has to be true or
> 
> > it would mean that the CUA could not forward the message via iMIP.
> > Which one would it send?
> 
> But CAP and iTIP are orthogonal.  A CS that uses CAP to talk to CUAs
> might use an extended protocol (iTIP with proprietary extensions, or
> future standard extensions) to talk to other CSes.  It would be a Good
> Thing if CAP1 clients could get the benefit (or, at least, not be shut
> out by an incompatible transition to CAP2).

Thats what 'fanout' is all about. Pat had an error in her meeting
notes (from Minneapolis or the pre-Minneapolis meeting I forget which).

I think that fanout is 'in'. And that means that a CAP message
can be forwarded via iMAP.

CAP is proposing to rev the VERSION to 2.1. That does not break iTIP.

Pat Egen - was the consensus that it was fanout IN or OUT ?

> As I said, that's fine.  If your MIME stack doesn't support
> multipart/alternative (which it should; it's not a mandatory part of
> MIME, but it's extremely easy) then your iTIP implementation will get
> all the iCal objects in sequence, and the last one it gets will be the
> most faithful rendition (as per the m/a spec; see RFC-2046,
> section 5.1.4), which probably means the one in the sender's native
> language, which is the one you would have gotten without this extension
> anyway, so you're no worse off.

That is one of the points brought up in Minneapolis. Frank presented
the details of why that is a problem and needed to be fixed.

> In any case, even if this example is found to be difficult or invalid,
> I maintain it is still the case that CAP must include bidirectional
> capability exchange. Without that, we don't get extensibility, and
> nonextensible protocols die off very quickly--probably without even
> getting an RFC out.

I strongly agree that the problems you address need to be solved.

If we solve this incorrectly we have a mess. Ask anyone that has done 
the code that implements the telnet options. I have been
told that the telnet I-HAVE and I-WANT from each side can get very messy.
I think that each side sending CAPABILITY might get into the
same problems.

I don't know the best way - I just don't want to step in the
same land mine.

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Thu Apr  8 17:32:52 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06985
	for <calsch-archive@odin.ietf.org>; Thu, 8 Apr 1999 17:32:51 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA20077
	for ietf-calendar-bks; Thu, 8 Apr 1999 13:55:28 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id NAA20073
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 13:55:28 -0700 (PDT)
Received: by dfssl with Internet Mail Service (5.5.2580.0)
	id <2P9D1RM2>; Thu, 8 Apr 1999 13:54:47 -0700
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B0246D7F3@HYDRANT>
From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
To: "'andrec@cst.ca'" <andrec@cst.ca>, ietf-calendar@imc.org
Subject: RE: Heirarchical error codes: A proposal
Date: Thu, 8 Apr 1999 13:54:51 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

With this proposal, are you intending that the strings in the table below be
sent along with the numbers?  I'd go for that -- yes it's lengthy, but it
makes design/debugging easier.

Lisa

-----Original Message-----
From: andrec@cst.ca [mailto:andrec@cst.ca]
Sent: Monday, March 22, 1999 8:31 AM
To: ietf-calendar@imc.org
Subject: Re: Heirarchical error codes: A proposal




Here's a proposal to solve the "Hierarchical error code issue", allowing us
to 
move forward

If we accept that error codes can be hierarchical, that is a series of
numbers
Separated by "."  (i.e. 4.5.5) and that we accept that there is a known
table
of error for a particular version of the protocol as could be illustrated by
the
example below:

		4.5.8	"BADLY FORMATED DATA"
4.5.8.1	"BADLY FORMATED VCAR"
4.5.8.2	"BADLY FORMATED iCAL DATA"
4.5.8.2.1	"BADLY FORMATED OWNNER PROPERTY
4.5.8.2.2	"BADLY FORMATED DTSTART
4.5.8.2.3	"BADLY FORMATED  DTEND"
4.5.8.3	"BADLY FORMATED PRINCIPAL


Then, given a new server that has more error codes, for instance 4.5.8.1.4,

with meaning "BADLY FORMATED CARID". Note that it is not in the table.

An older CUA can still function. It doesn't know exactly what the error
means but it known it's a badly formatted VCAR.

This way of doing has 2 benefits:

1-	Interoperability of servers supporting error codes that are more
specific. The example above illustrates it.
2-	Allows new set of error codes to be published for the protocol in a
standard way. The group, or individuals could certainly propose very well
defined extension, through the IETF process.

Andre Courtemanche
CS&T


From owner-ietf-calendar@imc.org  Thu Apr  8 17:33:17 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06997
	for <calsch-archive@odin.ietf.org>; Thu, 8 Apr 1999 17:33:16 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA20144
	for ietf-calendar-bks; Thu, 8 Apr 1999 14:03:03 -0700 (PDT)
Received: from doggate.exchange.microsoft.com (doggate.exchange.microsoft.com [131.107.88.55])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id OAA20138
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 14:03:02 -0700 (PDT)
Received: by doggate.exchange.microsoft.com with Internet Mail Service (5.5.2232.9)
	id <HY5MJRS1>; Thu, 8 Apr 1999 14:02:34 -0700
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B0246D7F4@HYDRANT>
From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
To: "'Antoine Leca'" <Antoine.Leca@renault.fr>,
        Doug Royer
	 <Doug.Royer@Sun.COM>
Cc: ietf-calendar@imc.org
Subject: RE: error codes
Date: Thu, 8 Apr 1999 14:02:22 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

There seems to be an assumption that whenever there is human-readable text
included, that the server must be able to translate that into the
appropriate language for the user.  Why is that?  Antoine's example of a
specific dialect is a good example why we can't expect that to happen.
Instead, Antoine's "ca-valencia-FR" client, which is carefully designed to
use proper dialect and (if it's a GUI) well-formatted dialog boxes of some
kind, will know all the standard errors and have a table mapping them to
appropriate catalan strings.  The client might even have additional
information it can tack on.  An english client might even receive the error
code "4.5.8  BADLY FORMATTED DATA"  and instead display it to the user as
"An error was received from the server which indicated that data was
improperly formatted".  Or the client might choose to do something
completely different than to display a text error.  Summary:  the client
will choose what to display anyway, so text error messages shouldn't be
translated/formatted for the client.

Instead, I've always understood text-based error messages in protocols to be
a convenience for protocol and implementation designers, testers, coders,
debuggers, system administrators, etc.  This makes it possible to use
strings which are brief but informative to techies, like "BADLY FORMATTED
VCAR".

Lisa

-----Original Message-----
From: Antoine Leca [mailto:Antoine.Leca@renault.fr]
Sent: Wednesday, April 07, 1999 3:10 AM
To: Doug Royer
Cc: ietf-calendar@imc.org
Subject: Re: error codes


Doug Royer wrote:
> 
> The 'iCalendar'-LANG parameter is what many people call LOCALE (as in
> 'en-us' vs 'en-uk' vs 'fr-ch' vs ...).  And the (ISO?)  ~standard~ for
> LOCALE is from the subset of LC_MONETARY, LC_TIME, LC_MESSAGES,
> LC_CTYPE, LC_COLLATE, LC_NUMERIC.  Example:

They are from the C language Standard (ISO/IEC 9899, aka ANSI C), except
LC_MESSAGES which is from ISO/IEC 9915 aka POSIX.

 
>         (There are probably more ...)

Not that I know of.

 
> As to error messages that are intended to be human readable:
> 
>     In order for there to be an error code to include a human readable
>     error message, the CS MUST have 2 things:
> 
>                 1) The iCalendar-LANG (or LOCALE) of the CUA

Agreed.

 
>                 2) The charset of the CUA.

Disagree.  What it needs is the charset used in the interchange.  Then
the CUA should be responsible to present it in the proper way to the user,
and this is completely outside the scope of the job on the server side
(think about GUI CUAs where the effective charset is really arrays of
pixels!)


>  -  With human readable error messages and IF the MUST implement for
>     CAP is UTF-8, then;  The CS still needs to have a message catalog
>     for all of the possible LANGs (LOCALEs) that a CUA might use.

I believe this is too large as a requirement: suppose I write a
ca-valencia-FR
CUA (Valencian version of Catalan as used in France): should all CS all over
the world have to catter with my very specific LOCALE?  I even do not expect
more than a pinch of CS to have messages in anything except English...

So we need negociation and fallbacks here.  With them, we then can have
a minimum (read: English) functionality.  Far from perfect, but better
than nothing.

 
>  -  If there is no default CHARSET, then the CS and CUA
>     MUST agree on the CHARSET, or you can not interoperate at all.

Agreed.


> -   If however there are NO messages from the CS that are intended
>     to be human readable:
> 
>     There is now less of a reason to support a large number
>     of CHARSETs in the CS. And there may be NO reason to
>     support multiple LANGs (LOCALEs) in the CS over CAP.

Right, but...

 
>     If the error messages are some kind of string (numeric or not), and
>     the data presented in a formatted way (Just an example):
> 
>         1.2.3 cap://www.foo.com/abc x-y-z
> 
>     The CUA and the CS could both know in any language and locale
>     this means something specific. For example:
> 
>         If 1.2.3 meant: permission denied
>         And x-y-z meant: CS performing backup - try later

This one is clear enough (although I doubt we have to be that precise).

But how can a CS express something that was not envisionned in the specs.
Examples might be "disk full", "disagree on TZ settings", "too much users
connected", "please obtain a cookie from www.cake.com before continuing",
"you are blacklisted", "only GTIML supported", "your driver is not
compliant,
upgrade to version 2.x.y", etc. (some may be already covered, some are not).

 
> -  If CAP is going to allow other than non-UTF-8 charsets, then
>    it is a MUST that the CUA and the CS MUST be able to default
>    back to UTF-8.

Certainly.  In fact, I do not believe non-UTF8 charsets are to be allowed
(what can be the benefits?)


Antoine


From owner-ietf-calendar@imc.org  Thu Apr  8 17:52:01 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07080
	for <calsch-archive@odin.ietf.org>; Thu, 8 Apr 1999 17:52:01 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA20328
	for ietf-calendar-bks; Thu, 8 Apr 1999 14:23:10 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id OAA20324
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 14:23:09 -0700 (PDT)
Received: by dfssl with Internet Mail Service (5.5.2580.0)
	id <2P9D1RS6>; Thu, 8 Apr 1999 14:22:29 -0700
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B0246D7F5@HYDRANT>
From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
To: "'Doug Royer'" <Doug.Royer@Sun.COM>, ietf-calendar@imc.org
Subject: RE: CAP Example READ-1
Date: Thu, 8 Apr 1999 14:22:32 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

SQL Cursors are cool and work well, but this would require a lot of state to
be maintained on the server.  (Database servers are meant to do that, but we
haven't really discussed whether that style of interaction is intended for
CAP servers).  How many different calendar clients are going to have views
into how many different calendars on one server?  

If the client can re-establish the context with each new request, then the
server load becomes much more manageable.  That would require sending:
 - the original search query, including ORDERBY
 - the calid of the current item
 - (possibly) how many rows to return.
Now if the server happens to have the original search query cached it can be
fast, and if it doesn't it can still respond.

The problem with this is that the current item could be deleted, and the
server would have to respond with an error, but there are similar
difficulties with cursoring.

Lisa


-----Original Message-----
From: Doug Royer [mailto:Doug.Royer@Sun.COM]
Sent: Friday, March 19, 1999 4:50 PM
To: ietf-calendar@imc.org
Subject: RE: CAP Example READ-1



Maybe we want to use SQL 'CURSOR's?  That's how SQL clients do it now for
dynamic binding (as I understand it).

Something like:

1) Define the QUERY by name (MyViewRange + cursor_name):

	C: ...
	C: BEGIN:VQUERY
	C: MAXSIZE:17000000
	C: QUERYNAME:MyViewRange
	C: QUERY:DECLARE cursor_name CURSOR FOR
	C:  SELECT DTSTART,DTEND,SUMMARY,UID;
	C:  FROM VEVENT;
	C:  WHERE (DTEND >= 19990310T080000Z AND DTSTART <=
19990310T190000Z);
	C:  ORDERBY (DTSTART ASC, DTEND, UID, SUMMARY)
	C: END:VQUERY
	C: ...
	
	(note MAXRESULTS was removed)

2) Then later in the same connection and session and perhaps in the same
   VCALENDAR mime packet, the CUA could send something like the following
   for each row to be retrieved:

	C: ...
 	C: BEGIN:VQUERY
	C: QUERYNAME:MyViewRange
	C: QUERY:FETCH NEXT FROM cursor_name
	C: END:VQUERY
	C: ...


Using standard SQL - no extensions needed.

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL

> From: "Tony Small (Exchange)" <tonysm@Exchange.Microsoft.com>
> Date: Thu, 18 Mar 1999 17:31:30 -0800
> 
> Can we add a RESULTSTART property?  For instance:
> 
> C: MAXRESULTS:20
> C: RESULTSTART:10
> 
> This example would return the results 10 through 30.
> If there is no resultstart, then it's assumed to be zero.
> 
> If a CUA can retrieve a specific number of results, it would seem that it
> would also need to be able to retrieve results that follow.  We wouldn't
> want to have to retrieve more than needed.
> 
> Tony
> 
> -----Original Message-----
> From: sman@netscape.com [mailto:sman@netscape.com]
> Sent: Wednesday, March 17, 1999 9:24 AM
> To: CalSched IETF
> Subject: CAP Example READ-1
> 
> 
> Example READ-1
> 
> This example shows how the READ command can be used to read events in a
> particular time range from multiple calendars.
> 
> 
> C: 10 READ VEVENT relcal2 ://bobo.ex.com/relcal3
> S: 10 2.0 cap://cal.example.com/relcal2
> S: 10 2.2 cap://bobo.ex.com/relcal3
> C: 10 SENDDATA
> S: 10 2.0.1
> C: CONTENT-TYPE: text/calendar; method=read; component=VCOMMAND
> C:
> C: BEGIN:VCALENDAR
> C: VERSION:2.1
> C: METHOD:READ
> C: BEGIN:VCOMMAND
> C: BEGIN:VQUERY
> C: MAXRESULTS:20
> C: MAXSIZE:17000000
> C: QUERYNAME:MyViewRange
> C: QUERY:SELECT (DTSTART,DTEND,SUMMARY,UID);
> C:   FROM VEVENT;
> C:   WHERE (DTEND >= 19990310T080000Z AND DTSTART <= 19990310T190000Z);
> C:   ORDERBY (DTSTART ASC, DTEND, UID, SUMMARY)
> C: END:VQUERY
> C: END:VCOMMAND
> C: END:VCALENDAR
> C: .
> S: 10 2.0 cap://cal.example.com/relcal2
> S: Content-type: text/calendar; Method=RESPONSE; Component=VDATA;
> Optinfo=VERSION 2.1
> S: Content-Transfer-Encoding: 7bit
> S:
> S: BEGIN:VCALENDAR
> S: VERSION:2.1
> S: METHOD:RESPONSE
> S: BEGIN:VDATA
> S: BEGIN:VEVENT
> S: DTSTART:19990310T090000Z
> S: DTEND:19990310T100000Z
> S: UID:1234
> S: SUMMARY:Big time meeting
> S: END:VEVENT
> S: BEGIN:VEVENT
> S: DTSTART:19990310T130000Z
> S: DTEND:19990310T133000Z
> S: UID:5678
> S: SUMMARY:small time meeting
> S: END:VEVENT
> S: END:VDATA
> S: END:VCALENDAR
> S: .
> S: 10 2.0 cap://bobo.ex.com/relcal3
> S: Content-type: text/calendar; Method=RESPONSE; Component=VDATA;
> Optinfo=VERSION 2.1
> S: Content-Transfer-Encoding: 7bit
> S:
> S: BEGIN:VCALENDAR
> S: VERSION:2.1
> S: METHOD:RESPONSE
> S: BEGIN:VDATA
> S: BEGIN:VEVENT
> S: DTSTART:19990310T140000Z
> S: DTEND:19990310T143000Z
> S: UID:1919191
> S: SUMMARY:Summer budget meeting
> S: END:VEVENT
> S: END:VDATA
> S: END:VCALENDAR
> S: .


From owner-ietf-calendar@imc.org  Thu Apr  8 17:53:32 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07093
	for <calsch-archive@odin.ietf.org>; Thu, 8 Apr 1999 17:53:31 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA20370
	for ietf-calendar-bks; Thu, 8 Apr 1999 14:26:29 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id OAA20366
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 14:26:28 -0700 (PDT)
Received: by dfssl with Internet Mail Service (5.5.2580.0)
	id <2P9D1RT6>; Thu, 8 Apr 1999 14:25:48 -0700
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B0246D7F6@HYDRANT>
From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
To: "'Doug Royer'" <Doug.Royer@Sun.COM>, ietf-calendar@imc.org
Subject: RE: CAP Example READ-1
Date: Thu, 8 Apr 1999 14:25:51 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

You're right, I forgot that we would need notification to do truly dynamic
search folders.  But still, if a user asks for "first 20" items in a search,
then an item is inserted #25, then 10 minutes later asks for "second 20
items" in the same search, the user would like to see the new #25.

Lisa

-----Original Message-----
From: Doug Royer [mailto:Doug.Royer@Sun.COM]
Sent: Monday, March 22, 1999 12:41 PM
To: ietf-calendar@imc.org
Subject: RE: CAP Example READ-1



> From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
> Date: Sun, 21 Mar 1999 13:34:41 -0800
> 
> Static searches are sometimes useful, but it annoys the user to be looking
> through a list of online tasks and not see new ones as they appear.
Dynamic
> or repeatedly refreshed searches are required client functionality, and
yet
> there are still ways of getting row-ranges from them.  Tony listed one, I
> just outlined a more generalized principle.

And how would your approach (in you previous post) show new events
that appear after you look at them? There is no 'date entered' property.
We only have LAST-MODIFIED and CREATED. And CREATED is the event
creation time, not the time is was entered into the store. So an event
could be stored that was created yesterday. It could be stored 1 second
after you just viewed that time range.

I do not think the problem (...see new ones as they appear) is solvable
with query. We deferred notification until CAP-2. Notification is what
would be required to implement seeing them as inserted into the store.
I don't see the above need as solvable with any query method.

> Lisa
> 
> -----Original Message-----
> From: sman@netscape.com [mailto:sman@netscape.com]
> Sent: Friday, March 19, 1999 12:47 PM
> To: alext@cst.ca
> Cc: ietf-calendar@imc.org
> Subject: Re: CAP Example READ-1
> 
> 
> hmm... I remember bringing that at the meeting: essentially to name or
store
> the
> solution set to a query. There are issues with naming/storing/referring to
> them on
> the server. For instance, how long do you keep the solution set around?
Most
> people
> just said to let the db subsystem worry about caching the querys/solution
> sets.
> 
> Comments?
> 
> -Steve
> 
> Alexander Taler wrote:
> 
> > Unless the server stores the results of the initial search and
> > subsequent reads are performed on the same data set there are serious
> > problems with this approach.
> >
> > If data is deleted between queries the position of the results may
> > change, so that what was result 12 on the first query may become
> > result 8 for the second query.  If I query for the first 10 and then
> > second 10 I will never receive that information.  Similarly if data is
> > added I may end up receiving the same information twice.
> >
> > So, if we really want the ability to incrementally retrieve data from
> > a search we need to add a facility for referencing search results on
> > the server.
> >
> > Steve Mansour wrote:
> > >
> > > OK that was probably it.  I like the resultstart, maxresults
combination
> the
> > > best.  Since that's what you proposed, I take it you prefer that as
> well.
> > > -Steve
> > >
> > > "Tony Small (Exchange)" wrote:
> > >
> > > > I originally suggested having two properties- resultstart and
> resultend.
> > > > Then I think Bruce Kahn suggested having resultstart with
maxresults.
> (I
> > > > cut out myself as the middleman. :-)
> > > >
> > > > -----Original Message-----
> > > > From: sman@netscape.com [mailto:sman@netscape.com]
> > > > Sent: Thursday, March 18, 1999 5:57 PM
> > > > To: Tony Small (Exchange)
> > > > Cc: CalSched IETF
> > > > Subject: Re: CAP Example READ-1
> > > >
> > > > This sounds reasonable to me.  I've made the update.  I think that
> someone
> > > > at
> > > > the meeting might have had another suggestion (please speak up if
> you're out
> > > > there).
> > > > -Steve
> > > >
> > > > "Tony Small (Exchange)" wrote:
> > > >
> > > > > Can we add a RESULTSTART property?  For instance:
> > > > >
> > > > > C: MAXRESULTS:20
> > > > > C: RESULTSTART:10
> > > > >
> > > > > This example would return the results 10 through 30.
> > > > > If there is no resultstart, then it's assumed to be zero.
> > > > >
> > > > > If a CUA can retrieve a specific number of results, it would seem
> that it
> > > > > would also need to be able to retrieve results that follow.  We
> wouldn't
> > > > > want to have to retrieve more than needed.
> > > > >
> > > > > Tony
> > > > >
> > > > > -----Original Message-----
> > > > > From: sman@netscape.com [mailto:sman@netscape.com]
> > > > > Sent: Wednesday, March 17, 1999 9:24 AM
> > > > > To: CalSched IETF
> > > > > Subject: CAP Example READ-1
> > > > >
> > > > > Example READ-1
> > > > >
> > > > > This example shows how the READ command can be used to read events
> in a
> > > > > particular time range from multiple calendars.
> > > > >
> > > > > C: 10 READ VEVENT relcal2 ://bobo.ex.com/relcal3
> > > > > S: 10 2.0 cap://cal.example.com/relcal2
> > > > > S: 10 2.2 cap://bobo.ex.com/relcal3
> > > > > C: 10 SENDDATA
> > > > > S: 10 2.0.1
> > > > > C: CONTENT-TYPE: text/calendar; method=read; component=VCOMMAND
> > > > > C:
> > > > > C: BEGIN:VCALENDAR
> > > > > C: VERSION:2.1
> > > > > C: METHOD:READ
> > > > > C: BEGIN:VCOMMAND
> > > > > C: BEGIN:VQUERY
> > > > > C: MAXRESULTS:20
> > > > > C: MAXSIZE:17000000
> > > > > C: QUERYNAME:MyViewRange
> > > > > C: QUERY:SELECT (DTSTART,DTEND,SUMMARY,UID);
> > > > > C:   FROM VEVENT;
> > > > > C:   WHERE (DTEND >= 19990310T080000Z AND DTSTART <=
> 19990310T190000Z);
> > > > > C:   ORDERBY (DTSTART ASC, DTEND, UID, SUMMARY)
> > > > > C: END:VQUERY
> > > > > C: END:VCOMMAND
> > > > > C: END:VCALENDAR
> > > > > C: .
> > > > > S: 10 2.0 cap://cal.example.com/relcal2
> > > > > S: Content-type: text/calendar; Method=RESPONSE; Component=VDATA;
> > > > > Optinfo=VERSION 2.1
> > > > > S: Content-Transfer-Encoding: 7bit
> > > > > S:
> > > > > S: BEGIN:VCALENDAR
> > > > > S: VERSION:2.1
> > > > > S: METHOD:RESPONSE
> > > > > S: BEGIN:VDATA
> > > > > S: BEGIN:VEVENT
> > > > > S: DTSTART:19990310T090000Z
> > > > > S: DTEND:19990310T100000Z
> > > > > S: UID:1234
> > > > > S: SUMMARY:Big time meeting
> > > > > S: END:VEVENT
> > > > > S: BEGIN:VEVENT
> > > > > S: DTSTART:19990310T130000Z
> > > > > S: DTEND:19990310T133000Z
> > > > > S: UID:5678
> > > > > S: SUMMARY:small time meeting
> > > > > S: END:VEVENT
> > > > > S: END:VDATA
> > > > > S: END:VCALENDAR
> > > > > S: .
> > > > > S: 10 2.0 cap://bobo.ex.com/relcal3
> > > > > S: Content-type: text/calendar; Method=RESPONSE; Component=VDATA;
> > > > > Optinfo=VERSION 2.1
> > > > > S: Content-Transfer-Encoding: 7bit
> > > > > S:
> > > > > S: BEGIN:VCALENDAR
> > > > > S: VERSION:2.1
> > > > > S: METHOD:RESPONSE
> > > > > S: BEGIN:VDATA
> > > > > S: BEGIN:VEVENT
> > > > > S: DTSTART:19990310T140000Z
> > > > > S: DTEND:19990310T143000Z
> > > > > S: UID:1919191
> > > > > S: SUMMARY:Summer budget meeting
> > > > > S: END:VEVENT
> > > > > S: END:VDATA
> > > > > S: END:VCALENDAR
> > > > > S: .
> > >
> > >
----------------------------------------------------------------------
> > >
> > >   Steve Mansour <sman@netscape.com>
> > >   Judge, Jury, and Executioner
> > >   Netscape
> > >
> > >   Steve Mansour
> > >   Judge, Jury, and Executioner  <sman@netscape.com>
> > >   Netscape
> > >   Mountain View                 Fax: 650-937-2103
> > >   CA                            Work: 650-937-2378
> > >   94043                         Netscape Conference Address
> > >                                 Netscape Conference DLS Server
> > >   Additional Information:
> > >   Last Name     Mansour
> > >   First Name    Steve
> > >   Version       2.1

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL


From owner-ietf-calendar@imc.org  Fri Apr  9 07:31:23 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00979
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:31:22 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id DAA22869
	for ietf-calendar-bks; Fri, 9 Apr 1999 03:49:20 -0700 (PDT)
Received: from a4.jck.com ([63.65.7.140])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id DAA22865
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 03:49:15 -0700 (PDT)
Received: from p6.jck.com ("port 1099"@[63.65.7.134])
 by a4.jck.com (PMDF V5.1-11 #C3296) with SMTP id <0F9X001214PRO5@a4.jck.com>
 for ietf-calendar@imc.org; Fri,  9 Apr 1999 06:49:03 -0400 (EDT)
Date: Fri, 09 Apr 1999 06:48:41 -0400 (Eastern Daylight Time)
From: John C Klensin <klensin@jck.com>
Subject: Re: error codes
In-reply-to: <370DA05F.58B61239@ms.com>
To: David Madeo <dmadeo@ms.com>
Cc: ietf-calendar@imc.org
Message-id: <SIMEON.9904090641.D@p6.jck.com>
MIME-version: 1.0
X-Mailer: Simeon for Win32 Version 4.1.5 Build (42)
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
X-Authentication: none
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


On Fri, 09 Apr 1999 02:38:23 -0400 David Madeo <dmadeo@ms.com> 
wrote:

> I agree with most of what Lisa (and the others) are saying on this.  However,
> the dissenting view convinced me.  To reiterate: 1) Adding text of any
> nationality makes the parsing more difficult, especially since it might include
> data as well as a return code (referrals).   2) People working with older
> protocols had found that developers had hard coded parsing based on the
> "friendly" text and were now locked into that format going forward.  Does anyone
> disagree with these two points?

I think the latter is a misreading of the experience.  There
have been two separate problems: 

(i) The original code set is inadequate, so people make up their
own.  This is rarely a "fix in version 2" problem: if
implementers discover that they _need_ something that isn't
there, they will make it up and use it, and, by "version 2", it
will be too late to get interoperability, at least without great
pain.  I suggest that the correct lesson is that, if one can't
be absolutely, 100%, positive that the set of codes provided is
sufficient and unambiguous, then the doc should specify exactly
what should be done when one of the exceptions is found (and
what conditions might constitute an exception, rather than an
excuse for overloading).

(ii) People start parsing, and interpreting, the text part
(whether to translate into a different natural language, or to
translate from geek-speak into "people", or for other purposes,
makes no difference.  This has been cited as a good reason for
banning such text entirely, but it is very handy for tracking
down problems of many varieties.  A flat ban on the practice of
parsing/ interpreting such strings is probably a good idea, but
the ban will stick iff the error code set is sufficient or
readily extensible in an orderly way.  And, of course, if there
have to be significant bits of text in those strings, it better
be *real* easy to find them and pull them out, language and
character-set independent.  

But trying to standardize the text strings and prohibit
everything else is probably a bad idea, if for no other reason
than that such requirements are almost always ignored in
practice. 

    john




From owner-ietf-calendar@imc.org  Fri Apr  9 07:32:10 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01037
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:32:10 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id BAA16367
	for ietf-calendar-bks; Fri, 9 Apr 1999 01:18:47 -0700 (PDT)
Received: from xenia.mc2.renault.fr (root@xenia.renault.fr [193.194.133.5])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id BAA16362
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 01:18:43 -0700 (PDT)
Received: from univers.mc2.renault.fr by xenia.mc2.renault.fr id KAA28701 for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 10:18:37 +0200 (MET DST)
Received: from renault.fr by univers.mc2.renault.fr id KAA27523 for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 10:18:35 +0200 (MET DST)
Message-ID: <370DB81E.8EEF3092@renault.fr>
Date: Fri, 09 Apr 1999 10:19:42 +0200
From: Antoine Leca <Antoine.Leca@renault.fr>
Organization: RENAULT  (mais cette contribution est personnelle et n'engage pas 
 RENAULT)
X-Mailer: Mozilla 4.5 [ca]C- per www.softcatala.org  (Win95; I)
X-Accept-Language: ca,fr
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: error codes
References: <199904090206.TAA16172@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer ha escrit:
> 
> > From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@exchange.microsoft.com>
> > Date: Thu, 8 Apr 1999 14:02:22 -0700
> >
> > There seems to be an assumption that whenever there is human-readable text
> > included, that the server must be able to translate that into the
> > appropriate language for the user.  Why is that?

"must" is too strong as a request, as I shown, but Doug have a point when
he said:
>         2) Forcing a CUA in France or Japan to display CS status
>            messages of a non-critical nature in English is bad manners.

So the answer is to me: "good-behaved".


But I believe everybody see that another criteria is coming into play:
"criticalness".

To give you a different example, we have here a firewall that is
derived of English-speaking work; we are mainly Frenchies to use it,
so the people quick complained that the first version only displayed
the error message (like "host not found") in English.

The present version displays:
- a banner showing the general meaning of the message, in French;
   this is part of the localization of the firewall
- an explanation in French that explains what can had happen usually;
   this is also part of the localization
- a banner to refer the user to the support if needed; this is generic,
   and is configured by the admin people here
- then, the same explanations as 1st and 2nd parts in English, giving
   also all the transcription of the faulty interchange with full
   messages.

Of course, usually people only read the beginning, which are in French,
and are in effect the same as numeric codes as we discuss.  Critical
informations, if any, has to go in this area.

OTOH, techies do read the whole page (when something not normal happens),
and so are required to read English; here non-critical messages in
English won't hurt (of course, the more near from my current LOCALE,
the better).
 

> Perhaps a compromise.
> 
> Maybe we can have some kind of tag or rule so that the CUA knows
> that a specific status message from the CS is not a typical status
> message, but something that the CUA really needs to display to the user.

Yes, I like this idea.
In fact, I was thinking about the contrary: adding a brief translation
of message code to English as a form of comment, but saying that they
are "non-normative" and what really matters is the numeric code.  But
allowing also non-comment messages for the kind of things I was talking 
about.

But I believe your idea is better, in the sense that the critical
messages are now an additionnal form, thus they are likely to *not*
being overused (at least at the beginning).


Antoine


From owner-ietf-calendar@imc.org  Fri Apr  9 07:32:11 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01042
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:32:11 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id AAA14557
	for ietf-calendar-bks; Fri, 9 Apr 1999 00:36:13 -0700 (PDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id AAA14550
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 00:36:11 -0700 (PDT)
Received: from [192.168.110.1] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id JAA25965; 
          Fri, 9 Apr 1999 09:36:02 +0200 (MET DST)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Sender: paf@nix.swip.net
Message-Id: <v04204c23b333590f72e8@[192.168.110.1]>
In-Reply-To: <199904090206.TAA16172@engmail2.Eng.Sun.COM>
References: <199904090206.TAA16172@engmail2.Eng.Sun.COM>
Date: Fri, 9 Apr 1999 09:14:16 +0200
To: Doug Royer <Doug.Royer@Sun.COM>, ietf-calendar@imc.org
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: RE: error codes
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

Regarding error codes, please check the discussions / drafts etc from 
the ftpext working group working with internationalization and 
standardization of ftp.

There might be some ideas you can borrow from that wg.

   Patrik
------------------------------------------------------------------
Area Director, Applications Area               Email: paf@swip.net
IETF                                             URL: http://paf.se
                                          PGP Key ID: 0xBD236602

   In theory there is no difference between theory and practice,
   but in practice, there is.


From owner-ietf-calendar@imc.org  Fri Apr  9 07:32:12 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01054
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:32:12 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id AAA11952
	for ietf-calendar-bks; Fri, 9 Apr 1999 00:01:48 -0700 (PDT)
Received: from piinbh2.ms.com (firewall-user@piinbh2.ms.com [199.89.64.72])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id AAA11948
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 00:01:47 -0700 (PDT)
Received: (from uucp@localhost)
        by piinbh2.ms.com (8.8.6/fw v1.22) id DAA12602;
        Fri, 9 Apr 1999 03:01:44 -0400 (EDT)
Received: from unknown(144.14.19.186) by piinbh2.ms.com via smap (4.1)
	id xma012314; Fri, 9 Apr 99 03:01:19 -0400
Received: from ms.com (eqhq50.morgan.com [205.228.83.50])
        by sasmh1.ms.com (8.8.5/hub+ldap v2.3) with ESMTP id DAA14555;
        Fri, 9 Apr 1999 03:01:18 -0400 (EDT)
Message-ID: <370DA5BD.4E9652BB@ms.com>
Date: Fri, 09 Apr 1999 03:01:17 -0400
From: David Madeo <dmadeo@ms.com>
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John Stracke <francis@ecal.com>
CC: ietf-calendar@imc.org
Subject: Re: CUA capabilities
References: <199904052126.OAA27260@engmail2.Eng.Sun.COM> <370B6BAD.B4C240FA@ecal.com>
Content-Type: multipart/mixed;
 boundary="------------8B1C70385959C67DDEE0FD5C"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------8B1C70385959C67DDEE0FD5C
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

John Stracke wrote:

> I'm now trying to argue that a CUA might need to be able to specify wha=
t
> languages its user understands, so that a CS can pick out an appropriat=
e
> translation of the iCalendar object.

Maybe I'm missing something here.  If I type "meeting with George" or"ren=
contrant
George" or "George treffen" or even "=C6=FC=CB=DC=B8=EC George", then tha=
t's what I'd expect to be
stored on the CS and that I'd get back in the CUA.  The CS shouldn't be t=
ranslating
behind the scenes.  At most, the client could translate when specifically=
 asked to by
the user. But I think we're off the topic of the CAP protocols at this po=
int.

dmadeo

--------------8B1C70385959C67DDEE0FD5C
Content-Type: text/x-vcard; charset=us-ascii;
 name="dmadeo.vcf"
Content-Description: Card for David Madeo
Content-Disposition: attachment;
 filename="dmadeo.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Madeo;David
tel;fax:212-762-1009
tel;work:212-762-2348
x-mozilla-html:FALSE
url:www.ms.com
org:Morgan Stanley Dean Witter and Discover;Information Technology
version:2.1
email;internet:dmadeo@ms.com
adr;quoted-printable:;;750 Seventh Ave=0D=0A;NY;NY;10019;USA
x-mozilla-cpt:;0
fn:David Madeo
end:vcard

--------------8B1C70385959C67DDEE0FD5C--



From owner-ietf-calendar@imc.org  Fri Apr  9 07:32:14 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01070
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:32:13 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id XAA11655
	for ietf-calendar-bks; Thu, 8 Apr 1999 23:38:39 -0700 (PDT)
Received: from hqinbh1.ms.com (hqinbh1.ms.com [205.228.12.71])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id XAA11649
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 23:38:38 -0700 (PDT)
Received: (from uucp@localhost)
        by hqinbh1.ms.com (8.8.6/fw v1.30) id CAA16008;
        Fri, 9 Apr 1999 02:38:30 -0400 (EDT)
Received: from unknown(144.14.19.186) by hqinbh1.ms.com via smap (4.1)
	id xma015967; Fri, 9 Apr 99 02:38:25 -0400
Received: from ms.com (eqhq50.morgan.com [205.228.83.50])
        by sasmh1.ms.com (8.8.5/hub+ldap v2.3) with ESMTP id CAA12677;
        Fri, 9 Apr 1999 02:38:23 -0400 (EDT)
Message-ID: <370DA05F.58B61239@ms.com>
Date: Fri, 09 Apr 1999 02:38:23 -0400
From: David Madeo <dmadeo@ms.com>
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
CC: "'Antoine Leca'" <Antoine.Leca@renault.fr>,
        Doug Royer <Doug.Royer@Sun.COM>, ietf-calendar@imc.org
Subject: Re: error codes
References: <FD7A762E588AD211A7BC00805FFEA54B0246D7F4@HYDRANT>
Content-Type: multipart/mixed;
 boundary="------------E2B4D8D9B255FC4D6100CD5E"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------E2B4D8D9B255FC4D6100CD5E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Lisa Lippert (Dusseault) (Exchange)" wrote:

> There seems to be an assumption that whenever there is human-readable text
> included, that the server must be able to translate that into the
> appropriate language for the user.  Why is that?  Antoine's example of a
> specific dialect is a good example why we can't expect that to happen.
> Instead, Antoine's "ca-valencia-FR" client, which is carefully designed to
> use proper dialect and (if it's a GUI) well-formatted dialog boxes of some
> kind, will know all the standard errors and have a table mapping them to
> appropriate catalan strings.  The client might even have additional
> information it can tack on.  An english client might even receive the error
> code "4.5.8  BADLY FORMATTED DATA"  and instead display it to the user as
> "An error was received from the server which indicated that data was
> improperly formatted".  Or the client might choose to do something
> completely different than to display a text error.  Summary:  the client
> will choose what to display anyway, so text error messages shouldn't be
> translated/formatted for the client.
>
> Instead, I've always understood text-based error messages in protocols to be
> a convenience for protocol and implementation designers, testers, coders,
> debuggers, system administrators, etc.  This makes it possible to use
> strings which are brief but informative to techies, like "BADLY FORMATTED
> VCAR".

I agree with most of what Lisa (and the others) are saying on this.  However,
the dissenting view convinced me.  To reiterate: 1) Adding text of any
nationality makes the parsing more difficult, especially since it might include
data as well as a return code (referrals).   2) People working with older
protocols had found that developers had hard coded parsing based on the
"friendly" text and were now locked into that format going forward.  Does anyone
disagree with these two points?  Unless they can be refuted, my opinion is that
I'd like to keep the parsing as easy to do as possible.  That outweighs the
slight gain in ease of use for an administrator.

I'd suggest that the RFC define each return code and the accompanying English
text to explain it.  A CS MUST reply with only the return code.  It MAY (if it
would like to make it's users happy) log the accompanying text (or it's
translated equivalent) or even Lisa's example text.  An especially industrious
implementor would include a wrapper for snoop or tcpdump or your favorite packet
sniffer which would provide a similar service.  As a customer/administrator,
that would be good enough for me.

I'm deliberately avoiding the topic of whether error messages should be
extensible.  Andre's example of "Bad Data"->"Bad Vcar"->"Bad CalID" is a
reasonable one.  But of course, you'd still need to go through the process of
registering the extensions, otherwise there's the potential for conflict.  Your
bad CalID is my password incorrect.

One question that keeps coming up is "what about errors we didn't envision
during this process".  Isn't that why so many people are vetting this?
Alternatively, that's what version 2 is for.   Antoine uses the example of disk
full.  Isn't there a big difference between protocol errors and what the CS is
logging behind the scenes?

Hopefully, we can come to agreement on this part of the discussion so that we
can start coming up with more CAP examples and focus on the difficult issues of
hierarchy, users vs calendars, and access control.

Thanks,

dmadeo


>
>
> -----Original Message-----
> From: Antoine Leca [mailto:Antoine.Leca@renault.fr]
> Sent: Wednesday, April 07, 1999 3:10 AM
> To: Doug Royer
> Cc: ietf-calendar@imc.org
> Subject: Re: error codes
>
> Doug Royer wrote:
> >
> > The 'iCalendar'-LANG parameter is what many people call LOCALE (as in
> > 'en-us' vs 'en-uk' vs 'fr-ch' vs ...).  And the (ISO?)  ~standard~ for
> > LOCALE is from the subset of LC_MONETARY, LC_TIME, LC_MESSAGES,
> > LC_CTYPE, LC_COLLATE, LC_NUMERIC.  Example:
>
> They are from the C language Standard (ISO/IEC 9899, aka ANSI C), except
> LC_MESSAGES which is from ISO/IEC 9915 aka POSIX.
>
>
> >         (There are probably more ...)
>
> Not that I know of.
>
>
> > As to error messages that are intended to be human readable:
> >
> >     In order for there to be an error code to include a human readable
> >     error message, the CS MUST have 2 things:
> >
> >                 1) The iCalendar-LANG (or LOCALE) of the CUA
>
> Agreed.
>
>
> >                 2) The charset of the CUA.
>
> Disagree.  What it needs is the charset used in the interchange.  Then
> the CUA should be responsible to present it in the proper way to the user,
> and this is completely outside the scope of the job on the server side
> (think about GUI CUAs where the effective charset is really arrays of
> pixels!)
>
> >  -  With human readable error messages and IF the MUST implement for
> >     CAP is UTF-8, then;  The CS still needs to have a message catalog
> >     for all of the possible LANGs (LOCALEs) that a CUA might use.
>
> I believe this is too large as a requirement: suppose I write a
> ca-valencia-FR
> CUA (Valencian version of Catalan as used in France): should all CS all over
> the world have to catter with my very specific LOCALE?  I even do not expect
> more than a pinch of CS to have messages in anything except English...
>
> So we need negociation and fallbacks here.  With them, we then can have
> a minimum (read: English) functionality.  Far from perfect, but better
> than nothing.
>
>
> >  -  If there is no default CHARSET, then the CS and CUA
> >     MUST agree on the CHARSET, or you can not interoperate at all.
>
> Agreed.
>
> > -   If however there are NO messages from the CS that are intended
> >     to be human readable:
> >
> >     There is now less of a reason to support a large number
> >     of CHARSETs in the CS. And there may be NO reason to
> >     support multiple LANGs (LOCALEs) in the CS over CAP.
>
> Right, but...
>
>
> >     If the error messages are some kind of string (numeric or not), and
> >     the data presented in a formatted way (Just an example):
> >
> >         1.2.3 cap://www.foo.com/abc x-y-z
> >
> >     The CUA and the CS could both know in any language and locale
> >     this means something specific. For example:
> >
> >         If 1.2.3 meant: permission denied
> >         And x-y-z meant: CS performing backup - try later
>
> This one is clear enough (although I doubt we have to be that precise).
>
> But how can a CS express something that was not envisionned in the specs.
> Examples might be "disk full", "disagree on TZ settings", "too much users
> connected", "please obtain a cookie from www.cake.com before continuing",
> "you are blacklisted", "only GTIML supported", "your driver is not
> compliant,
> upgrade to version 2.x.y", etc. (some may be already covered, some are not).
>
>
> > -  If CAP is going to allow other than non-UTF-8 charsets, then
> >    it is a MUST that the CUA and the CS MUST be able to default
> >    back to UTF-8.
>
> Certainly.  In fact, I do not believe non-UTF8 charsets are to be allowed
> (what can be the benefits?)
>
> Antoine

--------------E2B4D8D9B255FC4D6100CD5E
Content-Type: text/x-vcard; charset=us-ascii;
 name="dmadeo.vcf"
Content-Description: Card for David Madeo
Content-Disposition: attachment;
 filename="dmadeo.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Madeo;David
tel;fax:212-762-1009
tel;work:212-762-2348
x-mozilla-html:FALSE
url:www.ms.com
org:Morgan Stanley Dean Witter and Discover;Information Technology
version:2.1
email;internet:dmadeo@ms.com
adr;quoted-printable:;;750 Seventh Ave=0D=0A;NY;NY;10019;USA
x-mozilla-cpt:;0
fn:David Madeo
end:vcard

--------------E2B4D8D9B255FC4D6100CD5E--



From owner-ietf-calendar@imc.org  Fri Apr  9 07:32:15 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01087
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:32:14 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id TAA24178
	for ietf-calendar-bks; Thu, 8 Apr 1999 19:13:13 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id TAA24174
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:13:12 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA21721
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:13:10 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id TAA16983
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:13:07 -0700 (PDT)
Message-Id: <199904090213.TAA16983@engmail2.Eng.Sun.COM>
Date: Thu, 8 Apr 1999 19:13:09 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: RE: CAP Example READ-1
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: hrUcNGtyRElQDCQkyyOGbw==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@exchange.microsoft.com>
> Date: Thu, 8 Apr 1999 14:22:32 -0700 
> 
> SQL Cursors are cool and work well, but this would require a lot of state to
> be maintained on the server.  (Database servers are meant to do that, but we
> haven't really discussed whether that style of interaction is intended for
> CAP servers).  How many different calendar clients are going to have views
> into how many different calendars on one server?  

If it were done with a non-cursor method - it seems to me the same
state information would need to be maintained for the same number of
calendars on one server as with the cursor method?

> If the client can re-establish the context with each new request, then the
> server load becomes much more manageable.  That would require sending:
>  - the original search query, including ORDERBY
>  - the calid of the current item
>  - (possibly) how many rows to return.
> Now if the server happens to have the original search query cached it can be
> fast, and if it doesn't it can still respond.

Same with cursors - I don't see any difference here other then
the name and formatting of the method used to ask for the next data.

I simply proposed cursors because its an already standard thing
that we do not have to invent that many already know how to use.

-Doug



From owner-ietf-calendar@imc.org  Fri Apr  9 07:32:16 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01100
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:32:15 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id TAA24331
	for ietf-calendar-bks; Thu, 8 Apr 1999 19:17:11 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id TAA24327
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:17:10 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA22878
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:17:07 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id TAA17440
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:17:02 -0700 (PDT)
Message-Id: <199904090217.TAA17440@engmail2.Eng.Sun.COM>
Date: Thu, 8 Apr 1999 19:17:04 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: RE: CAP Example READ-1
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: HLfziiqVARO0ZaXo050fVA==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@exchange.microsoft.com>
> Date: Thu, 8 Apr 1999 14:25:51 -0700 
> 
> You're right, I forgot that we would need notification to do truly dynamic
> search folders.  But still, if a user asks for "first 20" items in a search,
> then an item is inserted #25, then 10 minutes later asks for "second 20
> items" in the same search, the user would like to see the new #25.

Agreed.

I think all of the proposals will work that way.

> -----Original Message-----
> From: Doug Royer [mailto:Doug.Royer@Sun.COM]
> 
> > From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
> > Date: Sun, 21 Mar 1999 13:34:41 -0800
> > 
> > Static searches are sometimes useful, but it annoys the user to be looking
> > through a list of online tasks and not see new ones as they appear.
> Dynamic
> > or repeatedly refreshed searches are required client functionality, and
> yet
> > there are still ways of getting row-ranges from them.  Tony listed one, I
> > just outlined a more generalized principle.
> 
> And how would your approach (in you previous post) show new events
> that appear after you look at them? There is no 'date entered' property.
> We only have LAST-MODIFIED and CREATED. And CREATED is the event
> creation time, not the time is was entered into the store. So an event
> could be stored that was created yesterday. It could be stored 1 second
> after you just viewed that time range.
> 
> I do not think the problem (...see new ones as they appear) is solvable
> with query. We deferred notification until CAP-2. Notification is what
> would be required to implement seeing them as inserted into the store.
> I don't see the above need as solvable with any query method.
> 
> > Lisa
> > 
> > -----Original Message-----
> > From: sman@netscape.com [mailto:sman@netscape.com]
> > Sent: Friday, March 19, 1999 12:47 PM
> > To: alext@cst.ca
> > Cc: ietf-calendar@imc.org
> > Subject: Re: CAP Example READ-1
> > 
> > 
> > hmm... I remember bringing that at the meeting: essentially to name or
> store
> > the
> > solution set to a query. There are issues with naming/storing/referring to
> > them on
> > the server. For instance, how long do you keep the solution set around?
> Most
> > people
> > just said to let the db subsystem worry about caching the querys/solution
> > sets.
> > 
> > Comments?
> > 
> > -Steve
> > 
> > Alexander Taler wrote:
> > 
> > > Unless the server stores the results of the initial search and
> > > subsequent reads are performed on the same data set there are serious
> > > problems with this approach.
> > >
> > > If data is deleted between queries the position of the results may
> > > change, so that what was result 12 on the first query may become
> > > result 8 for the second query.  If I query for the first 10 and then
> > > second 10 I will never receive that information.  Similarly if data is
> > > added I may end up receiving the same information twice.
> > >
> > > So, if we really want the ability to incrementally retrieve data from
> > > a search we need to add a facility for referencing search results on
> > > the server.
> > >
> > > Steve Mansour wrote:
> > > >
> > > > OK that was probably it.  I like the resultstart, maxresults
> combination
> > the
> > > > best.  Since that's what you proposed, I take it you prefer that as
> > well.
> > > > -Steve
> > > >
> > > > "Tony Small (Exchange)" wrote:
> > > >
> > > > > I originally suggested having two properties- resultstart and
> > resultend.
> > > > > Then I think Bruce Kahn suggested having resultstart with
> maxresults.
> > (I
> > > > > cut out myself as the middleman. :-)
> > > > >
> > > > > -----Original Message-----
> > > > > From: sman@netscape.com [mailto:sman@netscape.com]
> > > > > Sent: Thursday, March 18, 1999 5:57 PM
> > > > > To: Tony Small (Exchange)
> > > > > Cc: CalSched IETF
> > > > > Subject: Re: CAP Example READ-1
> > > > >
> > > > > This sounds reasonable to me.  I've made the update.  I think that
> > someone
> > > > > at
> > > > > the meeting might have had another suggestion (please speak up if
> > you're out
> > > > > there).
> > > > > -Steve
> > > > >
> > > > > "Tony Small (Exchange)" wrote:
> > > > >
> > > > > > Can we add a RESULTSTART property?  For instance:
> > > > > >
> > > > > > C: MAXRESULTS:20
> > > > > > C: RESULTSTART:10
> > > > > >
> > > > > > This example would return the results 10 through 30.
> > > > > > If there is no resultstart, then it's assumed to be zero.
> > > > > >
> > > > > > If a CUA can retrieve a specific number of results, it would seem
> > that it
> > > > > > would also need to be able to retrieve results that follow.  We
> > wouldn't
> > > > > > want to have to retrieve more than needed.
> > > > > >
> > > > > > Tony
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: sman@netscape.com [mailto:sman@netscape.com]
> > > > > > Sent: Wednesday, March 17, 1999 9:24 AM
> > > > > > To: CalSched IETF
> > > > > > Subject: CAP Example READ-1
> > > > > >
> > > > > > Example READ-1
> > > > > >
> > > > > > This example shows how the READ command can be used to read events
> > in a
> > > > > > particular time range from multiple calendars.
> > > > > >
> > > > > > C: 10 READ VEVENT relcal2 ://bobo.ex.com/relcal3
> > > > > > S: 10 2.0 cap://cal.example.com/relcal2
> > > > > > S: 10 2.2 cap://bobo.ex.com/relcal3
> > > > > > C: 10 SENDDATA
> > > > > > S: 10 2.0.1
> > > > > > C: CONTENT-TYPE: text/calendar; method=read; component=VCOMMAND
> > > > > > C:
> > > > > > C: BEGIN:VCALENDAR
> > > > > > C: VERSION:2.1
> > > > > > C: METHOD:READ
> > > > > > C: BEGIN:VCOMMAND
> > > > > > C: BEGIN:VQUERY
> > > > > > C: MAXRESULTS:20
> > > > > > C: MAXSIZE:17000000
> > > > > > C: QUERYNAME:MyViewRange
> > > > > > C: QUERY:SELECT (DTSTART,DTEND,SUMMARY,UID);
> > > > > > C:   FROM VEVENT;
> > > > > > C:   WHERE (DTEND >= 19990310T080000Z AND DTSTART <=
> > 19990310T190000Z);
> > > > > > C:   ORDERBY (DTSTART ASC, DTEND, UID, SUMMARY)
> > > > > > C: END:VQUERY
> > > > > > C: END:VCOMMAND
> > > > > > C: END:VCALENDAR
> > > > > > C: .
> > > > > > S: 10 2.0 cap://cal.example.com/relcal2
> > > > > > S: Content-type: text/calendar; Method=RESPONSE; Component=VDATA;
> > > > > > Optinfo=VERSION 2.1
> > > > > > S: Content-Transfer-Encoding: 7bit
> > > > > > S:
> > > > > > S: BEGIN:VCALENDAR
> > > > > > S: VERSION:2.1
> > > > > > S: METHOD:RESPONSE
> > > > > > S: BEGIN:VDATA
> > > > > > S: BEGIN:VEVENT
> > > > > > S: DTSTART:19990310T090000Z
> > > > > > S: DTEND:19990310T100000Z
> > > > > > S: UID:1234
> > > > > > S: SUMMARY:Big time meeting
> > > > > > S: END:VEVENT
> > > > > > S: BEGIN:VEVENT
> > > > > > S: DTSTART:19990310T130000Z
> > > > > > S: DTEND:19990310T133000Z
> > > > > > S: UID:5678
> > > > > > S: SUMMARY:small time meeting
> > > > > > S: END:VEVENT
> > > > > > S: END:VDATA
> > > > > > S: END:VCALENDAR
> > > > > > S: .
> > > > > > S: 10 2.0 cap://bobo.ex.com/relcal3
> > > > > > S: Content-type: text/calendar; Method=RESPONSE; Component=VDATA;
> > > > > > Optinfo=VERSION 2.1
> > > > > > S: Content-Transfer-Encoding: 7bit
> > > > > > S:
> > > > > > S: BEGIN:VCALENDAR
> > > > > > S: VERSION:2.1
> > > > > > S: METHOD:RESPONSE
> > > > > > S: BEGIN:VDATA
> > > > > > S: BEGIN:VEVENT
> > > > > > S: DTSTART:19990310T140000Z
> > > > > > S: DTEND:19990310T143000Z
> > > > > > S: UID:1919191
> > > > > > S: SUMMARY:Summer budget meeting
> > > > > > S: END:VEVENT
> > > > > > S: END:VDATA
> > > > > > S: END:VCALENDAR
> > > > > > S: .
> > > >
> > > >
> ----------------------------------------------------------------------
> > > >
> > > >   Steve Mansour <sman@netscape.com>
> > > >   Judge, Jury, and Executioner
> > > >   Netscape
> > > >
> > > >   Steve Mansour
> > > >   Judge, Jury, and Executioner  <sman@netscape.com>
> > > >   Netscape
> > > >   Mountain View                 Fax: 650-937-2103
> > > >   CA                            Work: 650-937-2378
> > > >   94043                         Netscape Conference Address
> > > >                                 Netscape Conference DLS Server
> > > >   Additional Information:
> > > >   Last Name     Mansour
> > > >   First Name    Steve
> > > >   Version       2.1
> 
> -Doug
> -------------------------------------------------------------------
> Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
> 801 W. El Camino #131		Work:   (650)786-7599
> Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Fri Apr  9 07:32:17 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01111
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 07:32:16 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id TAA23829
	for ietf-calendar-bks; Thu, 8 Apr 1999 19:06:12 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id TAA23823
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:06:11 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA20406
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:06:09 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id TAA16172
	for <ietf-calendar@imc.org>; Thu, 8 Apr 1999 19:06:06 -0700 (PDT)
Message-Id: <199904090206.TAA16172@engmail2.Eng.Sun.COM>
Date: Thu, 8 Apr 1999 19:06:08 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: RE: error codes
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 37S1COukkrtnXYgF3wwQRA==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@exchange.microsoft.com>
> Date: Thu, 8 Apr 1999 14:02:22 -0700 
> 
> There seems to be an assumption that whenever there is human-readable text
> included, that the server must be able to translate that into the
> appropriate language for the user.  Why is that?

I see it as two valid new points.
	
	1) There are some status messages that can't be covered
	   with generic messages numbers.
	   
	2) Forcing a CUA in France or Japan to display CS status
	   messages of a non-critical nature in English is bad manners.

> Antoine's example of a
> specific dialect is a good example why we can't expect that to happen.
> ...
> 
> Instead, I've always understood text-based error messages in protocols to be
> a convenience for protocol and implementation designers, testers, coders,
> debuggers, system administrators, etc.  This makes it possible to use
> strings which are brief but informative to techies, like "BADLY FORMATTED
> VCAR".

Perhaps a compromise.

Maybe we can have some kind of tag or rule so that the CUA knows
that a specific status message from the CS is not a typical status
message, but something that the CUA really needs to display to the user.

Perhaps a '*' could be used to mean "this really needs to be seen
by a user":

	1.2.3 cap://host.com/a/b/c * "this needs to be displayed"
	
Most IMAP server messages are not displayed to the users. So adding
them in the same way as IMAP I think would simply not gain anything
at all. They would not be displayed anyway.

Also I think the standard status messages should be optional.

-Doug



From owner-ietf-calendar@imc.org  Fri Apr  9 12:22:04 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04225
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 12:22:03 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id IAA29136
	for ietf-calendar-bks; Fri, 9 Apr 1999 08:53:57 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id IAA29130
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 08:53:56 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id IAA13163
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 08:53:50 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id LAA08820
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 11:56:11 -0400
Message-ID: <370E231B.C1567ACD@ecal.com>
Date: Fri, 09 Apr 1999 15:56:11 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: error codes
References: <FD7A762E588AD211A7BC00805FFEA54B0246D7F4@HYDRANT> <370DA05F.58B61239@ms.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

David Madeo wrote:

> I'd suggest that the RFC define each return code and the accompanying English
> text to explain it.  A CS MUST reply with only the return code.  It MAY (if it
> would like to make it's users happy) log the accompanying text (or it's
> translated equivalent) or even Lisa's example text.  An especially industrious
> implementor would include a wrapper for snoop or tcpdump or your favorite packet
> sniffer which would provide a similar service.

Bleah.  I don't like solutions which require the user to employ packet sniffing.
What if they're on a multiuser machine; do you want them to see other people's
sessions? (More likely, of course, they just won't be allowed to sniff anything.)
What if the calendar admin is not the superuser on the calendar server? What if the
user's on an OS which simply cannot support sniffers? (E.g., a cellphone of 2004
might well contain an IP stack, and a bare-bones CUA would be an obvious app to
include; but it probably won't be running an OS where the user can run third-party
software.)

I like Doug's suggestion, where a status report can consist of three parts:

   * A standard error code which the CUA can understand (MUST).
   * Descriptive text for debugging purposes (SHOULD).  Not necessarily in English,
     of course; it can be in the implementor's own language, or an implementor can
     make it localizable.
   * User-visible text which must be localizable.  (SHOULD, whenever the server has
     useful details that can't be conveyed in a standard error code.) How a server
     localizes text sent to a client is an interesting problem, of course.

> One question that keeps coming up is "what about errors we didn't envision
> during this process".  Isn't that why so many people are vetting this?

Yes, but we're rushed; we have to get this done by July, and it's not so improbable
that we'll miss some stuff.

> Alternatively, that's what version 2 is for.

Big-bang version changes in protocols are a Bad Thing.  Good protocols are smoothly
extensible.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Fri Apr  9 12:36:03 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04363
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 12:36:02 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id JAA29218
	for ietf-calendar-bks; Fri, 9 Apr 1999 09:01:14 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id JAA29214
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 09:01:14 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id JAA14096
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 09:01:08 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id MAA08834
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 12:03:30 -0400
Message-ID: <370E24D2.934EDBD3@ecal.com>
Date: Fri, 09 Apr 1999 16:03:30 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: CUA capabilities
References: <199904052126.OAA27260@engmail2.Eng.Sun.COM> <370B6BAD.B4C240FA@ecal.com> <370DA5BD.4E9652BB@ms.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

David Madeo wrote:

> > I'm now trying to argue that a CUA might need to be able to specify what
> > languages its user understands, so that a CS can pick out an appropriate
> > translation of the iCalendar object.
>
> Maybe I'm missing something here.  If I type "meeting with George" or"rencontrant
> George" or "George treffen" or even "ÆüËÜ¸ì George", then that's what I'd expect to be
> stored on the CS and that I'd get back in the CUA.

OK, so what do you do if you've got an event announcement (say, a soccer match) where
you'll have people attending who speak many different languages? You want each user to
see the announcement in their own language, which means the CS needs to be able to
present multiple versions and  CUA and the CS need to do content negotiation.  The CS
doesn't need to do the translation itself (though that may be an option eventually); it
would suffice for there to exist some (possibly proprietary) mechanism whereby the
alternative renditions can be provided for it to store.

> But I think we're off the topic of the CAP protocols at this point.

No, because, to do the above content negotiation, CAP needs to be able to express the
user's preferred language.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Fri Apr  9 12:37:48 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04404
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 12:37:47 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id JAA29263
	for ietf-calendar-bks; Fri, 9 Apr 1999 09:06:46 -0700 (PDT)
Received: from newshub1-work.home.com (newshub1-work.home.com [24.0.0.24])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id JAA29259
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 09:06:46 -0700 (PDT)
Received: from ariel.appoint.lan (ATHM-209-218-xxx-130.Home.net [209.218.166.130])
	by newshub1-work.home.com (8.8.5/8.8.5-AtHome) with ESMTP id JAA14784
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 09:06:40 -0700 (PDT)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id MAA08842
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 12:09:02 -0400
Message-ID: <370E261D.CEB23F86@ecal.com>
Date: Fri, 09 Apr 1999 16:09:02 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: CUA capabilities
References: <199904072105.OAA11998@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer wrote:

> > > it would mean that the CUA could not forward the message via iMIP.
> > > Which one would it send?
> >
> > But CAP and iTIP are orthogonal.  A CS that uses CAP to talk to CUAs
> > might use an extended protocol (iTIP with proprietary extensions, or
> > future standard extensions) to talk to other CSes.  It would be a Good
> > Thing if CAP1 clients could get the benefit (or, at least, not be shut
> > out by an incompatible transition to CAP2).
> [...]
> I think that fanout is 'in'. And that means that a CAP message
> can be forwarded via iMAP.

(I assume you mean iMIP.) "Can", yes, but that doesn't mean that iTIP is the only
mechanism the CS can use.

> I think that each side sending CAPABILITY might get into the
> same problems.

Perhaps--but at least it's an escape hatch.  If we find that CAPABILITIES works
only for a limited class of extensions, and come up with a better way eventually,
then CUAs and CSes can use CAPABILITIES to announce that they support the better
way.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Fri Apr  9 15:12:51 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06291
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 15:12:50 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id LAA00547
	for ietf-calendar-bks; Fri, 9 Apr 1999 11:20:37 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id LAA00543
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 11:20:36 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA27883
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 11:20:31 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id LAA01242
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 11:20:28 -0700 (PDT)
Message-Id: <199904091820.LAA01242@engmail2.Eng.Sun.COM>
Date: Fri, 9 Apr 1999 11:20:29 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: CUA capabilities
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=ISO-8859-1
Content-MD5: vAICC3PNMijGDfVMvpO29g==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mail.proper.com id LAA00544
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit


> Date: Fri, 09 Apr 1999 16:03:30 +0000
> From: John Stracke <francis@ecal.com>
> 
> David Madeo wrote:
> 
> > > I'm now trying to argue that a CUA might need to be able to specify what
> > > languages its user understands, so that a CS can pick out an appropriate
> > > translation of the iCalendar object.
> >
> > Maybe I'm missing something here.  If I type "meeting with George"
> > or"rencontrant George" or "George treffen" or even "ÆüËÜ¸ì George",
> > then that's what I'd expect to be stored on the CS and that I'd get
> > back in the CUA.
> 
> OK, so what do you do if you've got an event announcement (say, a
> soccer match) where you'll have people attending who speak many
> different languages? You want each user to see the announcement in
> their own language, which means the CS needs to be able to
> present multiple versions and  CUA and the CS need to do content
> negotiation.  The CS doesn't need to do the translation itself (though
> that may be an option eventually); it would suffice for there to exist
> some (possibly proprietary) mechanism whereby the alternative renditions
> can be provided for it to store.

It would be nice. In order for that to happen we have
to extend something - iTIP and iCal. As there is no way to transmit
that message via iMIP. Because only one DESCRIPTION is allowed in
a VEVENT. And a VEVENT is unique per UID. There can not be different
VEVENTS with the same UID, some with DESCRIPTION;param-set-1
and others with DESCRIPTION;param-set-2.

At some point it would not be possible to tell which was the
correct version.

If a user in lang-1 were to send back a correction to the CS
would the CS know how to translate that back into the other supported
languages? Or would the user not be allowed to update a DESCRIPTION
unless they knew every language the CS might have stored the VEVENT in?
Or would it be allowed that the DESCRIPTION for one language did not
evaluate to the same thing in another language? 

I can see how a vertical application CS might want to do this.
I can not see how a general purpose CS could ever do this.

So I go back to ...

> > But I think we're off the topic of the CAP protocols at this point.
> 
> No, because, to do the above content negotiation, CAP needs to be able to
> express the user's preferred language.

I agree - but that is a separate issue from being able to display
the same UID in different languages.

I want the CUA to send down its prefered charset and lang to the CS
so that the CUA and CS can decide what is best for the application.

If they can't agree on charst - then its UTF-8.
If they can't agree on language - then is up to the CS.

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Fri Apr  9 17:24:53 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07630
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 17:24:52 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA02092
	for ietf-calendar-bks; Fri, 9 Apr 1999 13:51:31 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id NAA02087
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 13:51:30 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA29949
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 13:51:32 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id NAA06959
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 13:51:28 -0700 (PDT)
Message-Id: <199904092051.NAA06959@engmail2.Eng.Sun.COM>
Date: Fri, 9 Apr 1999 13:51:30 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: RE: error codes
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=ISO-8859-1
Content-MD5: E40dT+qW7Q7on7I+qZfOzA==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mail.proper.com id NAA02088
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit


> Date: Fri, 9 Apr 1999 09:14:16 +0200
> From: Patrik Fältström  <paf@swip.net>
> 
> Regarding error codes, please check the discussions / drafts etc from 
> the ftpext working group working with internationalization and 
> standardization of ftp.
> 
> There might be some ideas you can borrow from that wg.

Thanks!

I have included some of that draft below - more information is in
the ftpext draft in section 4.

An excerpt from FTPEXT (draft-ietf-ftpext-intl-ftp-06.txt):

4. Language Support

  The Character Set Workshop Report [RFC2130] suggests that clients and
  servers SHOULD negotiate a language for "greetings" and "error
  messages". This specification interprets the use of the term  "error
  message", by RFC 2130, to mean any explanatory text string returned by
  server-PI in response to a user-PI command.

  Implementers SHOULD note that FTP commands and numeric responses are
  protocol elements. As such, their use is not affected by any guidance
  expressed by this specification.

  Language support of greetings and command responses shall be the
  default language supported by the server or the language supported by
  the server and selected by the client.

  It may be possible to achieve language support through a virtual host
  as described in [MLST]. However, an FTP server might not support
  virtual servers, or virtual servers might be configured to support an
  environment without regard for language. To allow language negotiation
  this specification defines a new LANG command. Clients and servers
  that comply with this specification MUST support the LANG command.

4.1 The LANG command

  A new command "LANG" is added to the FTP command set to allow server-
  FTP process to determine in which language to present server greetings
  and the textual part of command responses. The parameter associated
  with the LANG command SHALL be one of the language tags defined in RFC
  1766 [RFC1766]. If a LANG command without a parameter is issued the
  server's default language will be used.

  Greetings and responses issued prior to language negotiation SHALL be
  in the server's default language. Paragraph 4.5 of [RFC2277] state
  that this "default language MUST be understandable by an English-
  speaking person". This specification RECOMMENDS that the server
  default language be English encoded using ASCII. This text may be
  augmented by text from other languages. Once negotiated, server-PI
  MUST return server messages and textual part of command responses in
  the negotiated language and encoded in UTF-8. Server-PI MAY wish to
  re-send previously issued server messages in the newly negotiated
  language.

 The LANG command only affects presentation of greeting messages and
  explanatory text associated with command responses. No attempt should

 be made by the server to translate protocol elements (FTP commands and
  numeric responses) or data transmitted over the data connection.

  User-PI MAY issue the LANG command at any time during an FTP session.
  In order to gain the full benefit of this command, it SHOULD be
  presented prior to authentication. In general, it will be issued after
  the HOST command [MLST]. Note that the issuance of a HOST or REIN
  command [RFC959] will negate the affect of the LANG command. User-PI
  SHOULD be capable of supporting UTF-8 encoding for the language
  negotiated. Guidance on interpretation and rendering of UTF-8, defined
  in section 3, SHALL apply.

  Although NOT REQUIRED by this specification, a user-PI SHOULD issue a
  FEAT command [2389] prior to a LANG command. This will allow the user-
  PI to determine if the server supports the LANG command and which
  language options.

  In order to aid the server in identifying whether a connection has
  been established with a client which conforms to this specification or
  an older client, user-PI MUST send a HOST [MLST] and/or LANG command
  prior to issuing any other command (other than FEAT [2389]). If user-
  PI issues a HOST command, and the server's default language is
  acceptable, it need not issue a LANG command. However, if the
  implementation does not support the HOST command, a LANG command MUST
  be issued. Until server-PI is presented with either a HOST or LANG
  command it SHOULD assume that the user-PI does not comply with this
  specification.

 .... more in the FTPEXT draft...

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Fri Apr  9 17:45:41 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07782
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 17:45:40 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA02070
	for ietf-calendar-bks; Fri, 9 Apr 1999 13:49:28 -0700 (PDT)
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id NAA02066
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 13:49:25 -0700 (PDT)
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
	id AA28240; Fri, 9 Apr 99 16:50:22 EDT
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
	by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id QAA17615
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 16:49:25 -0400 (EDT)
Received: from mona-lisa (MONA-LISA.MIT.EDU [18.172.1.179])
	by melbourne-city-street.MIT.EDU (8.9.2/8.9.2) with SMTP id QAA11284
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 16:49:24 -0400 (EDT)
Message-Id: <3.0.2.32.19990409164603.03b8c640@po10.mit.edu>
X-Sender: pbh@po10.mit.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)
Date: Fri, 09 Apr 1999 16:46:03 -0400
To: ietf-calendar@imc.org
From: "Paul B. Hill" <pbh@mit.edu>
Subject: (long) problems with CAP not having "users" and hierarchical
  calendars
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hi,

I appologize for the long, dense posting but I think these are issues that
need to be considered within the working group. Please don't quote the
entire message when responding. I think everyone will be happier if you
just extract short section to comment on, and modify the subject line to
indicate the particilar point that is being addressed.

After having an out of band conversation with several of the CAP editors
about what we mean by "user" and the fact that the CAP Requirements
document says that CAP does not define "users", it looks like we need to
further refine the definitions. Thinking this through has an impact on how
we think about hierarchical calendars, group operations, fan-out, and the
opaqueness of CALIDs. Many of the CAP editors and other members of the
working group helped to flesh this out but none of them are responsible for
the contents of this particular message.

One of the key points of this discussion is that we often overload the term
"user". I think we have been falling into the pattern where designers often
think of a how a program "talks" to another when it's the people using the
program that is important.  As Bob Mahoney pointed out to me, "user's bleed
when you stick them with a needle." Usernames,  principal identifiers, or
authentication-ids are used by people to indicate to a system that, "I am
me, now I want to do the following operations."

More specifically, I am not confident that we can easily get to a point
where a CAP user will be able to perform two tasks that all customers will
expect to be able to perform, given the current text of the documents. The
first task is, "I am me, let me modify calendars that I already know
about." The second task is, "I am me, let me invite (or whatever) this
other person without knowing the details of what the real calid is.

This all got started when I came back from one of the interim meetings and
asked myself, "What are the implications of hierarchical calendars when
determining when a user might be available for a meeting?" And, "If I want
to insert a VEVENT into a calendar, for use by another user, into which
hierarchical calendar do I make the insertion?" This is a key point. Just
because I have a soccer calendar doesn't mean that other users should
attempt to place an invitation to a weekly pickup game in the calendar. It
might be my sister's soccer schedule. It's up to me to determine where an
invitation belongs.

In the previous paragraph I mean "user" to imply a person or customer of a
C&S system. I do not mean to imply any equivalency between a person and the
CUA that the person may use. In the original conversation it took several
iterations to make that assumed distinction well understood.

When reading the following paragraph from iCalendar I had always assumed
(and others seemed to as well) that "calendar user" and "user" usually
implied a person, or in some cases a resource such as a conference room.
(This is more accurately termed a "principal" within the security
community.) I never conceptualized these as CUA. Furthermore I always
assumed that this paragraph, and others, implied a relationship between a
user and a calendar. 

When used to request  free/busy time information, the "ATTENDEE" property
specifies the calendar users whose free/busy time is being requested; the
"ORGANIZER" property specifies the calendar user who is requesting the
free/busy time; the "DTSTART" and "DTEND" properties specify the window of
time for which the free/busy time is being requested; the "UID" and
"DTSTAMP" properties are specified to assist in proper sequencing of
multiple free/busy time requests.

On the other hand the CAP Requirements document clearly states that such a
relationship does not exist.

CAP does not define users. CAP does not define any default or implied
relationship between a user and a calendar. Users, via a CUA, authenticate
themselves to a CS to access information. All access is subject to access
control.

Having read this too many times I think that the preceding paragraph
overloads the term "user". Instead we probably want to introduce the terms
"authentication-id" and "principal" and carefully define them. However,
even if we do this, I do not think we have agreement about any default or
implied relationship between a calendar and a "user" (where I mean "user"
to be a person or customer of a C&S system.)

Before we go too much further, let's stop and think about how a person
would interact with a single server system that implements hierarchical
calendars with opaque CalIDs. 

Sidebar:

By opaque CalIDs I mean that the Relative CalID does not have a well
defined delimiter character that can be used to imply hierarchy to the end
user. And the Relative CalID contains no information that implies a context
to the end user. For example a Relative CalID of "joe" does not imply that
this calendar has anything to do with an end user named Joe. Another way to
think about it is that Joe's Relative CalID may be "joe" but that does not
imply that my Relative CalID is "pbh". For now I am treating the ongoing
discussion about delimiter characters and readability of a Relative CalID
as separate issue that will be resolved by the working group.


Just be sure that we're all on the same page the current definitions that I
am using state:

Calendar Identifier:
Also known as "CalID". A globally unique identifier associated with a
calendar within a CS.

Relative Calendar Identifier:
Also known as "Relative CalUID". A identifier for an individual calendar in
a calendar store. It is unique within a calendar store. It is recommended
to be globally unique. [Careful, some could interpret this to mean that it
is not just a username but it could be an LDAP distinguished name. Others
interpret this to mean that it is not a name but is more likely an
algorithmically derived GUID.] A Relative CalID consists of the portion of
the "scheme part" of a Qualified CalID following the Calendar Store
Identifier. This is the same as the "URL path" of the "Common Internet
Scheme Syntax" portion of a URL, as defined by [RFC1738].


As an initial example let's assume the our server has the following
Relative CalIDs:

17075
17075%20101
17075%20121
14612
14612%20101
14612%2011799

How do I, Paul, tell our example server that I would like to examine Bob's
calendar to see if he has a scheduled appointment for 2:00pm on Wednesday,
April 7th, 1999?

At first glance I was tempted to say that I'd have to learn the mapping
between Bob-the-user and Bob's CalID. I might get this from a directory. I
might get this from Bob's business card, his vCard, a phone conversation,
or maybe he sent it to me via email. Others have pointed out that this is
solved by the currently expired working group document,
draft-calsch-locating-01.txt. Unfortunately, I do not think this draft has
been well reviewed or discussed by the working group. 

As soon as we say we have hierarchical calendars I don't think that these
mechanisms are an adequate solution, if they ever were. The locating draft
introduces the concept of a default calendar for a user and mentions that
the default calendar may include rolled-up information from all the user's
other calendars. No working group document talks about "roll-up", whether
or not it is mandatory or optional, or how a user would control the roll-up.

Sidebar:

Roll-up or rollup is a consolidated view of multiple calendars. Another way
to think about roll-up is to think of it as document view of multiple
calendars.
But roll-up is more than just what calendars are "mine". There are many
cases where I'd want a sub-calendar which should not be used to determine
free/busy times. One example might be a calendar which represents the
office hours for members of a particular product team. It would be
reasonable for them to double book, or multiple book, that time. 

During the working group meeting in Minneapolis there was a brief
discussion about hierarchical calendars, although the term sub-calendars
was used. "Does a parent calendar inherit the contents of its
sub-calendars?" The current answer is no; it was pointed out that this may
complicate the CUAs, because they have to descend down through the tree.
(The CUA can request data from multiple calendars at once; but it
apparently has to descend the tree to know which calendars to request.)

Should there be a CAP operation that can be used to determine which
calendars I own? It's probably too much to ask which calendars I have
access to. (What does ownership or access mean in this context?)

Given our current definition of hierarchical, or sub-calendars, I am pretty
happy that parent calendars do not inherit the contents of their
sub-calendars. But this flexibility comes at a cost of complexity. At the
moment the definition states:

 Hierarchical Calendars - 
A CS feature where calendars may contain sub-calendars. The top-most
calendar in a hierarchy of calendars is called the root calendar. There may
be multiple root calendars in a single CS. Within a hierarchy of calendars,
all sub-calendars have a calendar with a parent topographical relationship.
In addition, sub-calendars may have sub-calendars (child topographical
relationship). In addition, the sub-calendar may have one or more calendars
with a sibling topographical relationship.

But I have not located any text that talks about any implied relationship
between the structure of a hierarchy and the data contained within the
calendars. I like this. It means this implementation can be very flexible
but it has some implications that everyone should consider.

Let's take another example. Again we have a single server but we have
either Relative CalIDs that appear legible to many users, or maybe I am
actually showing  Calendar Names instead of CalIDs. For now let's just
pretend that this distinction is not important.

Here is our example hierarchy:

alice
alice/doctor-appointments
alice/soccer
alice/sales-meetings
bob
bob/soccer
bob/appointments

Given the proper access rights, isn't it true that Alice (the user) could
decide that alice/soccer was unnecessary because he is on the same team as
Bob (the user) so instead she just views bob/soccer to determine when they
will have a soccer game? Alice finds this convenient because Bob is the
team manager and should have accurate information. Also Alice is a fanatic
about system performance and might assume that the system will be more
efficient if the soccer information doesn't have to be written in multiple
locations.

It appears that this would be legal within the context of all of the
current working group documents. And with access control it could be very
practical. However, if the working group changes its current consensus and
decides that a parent calendar inherits the contents of it children then
this usage should either be prohibited, or we should expect to derive few
benefits from this "roll-up" feature.

This flexibility also makes it very difficult for Alice to determine which
CalID should be used when scheduling a meeting with Bob. Even the locating
draft does not try to address the semantics of a list of CalID's that may
be associated with a user.  Nor does the draft provide for a mechanism to
update this information. Going back to the example above, if Alice starts
using  bob/soccer to track her soccer games how is that communicated to
anyone else, when they want to determine busy time in Alice's schedule?

Now George just wants to determine when Alice is available for a meeting.
Does George have to discover the entire calendar hierarchy and then query
each calendar to determine if Alice has an appointment in it? Obviously
this would be very inefficient.

One editor counter comments that "if you want to send an email and make
sure that I get it on all my MUAs, you have to know ALL the email addresses
that I use. Right? This isn't a different matter here." I actually think it
is a very different matter. The average end user doesn't care if the other
end user gets the message on all their MUAs. The average end user expects
that the other users will actually check all of their email accounts and
respond or act in a timely manner. In the case of using a C&S system I
think there is a different expectation. Customers have the expectation that
if they examine the calendar to determine there are no conflicts there is
pretty good chance that the other party might be available. Customers will
be upset if they are later told, "No I can't make it, you forgot to check
my calendar that I use to track my group meetings." There will be an
expectation on the requestor's part that the CUA will be able to perform
the operation with ease and reliability. The typical customer will reject a
product that requires the user to maintain an arbitrary list of CalIDs via
a separate mechanism just to interact with one other user.

Let's suppose that I work for a company that does not want me to store
personal data on the company's computer resources. But, also suppose that I
have the mythical 9 to 5 job. Sometimes I work at night or on the weekends.
Sometimes I'm on call but not actually working at night unless there is a
problem that requires my attention. And during 9 to 5, my hours are still
pretty flexible. I may be out of the office taking care of some personal
chores. In this case I may have multiple calendars in multiple domains. I
have my work calendar within ms.com and a personal calendar at
mindspring.com. If you are at ms.com and you view my calendar I have
configured things so that you see both my work related appointments and my
personal appointments, subject to access control. But my personal
appointments reside at mindspring.com. This should mean that you will not
try to schedule me for a server migration the same night that I am
attending my daughter's school play. My appointment with a certain doctor
who's a well known AIDS researcher also shows up as blocked out time, but
since the details reside at mindspring.com, even the ms.com system
administrators won't be able to examine the details. On the other hand
suppose you are not one of my co-workers, but you are a friend. You access
my calendar via mindspring.com. In this case I have configured things so
that M-F 7am to 6pm blocked off.

So, why do we have hierarchical calendars?

It appears that at least one potential customer is "interested in multiple
calendars with varying degrees of opaqueness from a free/BUSY point of
view."  "This fits into how we work, where I have different projects that
I share with others. There's also calendars that I want to inherit from the
firm (such as interesting business dates, unusual holidays, etc)."

The same customer goes on to say, "If I somehow query a server for the busy
time of a particular user, I think the server is responsible for verifying
that I'm allowed to see that and if so, then providing a single unified
view of the busy time.  Wherever it's looking at a single calendar, or
multiple calendars (potentially on other servers via iRIP or CAP). []
That's what my expectation would be."

The key thing I'm trying to push is that we should make the protocol simple
and provide flexibility for the server implementation.  If we say that CAP
has to provide (subject to authorization) the busy times of dmadeo when
asked to, then by hiding the details of whether that's many calendars or
one, we've simplified the protocol without limiting the implementors. I am
worried though that I'm missing something that will bite us.

A counter argument to the previous statement is that any opaqueness does
not need to be derived from the calendar hierarchy. Instead it can be
achieved using VCARs on individual events. However, applying default VCARs
to an entire hierarchical may result in fewer operational mistakes within
an organization. Please note that this is not a minor point. For many
customers this is a major issue.

Another user appears to use multiple calendars to help keep track of
overlapping appointments - knowing that he will not attend 'this one' this
week. I his case he does not want "rollup" to be a mandatory feature. A
counter argument to the previous statement is that VEVENTs within a
calendar may overlap and the user should simply modify the attendance on
the event that will be skipped during a particular week. Should we extend
iCalendar to include a property for "allow conflicts"?

Others have talked about using hierarchical calendars to model aspect of an
organization. For example a large company may have many building with
meetings rooms scattered around their facilities. The customer could then
create hierarchy where each building is a parent and meeting rooms within
the building are children of the calendar that represent the building. At
first glance, other than knowing which building a given resource is in,
this doesn't get you much. But, if we apply calendar properties and manage
inheritance within the hierarchy this might be very useful to many
customers. Counter to this idea the working group has had an extended
discussion about delimiter characters within a CalID, because people do not
want the CalID to expose any information about the hierarchy that the
customer site has created, especially when the CalIDs map to user's calendars.

Perhaps the strongest argument that I have heard for hierarchical calendars
is from vendors that have a very different view of how calendar data should
be maintained. In at least one case a vendor has a model where users
subscribe to calendars and the calendar contains events which may be of
interest to the subscriber. In this case the vendor is not really using
hierarchical calendars but is instead creating a web or net of calendars.
In many cases I am seeing vendors with more traditional models, that
evolved from the PIM world, migrating to this subscription concept for at
least some tasks, such as informing users of holidays. Even though I'm on a
NY server, I want London holidays.  Even though I sit in a NY office,
because I work overnight, holidays don't mean anything to me.  The only way
to do holidays and other inherited dates right is through subscriptions.

Some last minute thoughts:

I'm starting to wonder if "sub calendar" is the right notion we should be
selling.  Perhaps a flat namespace with both "default" and "nondefault"
calendars.    A default calendar is associated with a particular "entity:
person or thing".  It contains events as well as instructions for how to
attach nondefault calendars.  The choices are "informational:
[all,vevents,vtodo,vjournal]", "blocking: [all,vevents,vtodo,vjournal]".  A
nondefault calendar is not associated with an entity.

So,cap://cal.ms.com/dmadeo would contain the following
Info:vjournal   cap://cal.ms.com/ 848c8f7  (Firm Holidays)
Block:all          cap://cal.ms.com/8484783  (NY Holidays)
Block:all          cap://cal.ms.com/8334743  (Personal Items)
Block:all          cap://cal.ms.com/3848483  (Work Items)
Info:all             cap://cal.ms.com/3389393  (My organizational group)
Info:all             cap://cal.ms.com/9433433  (Brown Bag lunch schedule)

That gives everything a CS would need to determine what my schedule looks
like.  The only addition is that (and unfortunately this isn't in
iCalendar) for any given meeting, I might need to say "block this brown bag
lunch, I'll be there".


I hope that early next week I'll post a short, concise, write up on the
terms: user, username, principal, and authentication-id.

BTW, I know that Steve is wary of the issues that I have raised. At one
point during our email discussions he replied, "I have been working with a
lot of ISPs, Portals, and enterprise customers. They all have very
different ways of managing user information."  I hope that after my next
posting he'll be able to elaborate on this point.

Paul


From owner-ietf-calendar@imc.org  Fri Apr  9 17:58:33 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07846
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 17:58:32 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id OAA02580
	for ietf-calendar-bks; Fri, 9 Apr 1999 14:27:25 -0700 (PDT)
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id OAA02576
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 14:27:23 -0700 (PDT)
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
	id AA22151; Fri, 9 Apr 99 17:27:21 EDT
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
	by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id RAA21517
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 17:27:24 -0400 (EDT)
Received: from mona-lisa (MONA-LISA.MIT.EDU [18.172.1.179])
	by melbourne-city-street.MIT.EDU (8.9.2/8.9.2) with SMTP id RAA15816
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 17:27:23 -0400 (EDT)
Message-Id: <3.0.2.32.19990409172809.03b91610@po10.mit.edu>
X-Sender: pbh@po10.mit.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)
Date: Fri, 09 Apr 1999 17:28:09 -0400
To: ietf-calendar@imc.org
From: "Paul B. Hill" <pbh@mit.edu>
Subject: long comments also available via http...
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

Hi,

My posting 'problems with CAP not having "users" and hierarchical
calendars' is also available as a word document at 
<http://web.mit.edu/cal/ietf-wg/cap-users.doc>

Paul


From owner-ietf-calendar@imc.org  Fri Apr  9 19:18:55 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08341
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 19:18:54 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id PAA03429
	for ietf-calendar-bks; Fri, 9 Apr 1999 15:48:18 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id PAA03425
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 15:48:18 -0700 (PDT)
Received: by dfssl with Internet Mail Service (5.5.2580.0)
	id <2TW6KQJH>; Fri, 9 Apr 1999 15:47:41 -0700
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B0246D814@HYDRANT>
From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
To: "'Doug Royer'" <Doug.Royer@Sun.COM>, ietf-calendar@imc.org
Subject: RE: CAP Example READ-1
Date: Fri, 9 Apr 1999 15:47:44 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

response below >>>

> -----Original Message-----
> From: Doug Royer [mailto:Doug.Royer@Sun.COM]
> 
> > From: "Lisa Lippert (Dusseault) (Exchange)" 
> <lisal@exchange.microsoft.com>
> > Date: Thu, 8 Apr 1999 14:22:32 -0700 
> > 
> > SQL Cursors are cool and work well, but this would require 
> a lot of state to
> > be maintained on the server.  (Database servers are meant 
> to do that, but we
> > haven't really discussed whether that style of interaction 
> is intended for
> > CAP servers).  How many different calendar clients are 
> going to have views
> > into how many different calendars on one server?  
> 
> If it were done with a non-cursor method - it seems to me the same
> state information would need to be maintained for the same number of
> calendars on one server as with the cursor method?

Not really.  If the client maintains state for its user (which it should
anyway), then the client can pass the state to the server with a new
request, and the server doesn't have to maintain state for that user.

Lisa


From owner-ietf-calendar@imc.org  Fri Apr  9 19:20:23 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08360
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 19:20:23 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id PAA03375
	for ietf-calendar-bks; Fri, 9 Apr 1999 15:44:39 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id PAA03371
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 15:44:38 -0700 (PDT)
Received: by dfssl with Internet Mail Service (5.5.2580.0)
	id <2TW6KQ2M>; Fri, 9 Apr 1999 15:44:01 -0700
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B0246D813@HYDRANT>
From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@Exchange.Microsoft.com>
To: "'John Stracke'" <francis@ecal.com>, ietf-calendar@imc.org
Subject: RE: Delimiter characters in relativeCalUID
Date: Fri, 9 Apr 1999 15:44:04 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

Or, even, the server implementor could allow hierarchy in URLs, and just
know that in the flat database any name with '/' in it could still be
treated like an opaque string.

Having calendar "foo" and calendar "foo/bar" and making "foo" the parent of
"bar" (and "bar" the child of "foo") still does not impose storage
restrictions on the implementation.  

We're designing how implementations *appear*, not how they *work*.  

Lisa

> -----Original Message-----
> From: John Stracke [mailto:francis@ecal.com]
> Sent: Thursday, April 01, 1999 1:12 PM
> To: ietf-calendar@imc.org
> Subject: Re: Delimiter characters in relativeCalUID
> 
> 
> John Sun wrote:
> 
> > Here are some problems using a '/' to represent calendar hierarchy:
> >
> > 1) Force the server designer to use a specific calendar hierarchy.
> 
> No, it doesn't.  If you don't want a heirarchy, you just make sure you
> don't have any '/'s in your calendar IDs.
> 
> > 2) Exposes the calendar hierarchy to clients.
> 
> Aliases.
> 
> Again, I am not saying we should *use* the '/' in CAP1; I just want to
> reserve it (or some other character) for use in a hypothetical future
> version.  Otherwise, CAP1's calendar IDs will gobble up the entire
> namespace, and there won't be any safe way to build a string that
> delimits them.
> 
> --
> /=============================================================\
> |John Stracke    | My opinions are my own | S/MIME & HTML OK  |
> |francis@ecal.com|============================================|
> |Chief Scientist | NT's lack of reliability is only surpassed |
> |eCal Corp.      |  by its lack of scalability. -- John Kirch |
> \=============================================================/
> 
> 


From owner-ietf-calendar@imc.org  Fri Apr  9 19:52:28 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08514
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 19:52:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id QAA03837
	for ietf-calendar-bks; Fri, 9 Apr 1999 16:30:31 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id QAA03832
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 16:30:30 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA23188
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 16:30:32 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id QAA11411
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 16:30:29 -0700 (PDT)
Message-Id: <199904092330.QAA11411@engmail2.Eng.Sun.COM>
Date: Fri, 9 Apr 1999 16:30:30 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: RE: CAP Example READ-1
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 4cvD+iy1ZbU2Sswsngsf1g==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> From: "Lisa Lippert (Dusseault) (Exchange)" <lisal@exchange.microsoft.com>
> Date: Fri, 9 Apr 1999 15:47:44 -0700 
> 
> response below >>>
> 
> > -----Original Message-----
> > From: Doug Royer [mailto:Doug.Royer@Sun.COM]
> > 
> > > From: "Lisa Lippert (Dusseault) (Exchange)" 
> > <lisal@exchange.microsoft.com>
> > > Date: Thu, 8 Apr 1999 14:22:32 -0700 
> > > 
> > > SQL Cursors are cool and work well, but this would require 
> > > a lot of state to be maintained on the server.  (Database servers
> > > are meant to do that, but we haven't really discussed whether that
> > > style of interaction is intended for CAP servers).  How many different
> > > calendar clients are  going to have views into how many different
> > > calendars on one server?  
> > 
> > If it were done with a non-cursor method - it seems to me the same
> > state information would need to be maintained for the same number of
> > calendars on one server as with the cursor method?
> 
> Not really.  If the client maintains state for its user (which it should
> anyway), then the client can pass the state to the server with a new
> request, and the server doesn't have to maintain state for that user.

Sure it does.  We have a state-full protocol. That means
we keep session state including user information until that
user is done (by whatever method).

The query would have to be maintained until the state or query
was over. If not you could get the same results twice (or more) if
you did not keep query results.

	This could happen with the MIN-MAX method if the CS
	did not keep state information:
	
	At time T1 you query the CS for all VEVENTS today and ask
	for items 1-20 sorted by TRIGGER time. And say you get
	back 20 items all happened to between 9AM and 3PM.
	
	AT time T2 20 new VEVENTS are added, all of them
	with TRIGGER times between 1AM and 8AM.
	
	At time T3, you ask for items 21-30. If the CS did not keep
	the query results (state)- you get back the same 20 
	that was from your original (T1) query.

Thin clients would tend to only ask for one at a time anyway correct?

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Fri Apr  9 21:53:51 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09134
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 21:53:50 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id SAA05195
	for ietf-calendar-bks; Fri, 9 Apr 1999 18:22:38 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id SAA05191
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 18:22:36 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA15290
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 18:22:39 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id SAA26750;
	Fri, 9 Apr 1999 18:22:36 -0700 (PDT)
Message-Id: <199904100122.SAA26750@engmail2.Eng.Sun.COM>
Date: Fri, 9 Apr 1999 18:22:37 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: problems with CAP not having "users" and hierarchical calendars
To: ietf-calendar@imc.org
Cc: =?US-ASCII?Q?=10=10?=@Sun.COM
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=US-ASCII
Content-MD5: dhM/RPonM4xXV4dk7uD0Qw==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mail.proper.com id SAA05192
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit


> Date: Fri, 09 Apr 1999 16:46:03 -0400
> From: "Paul B. Hill" <pbh@mit.edu>

> ...
> 
> Before we go too much further, let's stop and think about how a person
> would interact with a single server system that implements hierarchical
> calendars with opaque CalIDs. 
> ...
> ...
> How do I, Paul, tell our example server that I would like to examine Bob's
> calendar to see if he has a scheduled appointment for 2:00pm on Wednesday,
> April 7th, 1999?
> 
> At first glance I was tempted to say that I'd have to learn the mapping
> between Bob-the-user and Bob's CalID. I might get this from a
> directory.... 
> 
> As soon as we say we have hierarchical calendars I don't think that these
> mechanisms are an adequate solution, if they ever were. The locating draft
> introduces the concept of a default calendar for a user and mentions that
> the default calendar may include rolled-up information from all the user's
> other calendars. No working group document talks about "roll-up", whether
> or not it is mandatory or optional, or how a user would control the roll-up.

I see roll-up as an implementation option. 
Some may not need it or can not use it, others may want or need it.

I could want no roll-up at all in a sub-calendar:

	I am maintaining a calendar for my groups football pool and it
	contains all of the NFL schedule and my implementation
	or administrator does not allow me to create root calendars.

I could want roll-up for named components only:

	I will only be attending the 49rs games that are local.
	And then maybe only some of them.

Or I might want roll-up in a vendor specific way:

	The root calendar is a pool of company cars
	and the sub-calendars are calendars for each
	physical car. The only time the root calendar is
	'busy' is when all cars in that time slice are booked
	in all of those sub-calendars.
	
	I also might have NO acceess to read any of those sub-calendars.
	
	(I know that resource groups and resource pools are not in
	CAP-1, but no need to break it for CAP-2).

In some cases the CS will not allow the CUA to change the
roll-up rules as they are part of the vertical application
in the CS.

> Should there be a CAP operation that can be used to determine which
> calendars I own?

Yes - ask for all calendars where the OWNER property contains
your authenticated id.

> It's probably too much to ask which calendars I have
> access to. (What does ownership or access mean in this context?)

OWNER-ship is a calendar tag (property) invented by the VCAR work
to help identify a set of users that will often have special rights.
(grant 'all' access to everyone that is tagged as an 'owner').

OWNER currently has no other meaning.

>  ...
>
> Let's take another example. Again we have a single server but we have
> either Relative CalIDs that appear legible to many users, or maybe I am
> actually showing  Calendar Names instead of CalIDs. For now let's just
> pretend that this distinction is not important.
> 
> ... (examples deleted)...
>
> Now George just wants to determine when Alice is available for a meeting.
> Does George have to discover the entire calendar hierarchy and then query
> each calendar to determine if Alice has an appointment in it? Obviously
> this would be very inefficient.

So is BUSY time a query to the CS or query to a calendar on a CS?

If it were a CS query - then how would I ask for a specific calendar only?

What if I want the calendar BUSY time, and not a authenticated id busy time?
(Is this room available - I do not care who else has it at other times).

Perhaps:

	If I provide only the CSID and a username, I would
	be asking for any BUSY time for the username
	for any calendar on the CS.
	
	If I provide a RELCALID and a username, I would be
	asking for any BUSY time for the username and only
	for that calendar.

	If I provide a RELCALID and NO username, I would be
	asking for any BUSY time on the calendar.

	I don't think that asking for BUSY time for all users
	on a CS	has any use.
		
> Let's suppose that I work for a company that does not want me to store
> personal data on the company's computer resources. ...
> ...
> So, why do we have hierarchical calendars?

I did not see that your example eliminated hierarchical calendars.
If my employer did not allow personal information, it does not
mean that I could not have hierarchical calendars containing
work related components. (Work Breakdown Structure - WBS)
		
> It appears that at least one potential customer is "interested in multiple
> calendars with varying degrees of opaqueness from a free/BUSY point of
> view."  "This fits into how we work, where I have different projects that
> I share with others. There's also calendars that I want to inherit from the
> firm (such as interesting business dates, unusual holidays, etc)."
> ...
> The key thing I'm trying to push is that we should make the protocol simple
> and provide flexibility for the server implementation.  If we say that CAP
> has to provide (subject to authorization) the busy times of dmadeo when
> asked to, then by hiding the details of whether that's many calendars or
> one, we've simplified the protocol without limiting the implementors.

Agreed.

> A counter argument to the previous statement is that any opaqueness does
> not need to be derived from the calendar hierarchy. Instead it can be
> achieved using VCARs on individual events. However, applying default VCARs
> to an entire hierarchical may result in fewer operational mistakes within
> an organization. Please note that this is not a minor point. For many
> customers this is a major issue.

I could see that you could have access to my BUSY time, and not
have a VCAR to access my DTSTART, DTEND, or DURATION. (If that
is what you are saying).

If I ask for all OPAQUE components and the DTSTART, DTEND, or DURATION,
I now might have a count of components. 

With BUSY time, I just know a time slice is opaque.

> Another user appears to use multiple calendars to help keep track of
> overlapping appointments - knowing that he will not attend 'this one' this
> week. I his case he does not want "rollup" to be a mandatory feature. A
> counter argument to the previous statement is that VEVENTs within a
> calendar may overlap and the user should simply modify the attendance on
> the event that will be skipped during a particular week. Should we extend
> iCalendar to include a property for "allow conflicts"?

Yes - I think by default conflicts should be allowed.
And I think that each component or calendar should be allowed
to be marked 'no conflicts' and enforced by the CS.

Another issue with appointments is, as Frank pointed out:

	That meeting is 15 minutes away, so I am also busy
	15 minutes before and 15 minutes after that appointment.

In which case the CUA better not tweak with the component. The time
block would have to be local to the users calendar and not pushed
back to the ORGANIZER as an update to the component. And it may or
might not be visible as a component in a query, yet be OPAQUE
and show up as BUSY.

Also another reason for hierarchical calendars:
	
	An ISP does not allow users to create root calendars.
	They can do whatever they want - under their calendar.
	
> Some last minute thoughts:
> 
> I'm starting to wonder if "sub calendar" is the right notion we should be
> selling.  Perhaps a flat namespace with both "default" and "nondefault"
> calendars.    A default calendar is associated with a particular "entity:
> person or thing".  It contains events as well as instructions for how to
> attach nondefault calendars.  The choices are "informational:
> [all,vevents,vtodo,vjournal]", "blocking: [all,vevents,vtodo,vjournal]".  A
> nondefault calendar is not associated with an entity.
> ...

So a 'linked' calendar that does roll-up?

> That gives everything a CS would need to determine what my schedule looks 
> like.  ...

Your schedule - yes.

You would loose the ability to allow users that can not create root
level calendars to have other non-rolled-up calendars.

I see hierarchical calendars and roll-up as separate.
And I see that roll-up as a calendar option listing the CALIDs
of any calendar - sub-calendar or not.

I could live with roll-up not in CAP-1.

> BTW, I know that Steve is wary of the issues that I have raised. At one
> point during our email discussions he replied, "I have been working with a
> lot of ISPs, Portals, and enterprise customers. They all have very
> different ways of managing user information."  I hope that after my next
> posting he'll be able to elaborate on this point.

THANK YOU VERY MUCH FOR THIS WORK!!!!

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Fri Apr  9 21:57:25 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09166
	for <calsch-archive@odin.ietf.org>; Fri, 9 Apr 1999 21:57:24 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id SAA05211
	for ietf-calendar-bks; Fri, 9 Apr 1999 18:24:10 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id SAA05207
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 18:24:09 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA15481
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 18:24:12 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id SAA26878
	for <ietf-calendar@imc.org>; Fri, 9 Apr 1999 18:24:09 -0700 (PDT)
Message-Id: <199904100124.SAA26878@engmail2.Eng.Sun.COM>
Date: Fri, 9 Apr 1999 18:24:10 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: problems with CAP not having "users" and hierarchical calendars
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=US-ASCII
Content-MD5: TCmR4wdGx9/b6PA0ZdjqqQ==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by mail.proper.com id SAA05208
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

> Date: Fri, 09 Apr 1999 16:46:03 -0400
> From: "Paul B. Hill" <pbh@mit.edu>

> ...
> 
> Before we go too much further, let's stop and think about how a person
> would interact with a single server system that implements hierarchical
> calendars with opaque CalIDs. 
> ...
> ...
> How do I, Paul, tell our example server that I would like to examine Bob's
> calendar to see if he has a scheduled appointment for 2:00pm on Wednesday,
> April 7th, 1999?
> 
> At first glance I was tempted to say that I'd have to learn the mapping
> between Bob-the-user and Bob's CalID. I might get this from a
> directory.... 
> 
> As soon as we say we have hierarchical calendars I don't think that these
> mechanisms are an adequate solution, if they ever were. The locating draft
> introduces the concept of a default calendar for a user and mentions that
> the default calendar may include rolled-up information from all the user's
> other calendars. No working group document talks about "roll-up", whether
> or not it is mandatory or optional, or how a user would control the roll-up.

I see roll-up as an implementation option. 
Some may not need it or can not use it, others may want or need it.

I could want no roll-up at all in a sub-calendar:

	I am maintaining a calendar for my groups football pool and it
	contains all of the NFL schedule and my implementation
	or administrator does not allow me to create root calendars.

I could want roll-up for named components only:

	I will only be attending the 49rs games that are local.
	And then maybe only some of them.

Or I might want roll-up in a vendor specific way:

	The root calendar is a pool of company cars
	and the sub-calendars are calendars for each
	physical car. The only time the root calendar is
	'busy' is when all cars in that time slice are booked
	in all of those sub-calendars.
	
	I also might have NO acceess to read any of those sub-calendars.
	
	(I know that resource groups and resource pools are not in
	CAP-1, but no need to break it for CAP-2).

In some cases the CS will not allow the CUA to change the
roll-up rules as they are part of the vertical application
in the CS.

> Should there be a CAP operation that can be used to determine which
> calendars I own?

Yes - ask for all calendars where the OWNER property contains
your authenticated id.

> It's probably too much to ask which calendars I have
> access to. (What does ownership or access mean in this context?)

OWNER-ship is a calendar tag (property) invented by the VCAR work
to help identify a set of users that will often have special rights.
(grant 'all' access to everyone that is tagged as an 'owner').

OWNER currently has no other meaning.

>  ...
>
> Let's take another example. Again we have a single server but we have
> either Relative CalIDs that appear legible to many users, or maybe I am
> actually showing  Calendar Names instead of CalIDs. For now let's just
> pretend that this distinction is not important.
> 
> ... (examples deleted)...
>
> Now George just wants to determine when Alice is available for a meeting.
> Does George have to discover the entire calendar hierarchy and then query
> each calendar to determine if Alice has an appointment in it? Obviously
> this would be very inefficient.

So is BUSY time a query to the CS or query to a calendar on a CS?

If it were a CS query - then how would I ask for a specific calendar only?

What if I want the calendar BUSY time, and not a authenticated id busy time?
(Is this room available - I do not care who else has it at other times).

Perhaps:

	If I provide only the CSID and a username, I would
	be asking for any BUSY time for the username
	for any calendar on the CS.
	
	If I provide a RELCALID and a username, I would be
	asking for any BUSY time for the username and only
	for that calendar.

	If I provide a RELCALID and NO username, I would be
	asking for any BUSY time on the calendar.

	I don't think that asking for BUSY time for all users
	on a CS	has any use.
		
> Let's suppose that I work for a company that does not want me to store
> personal data on the company's computer resources. ...
> ...
> So, why do we have hierarchical calendars?

I did not see that your example eliminated hierarchical calendars.
If my employer did not allow personal information, it does not
mean that I could not have hierarchical calendars containing
work related components. (Work Breakdown Structure - WBS)
		
> It appears that at least one potential customer is "interested in multiple
> calendars with varying degrees of opaqueness from a free/BUSY point of
> view."  "This fits into how we work, where I have different projects that
> I share with others. There's also calendars that I want to inherit from the
> firm (such as interesting business dates, unusual holidays, etc)."
> ...
> The key thing I'm trying to push is that we should make the protocol simple
> and provide flexibility for the server implementation.  If we say that CAP
> has to provide (subject to authorization) the busy times of dmadeo when
> asked to, then by hiding the details of whether that's many calendars or
> one, we've simplified the protocol without limiting the implementors.

Agreed.

> A counter argument to the previous statement is that any opaqueness does
> not need to be derived from the calendar hierarchy. Instead it can be
> achieved using VCARs on individual events. However, applying default VCARs
> to an entire hierarchical may result in fewer operational mistakes within
> an organization. Please note that this is not a minor point. For many
> customers this is a major issue.

I could see that you could have access to my BUSY time, and not
have a VCAR to access my DTSTART, DTEND, or DURATION. (If that
is what you are saying).

If I ask for all OPAQUE components and the DTSTART, DTEND, or DURATION,
I now might have a count of components. 

With BUSY time, I just know a time slice is opaque.

> Another user appears to use multiple calendars to help keep track of
> overlapping appointments - knowing that he will not attend 'this one' this
> week. I his case he does not want "rollup" to be a mandatory feature. A
> counter argument to the previous statement is that VEVENTs within a
> calendar may overlap and the user should simply modify the attendance on
> the event that will be skipped during a particular week. Should we extend
> iCalendar to include a property for "allow conflicts"?

Yes - I think by default conflicts should be allowed.
And I think that each component or calendar should be allowed
to be marked 'no conflicts' and enforced by the CS.

Another issue with appointments is, as Frank pointed out:

	That meeting is 15 minutes away, so I am also busy
	15 minutes before and 15 minutes after that appointment.

In which case the CUA better not tweak with the component. The time
block would have to be local to the users calendar and not pushed
back to the ORGANIZER as an update to the component. And it may or
might not be visible as a component in a query, yet be OPAQUE
and show up as BUSY.

Also another reason for hierarchical calendars:
	
	An ISP does not allow users to create root calendars.
	They can do whatever they want - under their calendar.
	
> Some last minute thoughts:
> 
> I'm starting to wonder if "sub calendar" is the right notion we should be
> selling.  Perhaps a flat namespace with both "default" and "nondefault"
> calendars.    A default calendar is associated with a particular "entity:
> person or thing".  It contains events as well as instructions for how to
> attach nondefault calendars.  The choices are "informational:
> [all,vevents,vtodo,vjournal]", "blocking: [all,vevents,vtodo,vjournal]".  A
> nondefault calendar is not associated with an entity.
> ...

So a 'linked' calendar that does roll-up?

> That gives everything a CS would need to determine what my schedule looks 
> like.  ...

Your schedule - yes.

You would loose the ability to allow users that can not create root
level calendars to have other non-rolled-up calendars.

I see hierarchical calendars and roll-up as separate.
And I see that roll-up as a calendar option listing the CALIDs
of any calendar - sub-calendar or not.

I could live with roll-up not in CAP-1.

> BTW, I know that Steve is wary of the issues that I have raised. At one
> point during our email discussions he replied, "I have been working with a
> lot of ISPs, Portals, and enterprise customers. They all have very
> different ways of managing user information."  I hope that after my next
> posting he'll be able to elaborate on this point.

THANK YOU VERY MUCH FOR THIS WORK!!!!

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Sat Apr 10 13:38:50 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22134
	for <calsch-archive@odin.ietf.org>; Sat, 10 Apr 1999 13:38:49 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id KAA12517
	for ietf-calendar-bks; Sat, 10 Apr 1999 10:08:39 -0700 (PDT)
Received: from electra.cc.umanitoba.ca (root@electra.cc.umanitoba.ca [130.179.16.23])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id KAA12513
	for <ietf-calendar@imc.org>; Sat, 10 Apr 1999 10:08:38 -0700 (PDT)
Received: from [130.179.154.50]
	(annex7-01.cc.umanitoba.ca [130.179.154.50]) by
	electra.cc.umanitoba.ca (8.9.0/8.9.0) with ESMTP id MAA16763
	for <ietf-calendar@imc.org>; Sat, 10 Apr 1999 12:08:39 -0500 (CDT)
Message-Id: <199904101708.MAA16763@electra.cc.umanitoba.ca>
X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410)
Date: Sat, 10 Apr 1999 11:50:21 -0500
Subject: Re: CUA capabilities
From: "Graham Davison" <g.m.davison@computer.org>
To: CalSch mailing list <ietf-calendar@imc.org>
Mime-version: 1.0
X-Priority: 3
Content-type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.proper.com id KAA12514
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit

>From: Doug Royer <Doug.Royer@Sun.COM>
>To: ietf-calendar@imc.org
>Subject: Re: CUA capabilities
>Date: Fri, 9 Apr 1999 13:20
>

>
>> Date: Fri, 09 Apr 1999 16:03:30 +0000
>> From: John Stracke <francis@ecal.com>
>>
>> David Madeo wrote:
>>
>> > > I'm now trying to argue that a CUA might need to be able to specify what
>> > > languages its user understands, so that a CS can pick out an appropriate
>> > > translation of the iCalendar object.
>> >
>> > Maybe I'm missing something here.  If I type "meeting with George"
>> > or"rencontrant George" or "George treffen" or even "ÆüËÜ¸ì George",
>> > then that's what I'd expect to be stored on the CS and that I'd get
>> > back in the CUA.
>>
>> OK, so what do you do if you've got an event announcement (say, a
>> soccer match) where you'll have people attending who speak many
>> different languages? You want each user to see the announcement in
>> their own language, which means the CS needs to be able to
>> present multiple versions and  CUA and the CS need to do content
>> negotiation.  The CS doesn't need to do the translation itself (though
>> that may be an option eventually); it would suffice for there to exist
>> some (possibly proprietary) mechanism whereby the alternative renditions
>> can be provided for it to store.
>
> It would be nice. In order for that to happen we have
> to extend something - iTIP and iCal. As there is no way to transmit
> that message via iMIP. Because only one DESCRIPTION is allowed in
> a VEVENT. And a VEVENT is unique per UID. There can not be different
> VEVENTS with the same UID, some with DESCRIPTION;param-set-1
> and others with DESCRIPTION;param-set-2.
>
> At some point it would not be possible to tell which was the
> correct version.
>
> If a user in lang-1 were to send back a correction to the CS
> would the CS know how to translate that back into the other supported
> languages? Or would the user not be allowed to update a DESCRIPTION
> unless they knew every language the CS might have stored the VEVENT in?
> Or would it be allowed that the DESCRIPTION for one language did not
> evaluate to the same thing in another language?
>
> I can see how a vertical application CS might want to do this.
> I can not see how a general purpose CS could ever do this.

Perhaps the best thing to do would be to allow more than one description per
VEVENT, as long as the languages were different. This would, of course,
require changing iCal. If a user were to update the VEVENT without changing
all languages, the unchanged languages should "disappear" from the VEVENT.

Having multiple languages is important in some countries. As someone
mentioned previously, a facility such as Ontario Place should have English
and French. In fact, most public facilities in Canada should have both and
government calendars would probably require it by law. This would also
benefit other countries with multiple official languages or where large
portions of the population speak different languages. And then there are
tourist locations where foreign tourists would be visiting...

Regards,
Graham Davison

--

----------------------------------------------------------------------------
Graham Davison           | We shall not cease from exploration, and the end
g.m.davison@computer.org | of all our exploring will be to arrive where we
Computer Eng, MSc student| started and know the place for the first time.
University of Manitoba   |                                     -T. S. Eliot
----------------------------------------------------------------------------



From owner-ietf-calendar@imc.org  Sat Apr 10 22:39:13 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26104
	for <calsch-archive@odin.ietf.org>; Sat, 10 Apr 1999 22:39:13 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id TAA15854
	for ietf-calendar-bks; Sat, 10 Apr 1999 19:09:08 -0700 (PDT)
Received: from snipe.prod.itd.earthlink.net (snipe.prod.itd.earthlink.net [207.217.120.62])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id TAA15850
	for <ietf-calendar@imc.org>; Sat, 10 Apr 1999 19:09:07 -0700 (PDT)
Received: from fdawson (1Cust7.tnt2.garden-city.ny.da.uu.net [208.250.136.7])
	by snipe.prod.itd.earthlink.net (8.8.7/8.8.5) with SMTP id TAA22947
	for <ietf-calendar@imc.org>; Sat, 10 Apr 1999 19:09:10 -0700 (PDT)
Message-ID: <001c01be83c0$20096a40$e937fea9@fdawson.lotus.com>
From: "Frank Dawson" <fdawson@earthlink.net>
To: "CalSch mailing list" <ietf-calendar@imc.org>
Subject: Re: CUA capabilities
Date: Sat, 10 Apr 1999 22:07:58 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Folks:

The RFC 2445 has a ALTREP parameter on any TEXT valued property. This
parameter is used to specify "alternate representation" of the property
value. You can use this to specify other forms for properties such as
DESCRIPTION and SUMMARY. We should be using this for specifying multiple
instances of the DESCRIPTION, SUMMARY, etc.

- - Frank



From owner-ietf-calendar@imc.org  Sun Apr 11 22:14:06 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10842
	for <calsch-archive@odin.ietf.org>; Sun, 11 Apr 1999 22:14:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id SAA25826
	for ietf-calendar-bks; Sun, 11 Apr 1999 18:38:39 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id SAA25822
	for <ietf-calendar@imc.org>; Sun, 11 Apr 1999 18:38:38 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA02935
	for <ietf-calendar@imc.org>; Sun, 11 Apr 1999 18:38:47 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id SAA01485
	for <ietf-calendar@imc.org>; Sun, 11 Apr 1999 18:38:44 -0700 (PDT)
Message-Id: <199904120138.SAA01485@engmail2.Eng.Sun.COM>
Date: Sun, 11 Apr 1999 18:38:45 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: CUA capabilities
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: naVTxqtWYF2085h4uD+kQQ==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> From: "Frank Dawson" <fdawson@earthlink.net>
> To: "CalSch mailing list" <ietf-calendar@imc.org>
> 
> Folks:
> 
> The RFC 2445 has a ALTREP parameter on any TEXT valued property. This
> parameter is used to specify "alternate representation" of the property
> value. You can use this to specify other forms for properties such as
> DESCRIPTION and SUMMARY. We should be using this for specifying multiple
> instances of the DESCRIPTION, SUMMARY, etc.

ALTREP can be used for anything. No interoperatability if
one implementation expects them to be LANG, and another 
expects HTML.

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Sun Apr 11 23:34:39 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13253
	for <calsch-archive@odin.ietf.org>; Sun, 11 Apr 1999 23:34:39 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id TAA03602
	for ietf-calendar-bks; Sun, 11 Apr 1999 19:50:17 -0700 (PDT)
Received: from komarr.local.thibault.org (adsl-151-197-16-76.bellatlantic.net [151.197.16.76])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id TAA03593
	for <ietf-calendar@imc.org>; Sun, 11 Apr 1999 19:50:15 -0700 (PDT)
Received: from ariel.local.thibault.org (ariel.local.thibault.org [192.168.10.18])
	by komarr.local.thibault.org (8.8.7/8.8.7) with ESMTP id WAA17329
	for <ietf-calendar@imc.org>; Sun, 11 Apr 1999 22:49:48 -0400
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.local.thibault.org (8.8.7/8.8.7) with ESMTP id WAA11971
	for <ietf-calendar@imc.org>; Sun, 11 Apr 1999 22:52:24 -0400
Message-ID: <37115FE8.85E3A119@ecal.com>
Date: Mon, 12 Apr 1999 02:52:24 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: CUA capabilities
References: <199904120138.SAA01485@engmail2.Eng.Sun.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Doug Royer wrote:

> ALTREP can be used for anything. No interoperatability if
> one implementation expects them to be LANG, and another
> expects HTML.

I think that could be made to work, actually.  ALTREP specifies a URI; if
it's an HTTP URL, then, when the CUA dereferences it, the server can do
content negotiation to (try to) provide the right language  While it's true
that ALTREP can be used for anything, I think all the reasonable uses for it
can be lumped into "find a better representation of this string"--where
"better" can mean "in a more pleasant format" or "in a language you can read"
or even "longer" (e.g., if the originator wrote a 10-page description, it may
be desirable to send only a summary to all the attendees).

I would like to see a way of delivering alternate languages inline, but
ALTREP will suffice.  (We may run into some use cases where it'll be seen as
discriminatory--e.g., when somebody in Canada publishes their events in
English with an ALTREP to get French if needed, and the French speakers
object to having to wait longer than the English speakers--but the answer to
that is to have the inline string contain both languages, and the ALTREP
present one or the other.)

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Mon Apr 12 02:23:57 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20999
	for <calsch-archive@odin.ietf.org>; Mon, 12 Apr 1999 02:23:57 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id WAA10675
	for ietf-calendar-bks; Sun, 11 Apr 1999 22:52:18 -0700 (PDT)
Received: from server1234 (ts005d29.phe-pa.concentric.net [209.31.154.233])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id WAA10666
	for <ietf-calendar@imc.org>; Sun, 11 Apr 1999 22:52:15 -0700 (PDT)
From: kuppler@toast.net
Message-Id: <199904120552.WAA10666@mail.proper.com>
To: <ietf-calendar@imc.org>
Subject: AD:Family Reunion T Shirts & More
Date: Mon, 13 Apr 1998 01:46:29
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

Message sent by:  Kuppler Graphics, 32 West Main Street, Maple Shade, New Jersey, 08052,
1-800-810-4330.   This list will NOT be sold.  All addresses 
are automatically added to our remove list.

Hello.  My name is Bill from Kuppler Graphics.  We do screenprinting on T Shirts, Sweatshirts,
Jackets, Hats, Tote Bags and more!

Do you or someone you know have a Family Reunion coming up?  Kuppler Graphics would like to
provide you with some great looking T Shirts for your Reunion.

Kuppler Graphics can also provide you with custom T's and promotional items such as imprinted
magnets, keychains, pens, mugs, hats, etc. for your business or any fundraising activity
(church, school, business etc.) We also can provide you with quality embroidery. 

We are a family owned company with over 15 years of experience.  

All work is done at this location.  No middle man.  Our prices are great!

Click reply to email us or call 1-800-810-4330 for more info


Bill
Kuppler Graphics
 
 
 
 
 
 
 
 
 
 
 
 
 


From owner-ietf-calendar@imc.org  Mon Apr 12 08:14:47 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23789
	for <calsch-archive@odin.ietf.org>; Mon, 12 Apr 1999 08:14:47 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id EAA15561
	for ietf-calendar-bks; Mon, 12 Apr 1999 04:42:06 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id EAA15557
	for <ietf-calendar@imc.org>; Mon, 12 Apr 1999 04:42:04 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22795;
	Mon, 12 Apr 1999 07:41:46 -0400 (EDT)
Message-Id: <199904121141.HAA22795@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-calendar@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-calsch-icalfpi-01.txt
Date: Mon, 12 Apr 1999 07:41:46 -0400
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts
directories.  This draft is a work item of the Calendaring and
Scheduling Working Group of the IETF.

	Title		: iCalendar v2.0 Formal Public Identifier
	Author(s)	: F. Dawson, P. Hoffman 
	Filename	: draft-ietf-calsch-icalfpi-01.txt
	Pages		: 4
	Date		: 11-Apr-99
	
The IETF has defined a standard format for exchanging calendaring and
scheduling data, called iCalendar. This format is useful for exchange
of personal calendar data across the Internet, as well as in non-
Internet environments.
 
In a number of environments where the iCalendar will be used, the
format type and version needs to be identified. For example, when
registering the iCalendar as a format for memory-based 'clipboard' or
'drag/drop' user interface interactions. For these cases, a
definitive formal public identifier (FPI) for the iCalendar will be
required. This memo defined the FPI to be used when referring to the
version 2.0 (the value in the 'VERSION' property) of the iCalendar
format.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-calsch-icalfpi-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-calsch-icalfpi-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-calsch-icalfpi-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990411145920.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsch-icalfpi-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-calsch-icalfpi-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990411145920.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-calendar@imc.org  Mon Apr 12 08:15:22 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23840
	for <calsch-archive@odin.ietf.org>; Mon, 12 Apr 1999 08:15:21 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id EAA15556
	for ietf-calendar-bks; Mon, 12 Apr 1999 04:42:00 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id EAA15552
	for <ietf-calendar@imc.org>; Mon, 12 Apr 1999 04:41:58 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22780;
	Mon, 12 Apr 1999 07:41:40 -0400 (EDT)
Message-Id: <199904121141.HAA22780@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-calendar@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-calsch-locating-02.txt
Date: Mon, 12 Apr 1999 07:41:40 -0400
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts
directories.  This draft is a work item of the Calendaring and
Scheduling Working Group of the IETF.

	Title		: Calendar attributes for vCard and LDAP
	Author(s)	:  T. Small, D. Hennessy, F. Dawson  Jr
	Filename	: draft-ietf-calsch-locating-02.txt
	Pages		: 17
	Date		: 11-Apr-99
	
When scheduling a calendar entity, such as an event, it is a
prerequisite that an organizer has the calendar address of each attendee
that will be invited to the event. Additionally, access to an attendee's
current 'busy time' provides an a priori indication of whether the
attendee will be free to participate in the event.
 
In order to meet these challenges, a calendar user agent (CUA) needs a
mechanism to locate (URI) individual user's calendar and free/busy time.
 
This draft defines three mechanisms for obtaining a URI to a user's
calendar and free/busy time. These include:
 
- Manual transfer of the information;

- Personal data exchange using the vCard format; and
 
- Directory lookup using the LDAP protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-calsch-locating-02.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-calsch-locating-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-calsch-locating-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990411145912.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsch-locating-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-calsch-locating-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990411145912.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-calendar@imc.org  Wed Apr 14 16:39:37 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04419
	for <calsch-archive@odin.ietf.org>; Wed, 14 Apr 1999 16:39:37 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA08825
	for ietf-calendar-bks; Wed, 14 Apr 1999 13:00:10 -0700 (PDT)
Received: from cdc.net (server1.cdc.net [207.244.0.12])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id NAA08821
	for <ietf-calendar@imc.org>; Wed, 14 Apr 1999 13:00:09 -0700 (PDT)
From: pregen@egenconsulting.com
Received: (qmail 13046 invoked from network); 14 Apr 1999 20:00:34 -0000
Received: from unknown (HELO egenconsulting.com) (207.244.42.65)
  by server1.cdc.net with SMTP; 14 Apr 1999 20:00:34 -0000
Received: by egenconsulting.com(Lotus SMTP MTA v4.6.2  (693.3 8-11-1998))  id 85256753.006DE63A ; Wed, 14 Apr 1999 16:00:23 -0400
X-Lotus-FromDomain: EGEN CONSULTING
To: ietf-calendar@imc.org
Message-ID: <85256753.006DE627.00@egenconsulting.com>
Date: Wed, 14 Apr 1999 16:00:22 -0400
Subject: Provide suggested text for drafts too
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

I've been watching all the dialogs going on with suggestions and comments
regarding items in the draft.  It would be also a good idea if when you
"complain" or "suggest" you might also send some suggested draft wording.
This helps the editors a lot and would be helpful to the rest of the list
to get an idea how a point should look.  Some people are already doing that
- I'd like to see more of it.  You all have great ideas - I bet you can
write well too. 8-)




From owner-ietf-calendar@imc.org  Sat Apr 17 01:48:16 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22412
	for <calsch-archive@odin.ietf.org>; Sat, 17 Apr 1999 01:48:16 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id WAA19265
	for ietf-calendar-bks; Fri, 16 Apr 1999 22:10:59 -0700 (PDT)
Received: from linux.home.mark (cr421685-a.slnt1.on.wave.home.com [24.112.208.155])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id WAA19261
	for <ietf-calendar@imc.org>; Fri, 16 Apr 1999 22:10:57 -0700 (PDT)
Received: from geocities.com (mark.home.mark [192.168.0.6])
	by linux.home.mark (8.9.2/8.8.7) with ESMTP id BAA12086
	for <ietf-calendar@imc.org>; Sat, 17 Apr 1999 01:11:34 -0400 (EDT)
Message-ID: <37181841.B9D5A068@geocities.com>
Date: Sat, 17 Apr 1999 01:12:33 -0400
From: Mark Swanson <swansma@geocities.com>
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: CalSch mailing list <ietf-calendar@imc.org>
Subject: Error in rfc2445
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello,

I've found an error in the spec that would cause people to develop
incompatible implementations. Check out 4.2.8 - Format Type. iana-token
and x-name are both inadequate to hold "application/binary" because of
the "/" character. MIME types are not possible here.

I don't know where to go from here so I'll leave it in the capable hands
of the people on this mailing list.

Cheers.

--
-----------------------------------------------
If DOS means "Denial Of Service" what's MS-DOS?
             And why should I tell it to "win"?




From owner-ietf-calendar@imc.org  Sun Apr 18 23:22:55 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07849
	for <calsch-archive@odin.ietf.org>; Sun, 18 Apr 1999 23:22:40 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id TAA13879
	for ietf-calendar-bks; Sun, 18 Apr 1999 19:45:51 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id TAA13870
	for <ietf-calendar@imc.org>; Sun, 18 Apr 1999 19:45:50 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA08157
	for <ietf-calendar@imc.org>; Sun, 18 Apr 1999 19:46:39 -0700 (PDT)
Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with SMTP id TAA04257
	for <ietf-calendar@imc.org>; Sun, 18 Apr 1999 19:46:35 -0700 (PDT)
Message-Id: <199904190246.TAA04257@engmail2.Eng.Sun.COM>
Date: Sun, 18 Apr 1999 19:46:37 -0700 (PDT)
From: Doug Royer <Doug.Royer@Sun.COM>
Reply-To: Doug Royer <Doug.Royer@Sun.COM>
Subject: Re: Error in rfc2445
To: ietf-calendar@imc.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: nuaGL24OAKLm/HOGPfP91g==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


> Date: Sat, 17 Apr 1999 01:12:33 -0400
> From: Mark Swanson <swansma@geocities.com>
> 
> Hello,
> 
> I've found an error in the spec that would cause people to develop
> incompatible implementations. Check out 4.2.8 - Format Type. iana-token
> and x-name are both inadequate to hold "application/binary" because of
> the "/" character. MIME types are not possible here.
> 
> I don't know where to go from here so I'll leave it in the capable hands
> of the people on this mailing list.


Yep - x-name and iana-token should also allow "/".	

Frank - this needs to be added to the list?

-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL



From owner-ietf-calendar@imc.org  Tue Apr 20 08:26:55 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06976
	for <calsch-archive@odin.ietf.org>; Tue, 20 Apr 1999 08:26:54 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id EAA21577
	for ietf-calendar-bks; Tue, 20 Apr 1999 04:25:21 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id EAA21573
	for <ietf-calendar@imc.org>; Tue, 20 Apr 1999 04:25:19 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04817;
	Tue, 20 Apr 1999 07:25:42 -0400 (EDT)
Message-Id: <199904201125.HAA04817@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-calendar@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-calsch-irip-03.txt
Date: Tue, 20 Apr 1999 07:25:41 -0400
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts
directories.  This draft is a work item of the Calendaring and
Scheduling Working Group of the IETF.

	Title		: ICalendar Real-time Interoperability Protocol (IRIP)
	Author(s)	: A. Courtemanche, S. Mansour, P. O'Leary
	Filename	: draft-ietf-calsch-irip-03.txt
	Pages		: 38
	Date		: 16-Apr-99
	
This document specifies a binding from the iCalendar
Transport-independent Interoperability Protocol [ITIP] to a real-time
transport. Calendaring entries defined by the iCalendar Object Model
[ICAL] are composed using constructs from [RFC-2045], [RFC-2046],
[RFC-2047], [RFC-2048] and [RFC-2049].
 
This document is based on the calendaring and scheduling model defined
by [ICMS].
 
This document is based on discussions within the Internet Engineering
Task Force (IETF) Calendaring and Scheduling (CALSCH) working group.
More information about the IETF CALSCH working group activities can be
found on the IMC website at http://www.imc.org, the IETF website at
http://www.ietf.org/html.charters/calsch-charter.html. Refer to the
references within this document for further information on how to
access these various documents.
 
Distribution of this document is unlimited. Comments and suggestions
for improvement should be sent to the authors.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-calsch-irip-03.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-calsch-irip-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-calsch-irip-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<19990416154941.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-calsch-irip-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-calsch-irip-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990416154941.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-calendar@imc.org  Thu Apr 22 20:04:37 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00712
	for <calsch-archive@odin.ietf.org>; Thu, 22 Apr 1999 20:04:35 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id QAA03826
	for ietf-calendar-bks; Thu, 22 Apr 1999 16:27:09 -0700 (PDT)
Received: from plexus.cst.ca (plexus.CST.CA [207.139.176.42])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id QAA03821
	for <ietf-calendar@imc.org>; Thu, 22 Apr 1999 16:27:08 -0700 (PDT)
Received: from apollo.cst.ca (apollo.CST.CA [193.77.49.44])
	by plexus.cst.ca (8.9.3/1.0.1) with ESMTP id TAA16841
	for <ietf-calendar@imc.org>; Thu, 22 Apr 1999 19:27:54 -0400
Received: from cst.ca (pc-146.CST.CA [193.77.49.86]) by apollo.cst.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id 2RCX0YM5; Thu, 22 Apr 1999 19:29:12 -0400
Message-ID: <371FB067.3724F05A@cst.ca>
Date: Thu, 22 Apr 1999 19:27:35 -0400
From: Alexander Taler <alext@cst.ca>
Reply-To: alext@cst.ca
Organization: CS&T
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Termination for SENDDATA command
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

At the last IETF there was some objection to the use of CRLF "." CRLF
as a termination for data sent with an iRIP command, but there was no
clear agreement on what should be used instead.  Here are the options
that I see, and some of their drawbacks:

1]  Terminate the data with CRLF "." CRLF, escaping "."'s at the 
    beginning of a line a la SMTP.

    --Requires sender and receiver to parse data for CRLF "." 
      sequences.

2]  Provide a byte count when issuing the command, 
    eg "SENDDATA 2345".

    --Requires sender to fully generate data, and count it, prior to 
      commencing transmission.

3]  Provide a termination string when issuing the command, 
    eg "SENDDATA :=="

    --Sender must ensure that string does not appear in transmitted
      data, this may require fully generating and parsing data in 
      some cases.

4]  Send data across another connection, a la FTP.

    --Uh, it's complicated right?
    --Security?


Alex


From owner-ietf-calendar@imc.org  Fri Apr 23 17:17:57 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26818
	for <calsch-archive@odin.ietf.org>; Fri, 23 Apr 1999 17:17:56 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id NAA15340
	for ietf-calendar-bks; Fri, 23 Apr 1999 13:30:19 -0700 (PDT)
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28])
	by mail.proper.com (8.8.8/8.8.5) with SMTP id NAA15335
	for <ietf-calendar@imc.org>; Fri, 23 Apr 1999 13:30:17 -0700 (PDT)
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
	id AA10670; Fri, 23 Apr 99 16:31:30 EDT
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45])
	by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id QAA25735
	for <ietf-calendar@imc.org>; Fri, 23 Apr 1999 16:31:27 -0400 (EDT)
Received: from mona-lisa (MONA-LISA.MIT.EDU [18.172.1.179])
	by melbourne-city-street.MIT.EDU (8.9.2/8.9.2) with SMTP id QAA15149
	for <ietf-calendar@imc.org>; Fri, 23 Apr 1999 16:31:26 -0400 (EDT)
Message-Id: <3.0.2.32.19990423163128.03a99ec0@po10.mit.edu>
X-Sender: pbh@po10.mit.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)
Date: Fri, 23 Apr 1999 16:31:28 -0400
To: ietf-calendar@imc.org
From: "Paul B. Hill" <pbh@mit.edu>
Subject: user != username != authentication-id, and what's a realm
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

Hi,

At the last IETF meeting there were some hallway discussions about the
possible limitations, or implications, of SASL, and how specific SASL
mechanims might interact with CAP or other C&S related protocols. The
following is a short introduction to some of the concepts. I know that some
people that had an early look at this wanted to make comments, but I also
wanted to get this to the list before the next interim meeting. Hopefully
the comments will be made to the list.

Definitions:

User - in the context of this discussion a person, or a physical customer
of a Calendaring and Scheduling system.  A User should not be confused with
the CUA, which is the application or device with which the user interacts.
["The difference is, if you stick a user with a needle, it bleeds." - Bob
Mahoney ]

Username -  An identifier which is intended to map to a user. Note that
usernames do not include host names or service names, because of this
limitation other types of identifiers have been created  for the jargon of
computer security.

Principal - 1) A completely generic term used by the security community to
include both people and computer systems. Coined because it is more
dignified than "thingy" and because "object" and "entity" (which also mean
thingy) were already overused. [1] 2) A uniquely named client or server
instance that participates in a network communication. [2] 3) An entity
which can both prove its identity and verify the identities of other
principals who wish to communicate with it; each user and each service
registered with Kerberos is thus a principal. [3]

authentication-id - The "authentication identifier" used to uniquely
identify the individual connecting to a service. The syntax and semantics
of an authentication-id may be specific to a particular authentication
mechanism, network, and/or host operating system. Coined by people that
couldn't remember what principal means. [4]

Realm -1) Conceptually, it is the name of a collection of accounts that
might include the user's account. Mechanistically, a string to be displayed
to users so they know which username and password to use. [5] 2) A Kerberos
term for all of the principals served by a particular KDC, Key Distribution
Center. [2] 3) Microsoft uses the term Domain to mean Realm in most cases,
the exception being when they talk about DNS domains.

Impersonation vs. on-behalf-of - For the purposes of this discussion
"impersonation" means that a server can reproduce the authentication
information for a user. Doing so permits one server to appear to another
server as if it were the authenticated CUA of the original user.
"On-behalf-of" means that the server is not able to reproduce a user's
authentication and instead must authenticate itself to other servers as a
machine principal. Once it has been authenticated as the machine principal
it may then attempt to carry out the original user's requests.

Some further discussion of the above terms:

Principals, authentication-ids, and usernames are in general simple strings
that do not convey much information. How an authentication mechanism uses
these and other related information has a major impact on system design and
functionality. The following is a brief description of some authentication
mechanisms and their possible impact on the design of a Internet protocol.

Everyone is pretty familiar with the concept of a username, but usernames
are not globally unique. The previous definitions of principal and
authentication-id include uniqueness in the definition.

What do we mean by uniqueness? 

That depends. Uniqueness comes at a price when you try to scale systems to
large numbers. If you try to scale a principal name or authentication-id to
be unique across the entire Internet most names with be difficult to
memorize or type. X.500 addresses the uniqueness with distinguished names,
but most people do not like using DNs in day to day tasks. However, if you
combine a principal name with other information the name will remain
useable by humans but may also be sufficiently unique to be usable on the
Internet. For example paul@mit.edu is sufficiently unique to deliver email
to Paul B. Hill, employed by the Massachusetts Institute of Technology, but
"paul" is not sufficiently unique to be useful on the Internet.

Most IETF participants are familiar with UNIX password files. Traditionally
when using these each host system contains a local copy of a file which
contains a username and an encrypted form of the user's password. Systems
may or may not use a synchronization method to propagate the password
files. In many environments the username "paul" on one machine may not
represent the same user on a different machine. Or the username may
represent the same person but a different password may be required on each
machine. Much of the history of computer security has revolved around
eliminating this source of confusion and the errors that it creates.

SASL, RFC2222, is a framework for implementing strong authentication in an
application. SASL support many different authentication mechanisms. Let's
take a brief look at some of the possible mechanisms and see how they might
impact the functionality of a system.

One possible mechanism is defined in draft-ietf-authentication-03.txt dated
September 2, 1999 and draft-leach-digest-sasl-03.txt. These drafts discuss
the Basic and Digest Access Authentication for HTTP. The first draft is
intended to replace RFC2069. Section 3.1.4 discusses the limitations of the
Digest Access Authentication mechanism. These comments are also directly
applicable to RFC2195, "IMAP/POP AUTHorize Extension for Simple
Challenge/Response".

The Digest authentication scheme suffers from some known limitations. It is
intended as a replacement for Basic authentication and nothing more. It is
a password-based system and (on the server side) suffers from all the same
problems of any password system. In particular, no provision is made in
this protocol for the initial secure arrangement between user and server to
establish the user's password. [6] Users and implementers should be aware
that this protocol is not as secure as Kerberos, and not as secure as any
client-side private-key scheme.  Nevertheless it is better than nothing,
better than what is commonly used with telnet and ftp, and better than
Basic authentication. However, since it prevents chosen plain text attacks,
it is stronger than (e.g.) CRAM-MD5, which has been proposed for use with
LDAP, POP and IMAP (see RFC 2195). It is intended to replace the much
weaker and even more dangerous use of plain text passwords. [5]

Digest Authentication offers no confidentiality protection beyond
protecting the actual password. All of the rest of the challenge and
response are available to an eavesdropper, including the user's name and
authentication realm.  [5]

The draft for HTTP Digest Authentication does offer more than the CRAM-MD5
mechanism defined in RFC 2195. It introduces a realm. This is very
important when you consider the possibility of a CUA connected to one
server but trying to manipulate data on a different server.

A realm may imply many different things depending on the context within
which it is used. For sites using Kerberos a realm maps to a collection of
users and machines within a DNS domain. One Kerberos realm may server an
entire DNS domain. Or a DNS domain may use several different Kerberos realms. 

Ignoring Kerberos for the moment let's look at how a realm may be
interpreted when using traditional UNIX password files. If the password
file is unique to a single host, i.e. not replicated to any other hosts or
centrally managed via some other mechanism, then a realm consists of just
that one machine. However, if a collection of machines have a replicated,
or identical, password file then the realm would map to that collection of
machines. In other words a realm defines the set of machines that have a
consistent username/password pair. (A realm does _not_ include the case
where individual users maintain their own consistent username/password
mapping.)

Assume that Alice uses CUA1 to connect to SV1.example.com and that the
authentication method is CRAM-MD5. Also assume that Alice's principal name
or authentication-id is "alice". Next assume that on the same connection
Alice decides to write to calendar XYZ on SV2.foobar.com. Will this be
permitted? 

My recommendation is NO. If SV1 was able to recreate the CRAM-MD5
authentication for "alice" and "replay" it to SV2 intact there would still
be no guarantee that "alice" on SV1 and "alice" on SV2 both map to Alice.
If neither site forces a good password policy and you scale this scenario
to the Internet it is possible that you could find two systems that had the
same username/password pair but two different users. The degenerate case
occurs when you consider the authentication-id "guest". 

What if we modified the previous scenario slightly. Instead of having SV1
recreate Alice's CRAM-MD5 authentication, SV1 uses any mechanism to
authenticate itself to SV2, as SV1. Then SV1 could assert to its trusting
friend SV2 that it has made sure that "alice" is Alice to please make these
changes to its data. If the initial authentication is done using CRAM-MD5
this behavior is also bad. There is not enough information to determine
that "alice" on SV1 is equivalent to "alice" on SV2.

If we use an authentication method that supports realms we have a lot more
flexibility. Let's assume we have a multi-valued realm where the realms are
example.com and foobar.com. In this case we can assert that
alice@sv1.example.com and alice@sv2.foobar.com both map to the user Alice.
This implies that we can either have SV1 impersonate "alice" and provide
her credentials to SV2, or SV1 can authenticate itself to SV2 as the
service principal sv1@example.com and then assert that it has authenticated
"alice" and would like to modify some data on her behalf.

As the working group refines the VCAR documentation the "authenticated user
list" should be changed to reflect that we want a more complete declaration
which includes a realm or security context information.

ISPs, Portals, and enterprise customers all have very different ways of
managing user information, how could any of this be implemented? 

I think one of the best market segments to compare this against is email
servers. ISPs, Portals, and enterprise customers all buy or build email
servers and manage the user accounts for the system. Some systems have an
internal, proprietary, directory. E.g. the original design of Microsoft
Exchange and Lotus CCmail. Some systems use directories or meta-directories
which are not tightly integrated into the email infrastructure, and which
do not use standard protocols. E.g. the mail systems used at Stanford, CMU,
MIT, and UMich in the late '80s and through most of the '90s. More recently
we have developers understanding the importance of a separate, centralized,
directory which can be accessed via well documented protocols. E.g. LDAP,
NDS, and ADSI being used by Netscape, Novell's Groupwise, and Microsoft
Exchange.  In all cases of using POP3 and SMTP, the CUA does not have to
understand how the server implements its user account management.




Bibliography

[1] "Network Security, Private Communication in a Public World" by Charlie
Kaufman, Radia Perlman, Mike Spencer, Prentice Hall, 1995, ISBN 0-13-061466-1

[2] Kerberos RFC?

[3] "Kerberos: An Authentication Service for Open Network Systems",
Jennifer G. Steiner, Clifford Neuman , Jeffrey I. Schiller

[4] RFC2195, "IMAP/POP AUTHorize Extension for Simple Challenge/Response"

[5] draft-leach-digest-sasl-03.txt, "Using Digest Authentication as  a SASL
Mechanism"

[6] draft-ietf-http-authentication-03.txt, "HTTP Authentication: Basic and
Digest Access Authentication."



From owner-ietf-calendar@imc.org  Fri Apr 23 19:36:39 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27811
	for <calsch-archive@odin.ietf.org>; Fri, 23 Apr 1999 19:36:38 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id QAA16688
	for ietf-calendar-bks; Fri, 23 Apr 1999 16:07:09 -0700 (PDT)
Received: from plexus.cst.ca (plexus.CST.CA [207.139.176.42])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id QAA16684
	for <ietf-calendar@imc.org>; Fri, 23 Apr 1999 16:07:08 -0700 (PDT)
Received: from apollo.cst.ca (apollo.CST.CA [193.77.49.44])
	by plexus.cst.ca (8.9.3/1.0.1) with ESMTP id TAA21502
	for <ietf-calendar@imc.org>; Fri, 23 Apr 1999 19:07:48 -0400
Received: from cst.ca (pc-146.CST.CA [193.77.49.86]) by apollo.cst.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id 2RCX0ZXM; Fri, 23 Apr 1999 19:09:10 -0400
Message-ID: <3720FD2F.371B679B@cst.ca>
Date: Fri, 23 Apr 1999 19:07:27 -0400
From: Alexander Taler <alext@cst.ca>
Reply-To: alext@cst.ca
Organization: CS&T
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Users and calendars in CAP
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi All,

I've realised a mistake that we've been making.  A calid is _not_ a
caladdress.  CAP commands work on calendars, not on caladdresses /
users / principals.  This is what distinguishes CAP commands from iTIP
commands, and as a consequence of this they are governed by a
different security model than iTIP commands.  iTIP commands are
governed by the security model described in [ITIP]: only the
"ORGANIZER" can modify an event, except that "ATTENDEES" can delegate,
indicate participation status, etc.  On the other hand, CAP commands
are governed by access rights described in "VCAR" components in the
calendar store.

Paul Hill pointed out that:
> two tasks that all customers will
> expect to be able to perform, given the current text of the documents. The
> first task is, "I am me, let me modify calendars that I already know
> about." The second task is, "I am me, let me invite (or whatever) this
> other person without knowing the details of what the real calid is.

The second task is already handled by iTIP and iMIP, I create a
VEVENT, with an appropriate ATTENDEE property, and I mail it to the
person.  It is a lot easier to get an email address than a calid.

The first task is the purpose of CAP, I want to be able to manipulate
my calendar, create new events, delete ones I am not interested in,
change or add properties to existing events, etc.

The only trick is to get CAP to perform the second task, since I don't
want to email people whose calendars are stored on the same server as
mine.  The obvious way to do this is to incorporate iTIP into CAP.

CAP should have two sets of methods, the first being iTIP methods
which use caladdresses, the second being CAP methods which use calids.
With this partition it is easy to manipulate calendars ignoring the
iTIP request-reply paradigm, by using calids and the CAP methods.  It is
also easy to request meetings and check busy time, ignoring the issues
of which calendars to use, by using caladdresses and the iTIP methods.

This also addresses some of the questions of fanout.  If CAP fanout is
not available, iTIP fanout can still be used over iRIP or iMIP, and
since CAP uses the iTIP methods themselves, there is no problem of
translation.

Of course the relationship between calids and a caladdresses still has
to be described of course.  A good place to start on this problem is
Paul Hill's observations on the problem.

This also has implications for how authentication is handled.  I will
follow this issue in another post.

Alex


From owner-ietf-calendar@imc.org  Fri Apr 23 19:39:12 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27826
	for <calsch-archive@odin.ietf.org>; Fri, 23 Apr 1999 19:39:11 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id QAA16704
	for ietf-calendar-bks; Fri, 23 Apr 1999 16:07:49 -0700 (PDT)
Received: from plexus.cst.ca (plexus.CST.CA [207.139.176.42])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id QAA16700
	for <ietf-calendar@imc.org>; Fri, 23 Apr 1999 16:07:48 -0700 (PDT)
Received: from apollo.cst.ca (apollo.CST.CA [193.77.49.44])
	by plexus.cst.ca (8.9.3/1.0.1) with ESMTP id TAA21507
	for <ietf-calendar@imc.org>; Fri, 23 Apr 1999 19:08:29 -0400
Received: from cst.ca (pc-146.CST.CA [193.77.49.86]) by apollo.cst.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id 2RCX0ZX3; Fri, 23 Apr 1999 19:09:51 -0400
Message-ID: <3720FD58.8702666A@cst.ca>
Date: Fri, 23 Apr 1999 19:08:08 -0400
From: Alexander Taler <alext@cst.ca>
Reply-To: alext@cst.ca
Organization: CS&T
X-Mailer: Mozilla 4.05 [en] (WinNT; I)
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Users and Authentication Ids in CAP
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi All

I think that we need to make a distinction between authentication ids
and caladdresses.  caladdresses are what we use for scheduling
meetings and defining access rights to the calendar store.  It seems
inappropriate to base these things on the authentication mechanism.
At least one participant at Minneapolis pointed out that he had
multiple personas and would be very happy if these could be handled
appropriately in a CS.  Many people have multiple authentication
systems, eg Kerberos in the office, OTP on the road.  It would be
appropriate to be able map these to a single caladdress for the
purpose of handling access rights and invitations in CAP.

SASL provides an authorization mechanism which fulfills these needs.
I can authenticate using any of a number of authentication mechanisms,
and then authorize to the caladdress which I use.

I could also have multiple caladdresses to which I wish to authorize.
Users on the same calendar store as me will typically invite me using
my CAP caladdress, whereas remote users will use my iRIP caladdress or
a mailto URI.  I would like to be able to authorize to any of these
addresses in order to handle my calendaring information.

This same system could also be used by iRIP.

Alex


From owner-ietf-calendar@imc.org  Sat Apr 24 15:54:19 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13864
	for <calsch-archive@odin.ietf.org>; Sat, 24 Apr 1999 15:54:19 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id MAA26532
	for ietf-calendar-bks; Sat, 24 Apr 1999 12:15:54 -0700 (PDT)
Received: from piinbh2.ms.com (firewall-user@piinbh2.ms.com [199.89.64.72])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id MAA26528
	for <ietf-calendar@imc.org>; Sat, 24 Apr 1999 12:15:53 -0700 (PDT)
Received: (from uucp@localhost)
        by piinbh2.ms.com (8.8.6/fw v1.22) id PAA07276
        for <ietf-calendar@imc.org>; Sat, 24 Apr 1999 15:16:53 -0400 (EDT)
Received: from unknown(144.14.191.100) by piinbh2.ms.com via smap (4.1)
	id xma007072; Sat, 24 Apr 99 15:16:30 -0400
Received: from ms.com (eqhq144.morgan.com [205.228.83.144])
        by hqsmh1.ms.com (8.8.5/imap+ldap v2.3) with ESMTP id PAA22956;
        Sat, 24 Apr 1999 15:16:29 -0400 (EDT)
Message-ID: <3722188C.8243164D@ms.com>
Date: Sat, 24 Apr 1999 15:16:28 -0400
From: David Madeo <dmadeo@ms.com>
Reply-To: dmadeo@ms.com
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.51 [en]C-CCK-MCD   (WinNT; I)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Differences in Rollup
Content-Type: multipart/mixed;
 boundary="------------3C2871BB02CF1B3B521AA0FA"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>

This is a multi-part message in MIME format.
--------------3C2871BB02CF1B3B521AA0FA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Not to be too focused on rollup, but after spending time with Paul going
back and forth on the user issue, it's occurred to me that there's also
a distinction I've been missing (and it appears others have as well),
with rollup.  Alex Taler's mail earlier today highlights these in my
mind.

There's the CUA rollup which I expect can range from the extremely
simple (one set of dates) to the grotesquely complex (multiple views of
multiple input sources).   I expect different implementations will
retrieve data via CAP from various sources and combine it for
presentation in a hopefully wide variety of ways.  This should primarily
be used for a user to create their own personal view of calendar data.
In Alex's parlance, these would involve CALID's, the raw agenda
addresses, presumably hidden away from the user.  It shouldn't be called
rollup, as from the protocol view, it's not.  It's where most of the
discussion of rollup has been though.

Then there's the CS rollup, which provides a simple view of a "user".
Each implementation can figure out how to determine what sources are
used to determine this simple view.  The most primitive will only allow
a single input source, while the more complex will allow multiple
sources with different ratings of how each one affects the free/busy
time.  However, the choice of what gets sent out over the wire needs to
be strictly defined in CAP so that all implementations can equally use
it.  This involves the use of CALADDRESSES, indicating a user, rather
than a raw calendar.

All of this is purely to solve the user demand to be able to see "is Joe
Smith busy today at 5pmEST" and potentially (if properly authorized),
the details of what he's doing.

dmadeo

--------------3C2871BB02CF1B3B521AA0FA
Content-Type: text/x-vcard; charset=us-ascii;
 name="dmadeo.vcf"
Content-Description: Card for David Madeo
Content-Disposition: attachment;
 filename="dmadeo.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Madeo;David
tel;fax:212-762-1009
tel;work:212-762-2348
x-mozilla-html:FALSE
url:www.ms.com
org:Morgan Stanley Dean Witter and Discover;Information Technology
version:2.1
email;internet:dmadeo@ms.com
adr;quoted-printable:;;750 Seventh Ave=0D=0A;NY;NY;10019;USA
x-mozilla-cpt:;0
fn:David Madeo
end:vcard

--------------3C2871BB02CF1B3B521AA0FA--



From owner-ietf-calendar@imc.org  Mon Apr 26 10:53:51 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18089
	for <calsch-archive@odin.ietf.org>; Mon, 26 Apr 1999 10:53:51 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id HAA28809
	for ietf-calendar-bks; Mon, 26 Apr 1999 07:13:27 -0700 (PDT)
Received: from plexus.cst.ca (plexus.CST.CA [207.139.176.42])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id HAA28805
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 07:13:26 -0700 (PDT)
From: andrec@cst.ca
Received: from apollo.cst.ca (apollo.CST.CA [193.77.49.44])
	by plexus.cst.ca (8.9.3/1.0.1) with ESMTP id KAA27227
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 10:14:20 -0400
Received: by apollo.CST.CA with Internet Mail Service (5.5.2448.0)
	id <JSQSP9G4>; Mon, 26 Apr 1999 10:15:48 -0400
Message-ID: <CB739DB1CAD3D21183F00060974F90F00C8A8F@apollo.CST.CA>
To: ietf-calendar@imc.org
Subject: Registration: Montreal Interim Working Group meeting
Date: Mon, 26 Apr 1999 10:15:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>


Errata:

Anybody who intends to attend should register
with Eileen Ingham (EileenI@cst.ca).







From owner-ietf-calendar@imc.org  Mon Apr 26 10:59:30 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18173
	for <calsch-archive@odin.ietf.org>; Mon, 26 Apr 1999 10:59:30 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id HAA28776
	for ietf-calendar-bks; Mon, 26 Apr 1999 07:10:21 -0700 (PDT)
Received: from plexus.cst.ca (plexus.CST.CA [207.139.176.42])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id HAA28772
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 07:10:20 -0700 (PDT)
From: andrec@cst.ca
Received: from apollo.cst.ca (apollo.CST.CA [193.77.49.44])
	by plexus.cst.ca (8.9.3/1.0.1) with ESMTP id KAA27211;
	Mon, 26 Apr 1999 10:11:14 -0400
Received: by apollo.CST.CA with Internet Mail Service (5.5.2448.0)
	id <JSQSP9GN>; Mon, 26 Apr 1999 10:12:42 -0400
Message-ID: <CB739DB1CAD3D21183F00060974F90F00C8A8C@apollo.CST.CA>
To: ietf-calendar@imc.org
Cc: Eileenh@cst.ca
Subject: Montreal Interim Working Group meeting
Date: Mon, 26 Apr 1999 10:12:41 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.proper.com id HAA28773
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit


Montreal Interim Working Group meeting

CS&T is hosting an Interim working group meeting
for the CAP protocol, June 15th and 16th. The event
will start with a group dinner on June 14t. The 
Meeting will  happen in Montreal, Canada.

Anybody who intends to attend should register
with Eileen Ingham (Eileenh@cst.ca).

I suggest that people quickly make reservations 
as it happens concurrently with the Montreal
Jazz festival.

Here are suggested hotels. All rates are approximate
in Canadian dollars.

L'Hôtel de la Montagne  RATES $125 - STANDARD - SUITES $225  - CDN.
1430 de la Montagne Street
Montréal (Québec) H3G 1Z5
Métro: Peel
Tel.: (514) 288-5656 Fax: (514) 288-9658
Toll free: 1-800-361-6262

Hôtel Omni Montréal  RATES $219 - STANDARD - DELUXE - $229 - CDN.
1050 Sherbrooke Street West
Montréal (Québec) H3A 2R6
Métro: Peel 
Tel.: (514) 284-1110 Fax: (514) 845-3025
Toll free: 1-800-223-3000
E-mail: westin-anja@IQ.CA


Andre Courtemanche
CS&T.







From owner-ietf-calendar@imc.org  Mon Apr 26 11:52:01 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18883
	for <calsch-archive@odin.ietf.org>; Mon, 26 Apr 1999 11:52:00 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id IAA29326
	for ietf-calendar-bks; Mon, 26 Apr 1999 08:06:39 -0700 (PDT)
Received: from sparcmail.cube.com (sparcmail.cube.com [207.242.168.22])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id IAA29322
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 08:06:37 -0700 (PDT)
Received: from appoint.net (mail.appoint.net [207.242.168.162])
	by sparcmail.cube.com (8.9.1/8.9.1) with ESMTP id KAA22146
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 10:56:25 -0400 (EDT)
Received: from ariel.appoint.lan [209.218.166.130] by appoint.net with ESMTP
  (SMTPD32-5.00) id A1C1D3000E4; Mon, 26 Apr 1999 11:09:53 EST
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id LAA01662
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 11:07:48 -0400
Message-ID: <37248144.DA63809E@ecal.com>
Date: Mon, 26 Apr 1999 15:07:48 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: user != username != authentication-id, and what's a realm
References: <3.0.2.32.19990423163128.03a99ec0@po10.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Paul B. Hill" wrote:

> Principal [...] 3) An entity
> which can both prove its identity and verify the identities of other
> principals

Aren't these two separate functions? I believe there are cases where an entity
needs to be able to prove its identity, but does not care to verify anybody
else's identity.  As an easy example, consider a broadcast model, where the
sender may want to prove that its identity, so that nobody else can spoof its
messages, but doesn't care who the receivers are.  For a calendar-related
example, suppose I'm running on a trusted intranet, where I know that, when I
connect to the CS's address, I can be sure I'm getting the CS; in such a case,
the CS doesn't need to authenticate itself to the CUA, and I may want a CUA and
a CS that let me disable such authentication.  (Of course, another view is that,
in this case, the CUA is still verifying the CS's credentials, but those
credentials are the IP number and port.)

I do agree with your conclusions; I'm just unsure about the implications of this
definition.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





From owner-ietf-calendar@imc.org  Mon Apr 26 11:59:41 1999
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19028
	for <calsch-archive@odin.ietf.org>; Mon, 26 Apr 1999 11:59:40 -0400 (EDT)
Received: (from majordomo@localhost)
	by mail.proper.com (8.8.8/8.8.5) id IAA29377
	for ietf-calendar-bks; Mon, 26 Apr 1999 08:10:46 -0700 (PDT)
Received: from sparcmail.cube.com (sparcmail.cube.com [207.242.168.22])
	by mail.proper.com (8.8.8/8.8.5) with ESMTP id IAA29372
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 08:10:44 -0700 (PDT)
Received: from appoint.net (mail.appoint.net [207.242.168.162])
	by sparcmail.cube.com (8.9.1/8.9.1) with ESMTP id LAA22211
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 11:00:34 -0400 (EDT)
Received: from ariel.appoint.lan [209.218.166.130] by appoint.net with ESMTP
  (SMTPD32-5.00) id A2BFE4F0138; Mon, 26 Apr 1999 11:14:07 EST
Received: from ecal.com (localhost [127.0.0.1])
	by ariel.appoint.lan (8.8.7/8.8.7) with ESMTP id LAA01678
	for <ietf-calendar@imc.org>; Mon, 26 Apr 1999 11:12:02 -0400
Message-ID: <37248242.44BCF62D@ecal.com>
Date: Mon, 26 Apr 1999 15:12:02 +0000
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.51 [en] (X11; U; Linux 2.0.36 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-calendar@imc.org
Subject: Re: Users and calendars in CAP
References: <3720FD2F.371B679B@cst.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-calendar@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-calendar/mail-archive/>
List-Unsubscribe: <mailto:ietf-calendar-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Alexander Taler wrote:

> The only trick is to get CAP to perform the second task, since I don't
> want to email people whose calendars are stored on the same server as
> mine.

Or whose calendars your server can access via iRIP.

> The obvious way to do this is to incorporate iTIP into CAP.

I'm not sure we want to incorporate it; a better approach might be to have CUAs
implement both CAP and iRIP.  That way we avoid the complications of defining
yet another transport binding for iTIP.

On the other hand, there is certainly some advantage to having CAP-like and
iTIP-like functionality occur over the same TCP link.  Perhaps CAP could be an
extension of iRIP?

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/





