[ischedule] Capabilities question
Mike Douglass <douglm@rpi.edu> Thu, 10 December 2009 18:30 UTC
Return-Path: <douglm@rpi.edu>
X-Original-To: ischedule@core3.amsl.com
Delivered-To: ischedule@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0940828C126 for <ischedule@core3.amsl.com>; Thu, 10 Dec 2009 10:30:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level:
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74]
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 aFjLqldw6vp8 for <ischedule@core3.amsl.com>; Thu, 10 Dec 2009 10:30:15 -0800 (PST)
Received: from smtp8.server.rpi.edu (smtp8.server.rpi.edu [128.113.2.228]) by core3.amsl.com (Postfix) with ESMTP id B69FD3A6874 for <ischedule@ietf.org>; Thu, 10 Dec 2009 10:30:11 -0800 (PST)
Received: from [128.113.124.223] (blue-eyes-white-dragon-15.dynamic2.rpi.edu [128.113.124.223]) (authenticated bits=0) by smtp8.server.rpi.edu (8.13.1/8.13.1) with ESMTP id nBAITwpk020158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ischedule@ietf.org>; Thu, 10 Dec 2009 13:29:59 -0500
Message-ID: <4B213E26.8070703@rpi.edu>
Date: Thu, 10 Dec 2009 13:29:58 -0500
From: Mike Douglass <douglm@rpi.edu>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: ischedule@ietf.org
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always)
X-CanItPRO-Stream: outgoing
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.228
Subject: [ischedule] Capabilities question
X-BeenThere: ischedule@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Internet Calendar Scheduling Protocol \(iSchedule\) discussion list" <ischedule.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ischedule>, <mailto:ischedule-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ischedule>
List-Post: <mailto:ischedule@ietf.org>
List-Help: <mailto:ischedule-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ischedule>, <mailto:ischedule-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Dec 2009 18:30:16 -0000
The comp element in <supported-scheduling-message-set>:
I assume
<comp name="VEVENT">
<method name="REQUEST"/>
<method name="ADD"/>
<method name="REPLY"/>
<method name="CANCEL"/>
</comp>
means ONLY those methods for events - that's fine.
What does this mean:
<comp name="VTODO"/>
NO methods or ANY method?
--
Mike Douglass douglm@rpi.edu
Senior Systems Programmer
Communication & Collaboration Technologies 518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180
- [ischedule] Capabilities question Mike Douglass