IETF Logo Mail Archive

Re: [Jcardcal] Stephen Farrell's No Objection on draft-ietf-jcardcal-jcal-09: (with COMMENT)

Philipp Kewisch <kewisch@gmail.com> Mon, 24 March 2014 21:29 UTC

Return-Path: <kewisch@gmail.com>
X-Original-To: jcardcal@ietfa.amsl.com
Delivered-To: jcardcal@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A051A02A9; Mon, 24 Mar 2014 14:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bi_Fll0bOYAy; Mon, 24 Mar 2014 14:29:28 -0700 (PDT)
Received: from mail-bk0-x22e.google.com (mail-bk0-x22e.google.com [IPv6:2a00:1450:4008:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E38BE1A02AF; Mon, 24 Mar 2014 14:29:23 -0700 (PDT)
Received: by mail-bk0-f46.google.com with SMTP id v15so635004bkz.33 for <multiple recipients>; Mon, 24 Mar 2014 14:29:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+5qb794fB+U+9wgKenX1woe0+3zmxLse+GMUTs56P7c=; b=cPXq4oS8SwlHZdIJKo9mJh+q4TpQiBc5HHYiyegAQ+8L4puxI89EbjxrseAbESYv+g 6TJ7yIkIq6CLnPbvnfRFOHjBqR3UdPObUWDJVLlcg6DA1FpNVjvDSi7+FTTf6v8XAvl5 BoTu+puDlRAojoFy3Sl2kLIlg+TlhaPgUllH13yOpgOJFAhuUewjCRCSMzfo7Y/yCbpM 2wsVQrBAwgTW19TKie27PSdd4ZOI0SUzq4a4BAne9qWv83Gy7WPehqiNPu4+pXTvWI9j nMksRLoelz7OXO2A/p94/p2gnSy5d44ibR5ewGQIclcWeSOwOiGeXq1QRDGHLMWEgNnw /u9w==
X-Received: by 10.204.103.9 with SMTP id i9mr37676501bko.14.1395696562522; Mon, 24 Mar 2014 14:29:22 -0700 (PDT)
Received: from [192.168.2.104] (p5DC1549E.dip0.t-ipconnect.de. [93.193.84.158]) by mx.google.com with ESMTPSA id tg13sm15946531bkb.10.2014.03.24.14.29.21 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Mar 2014 14:29:21 -0700 (PDT)
Message-ID: <5330A3B0.3080900@gmail.com>
Date: Mon, 24 Mar 2014 22:29:20 +0100
From: Philipp Kewisch <kewisch@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Thunderbird/28.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <20140324210114.12842.55998.idtracker@ietfa.amsl.com> <CALaySJLf14Mvjkqmb46DyPq5jhORiq_X_p4T28fxhHhKOcLRdw@mail.gmail.com>
In-Reply-To: <CALaySJLf14Mvjkqmb46DyPq5jhORiq_X_p4T28fxhHhKOcLRdw@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/jcardcal/t2UgYvEDaDvotabvBj6QKT0TZBo
Cc: draft-ietf-jcardcal-jcal@tools.ietf.org, The IESG <iesg@ietf.org>, jcardcal-chairs@tools.ietf.org, "jcardcal@ietf.org" <jcardcal@ietf.org>
Subject: Re: [Jcardcal] Stephen Farrell's No Objection on draft-ietf-jcardcal-jcal-09: (with COMMENT)
X-BeenThere: jcardcal@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: JSON data formats for vCard and iCalendar WG <jcardcal.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jcardcal/>
List-Post: <mailto:jcardcal@ietf.org>
List-Help: <mailto:jcardcal-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Mar 2014 21:29:30 -0000

On 3/24/14, 10:10 PM, Barry Leiba wrote:
>> section 1: this is odd: "Extensions to the underlying
>> iCalendar specification must not lead to requiring an update
>> to jCal." How are you going to prevent that happening?  I
>> think the best you can do is point out how such an extension
>> could break jcal and recommend to not do that.
> It's a lower-case "must not".  What it's saying is that jCal is
> designed to accommodate extensions to iCalendar, without requiring
> changes to jCal.  It's not talking about changes that might show up in
> a new major iCalendar version... just changes that use the normal
> iCalendar extension mechanisms.
>
Indeed, this was the intent. Do you still think it needs changing?

Philipp

v2.23.0 | Report a Bug | By Email