Re: [Enum] comment on draft-ietf-enum-calendar-service-04
Duane <duane@e164.org> Wed, 12 March 2008 18:04 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 C2D1F28C6F0; Wed, 12 Mar 2008 11:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.797
X-Spam-Level:
X-Spam-Status: No, score=-100.797 tagged_above=-999 required=5 tests=[AWL=-0.360, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, 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 i4COmbIcsl7y; Wed, 12 Mar 2008 11:04:31 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE71628C625; Wed, 12 Mar 2008 11:04: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 F2AAC28C625 for <enum@core3.amsl.com>; Wed, 12 Mar 2008 11:04: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 tuRNIoREyXMH for <enum@core3.amsl.com>; Wed, 12 Mar 2008 11:04:30 -0700 (PDT)
Received: from mail.aus-biz.com (mail.aus-biz.com [208.82.100.153]) by core3.amsl.com (Postfix) with ESMTP id 1840528C462 for <enum@ietf.org>; Wed, 12 Mar 2008 11:04:29 -0700 (PDT)
Received: from [192.168.2.144] (220-245-82-41.static.tpgi.com.au [220.245.82.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.aus-biz.com (Postfix) with ESMTP id D922D4B8072 for <enum@ietf.org>; Thu, 13 Mar 2008 05:02:11 +1100 (EST)
Message-ID: <47D81A9D.1010209@e164.org>
Date: Thu, 13 Mar 2008 05:02:05 +1100
From: Duane <duane@e164.org>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: "enum@ietf.org" <enum@ietf.org>
References: <47D7F505.4080808@enum.at>
In-Reply-To: <47D7F505.4080808@enum.at>
X-Enigmail-Version: 0.95.0
Subject: Re: [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
Alexander Mayrhofer wrote:
> 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.
there is sub-types to distinguish other url types and even duplicates of
some url types as sub-url types......
> 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?
So things aren't messy enough for you, that you want to go and make a
new one? :)
--
Best regards,
Duane
_______________________________________________
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