[Enum] comment on draft-ietf-enum-calendar-service-04
Alexander Mayrhofer <alexander.mayrhofer@enum.at> Wed, 12 March 2008 15:24 UTC
Return-Path: <enum-bounces@ietf.org>
X-Original-To: ietfarch-enum-archive@core3.amsl.com
Delivered-To: ietfarch-enum-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61EFC28C658; Wed, 12 Mar 2008 08:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.111
X-Spam-Level:
X-Spam-Status: No, score=-100.111 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_45=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 d1nBu2VH80U7; Wed, 12 Mar 2008 08:24:34 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4666E28C241; Wed, 12 Mar 2008 08:24:31 -0700 (PDT)
X-Original-To: enum@core3.amsl.com
Delivered-To: enum@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3982328C658 for <enum@core3.amsl.com>; Wed, 12 Mar 2008 08:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 K4FQcfwMxuuu for <enum@core3.amsl.com>; Wed, 12 Mar 2008 08:24:25 -0700 (PDT)
Received: from kahua.nona.net (pahula.nona.net [193.80.224.123]) by core3.amsl.com (Postfix) with ESMTP id A948B28C241 for <enum@ietf.org>; Wed, 12 Mar 2008 08:24:16 -0700 (PDT)
Received: from [130.129.21.190] ([::ffff:130.129.21.190]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Wed, 12 Mar 2008 16:19:59 +0100 id 00038026.47D7F4A0.0000126D
Message-ID: <47D7F505.4080808@enum.at>
Date: Wed, 12 Mar 2008 16:21:41 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Organization: enum.at GmbH
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: enum@ietf.org, rohan@ekabal.com
Subject: [Enum] comment on draft-ietf-enum-calendar-service-04
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: enum-bounces@ietf.org
Errors-To: enum-bounces@ietf.org
Hi,
i'm a bit hesitant about the "sched" subtype being used for both iMIP
and CalDAV. Essentially that would mean that any ical:sched capable
client would need to support both protocols, because it must not select
a NAPTR by looking at the URI scheme...
Is that intended?
An alternative would be to define seperate subtypes for iMIP and CalDAV
scheduling protocols, so that a client which does not support CalDAV
does not "run" into a URI scheme that it cannot use.
Actually this might even be a use case for those nasty "sub-sub-Types"
("ical:sched:imip" and "ical:sched:caldav", but i'm pretty sure we don't
want to go down this road, do we?
comments?
Alex
_______________________________________________
enum mailing list
enum@ietf.org
https://www.ietf.org/mailman/listinfo/enum
- [Enum] comment on draft-ietf-enum-calendar-servic… Alexander Mayrhofer
- Re: [Enum] comment on draft-ietf-enum-calendar-se… Duane