IETF Logo Mail Archive

Re: [caldav] various question on scheduling draft

"Tim Hare" <TimHare@comcast.net> Sat, 17 October 2009 19:15 UTC

Return-Path: <timhare@comcast.net>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9C5D3A68A9 for <caldav@core3.amsl.com>; Sat, 17 Oct 2009 12:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fwruqeATt677 for <caldav@core3.amsl.com>; Sat, 17 Oct 2009 12:15:17 -0700 (PDT)
Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id C62983A67F2 for <caldav@ietf.org>; Sat, 17 Oct 2009 12:15:16 -0700 (PDT)
Received: from OMTA24.westchester.pa.mail.comcast.net ([76.96.62.76]) by QMTA10.westchester.pa.mail.comcast.net with comcast id tvBD1c0021ei1Bg5AvFNjp; Sat, 17 Oct 2009 19:15:22 +0000
Received: from THARE ([71.203.105.66]) by OMTA24.westchester.pa.mail.comcast.net with comcast id tvN21c00B1RyUCv3kvN2UA; Sat, 17 Oct 2009 19:22:03 +0000
From: Tim Hare <TimHare@comcast.net>
To: caldav@ietf.org
References: <4AC23DBD.6020206@sun.com> <4AD737D5.7040300@oracle.com> <002901ca4dab$f9ba6850$ed2f38f0$@net> <88061EBB-EA5E-4129-A358-840BA7F8C794@opengroupware.org>
In-Reply-To: <88061EBB-EA5E-4129-A358-840BA7F8C794@opengroupware.org>
Date: Sat, 17 Oct 2009 15:15:09 -0400
Message-ID: <002a01ca4f5e$26201f80$72605e80$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcpNsEa/7XHj38poTS697nOnn7emFABrXP6w
Content-Language: en-us
Subject: Re: [caldav] various question on scheduling draft
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Oct 2009 19:15:17 -0000

In light of the comments below, then perhaps the PRODID should be defined as
the identifier for the product which last rewrote or updated the iCalendar
object.   I would not intend it for user-agent identification, but as a
debugging tool only - if everyone complied with the standard we could at
least see what last touched the object.

Tim

>For example our Outlook plugin only touches the parts of the iCalendar  
>entity which it knows about, other parts are preserved as-is. Hence  
>the resulting iCalendar entity after PUT operations is like a mixture  
>between two or even more clients.

>I'm not sure what the PRODID is good for anyways, user-agent sniffing  
>is dangerous ...

>Greets,
>   Helge
>-- 
>Helge Hess
>http://zideone.com/

v2.23.0 | Report a Bug | By Email