IETF Logo Mail Archive

Re: [caldav] various question on scheduling draft

Helge Hess <helge.hess@opengroupware.org> Thu, 15 October 2009 15:57 UTC

Return-Path: <helge.hess@opengroupware.org>
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 9BF4728C11E for <caldav@core3.amsl.com>; Thu, 15 Oct 2009 08:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 GTU5zkbIg6an for <caldav@core3.amsl.com>; Thu, 15 Oct 2009 08:57:56 -0700 (PDT)
Received: from mail.mdlink.net (mail.mdlink.net [213.211.192.40]) by core3.amsl.com (Postfix) with ESMTP id 8CB8D28C11D for <caldav@ietf.org>; Thu, 15 Oct 2009 08:57:56 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.mdlink.net (Postfix) with ESMTP id BA93865001B; Thu, 15 Oct 2009 17:57:58 +0200 (CEST)
Received: from [192.168.0.111] (91-65-139-32-dynip.superkabel.de [91.65.139.32]) by mail.mdlink.net (Postfix) with ESMTP id 5B7B6125001F; Thu, 15 Oct 2009 17:57:58 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
From: Helge Hess <helge.hess@opengroupware.org>
In-Reply-To: <002901ca4dab$f9ba6850$ed2f38f0$@net>
Date: Thu, 15 Oct 2009 17:57:57 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <88061EBB-EA5E-4129-A358-840BA7F8C794@opengroupware.org>
References: <4AC23DBD.6020206@sun.com> <4AD737D5.7040300@oracle.com> <002901ca4dab$f9ba6850$ed2f38f0$@net>
To: Tim Hare <TimHare@comcast.net>
X-Mailer: Apple Mail (2.1076)
Cc: 'Arnaud Quillaud' <Arnaud.Quillaud@Sun.COM>, caldav@ietf.org
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: Thu, 15 Oct 2009 15:57:57 -0000

On 15.10.2009, at 17:27, Tim Hare wrote:
> In RFC 5445 for PRODID
>
> "   Purpose:  This property specifies the identifier for the product  
> that
>      created the iCalendar object."
>
> While it doesn't say this is REQUIRED or 'MUST specify' I believe  
> that is
> the intent.  The language could perhaps specify that requirement in  
> the
> future, with some standardized form for 'hand-edited' items.  For  
> interop
> troubleshooting issues it is critical that we know what created the
> particular object we're looking at.

In the context of CalDAV its a bit more complicated than with the  
throwaway iMIP entities (which the original iCal authors probably had  
in mind).
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