Re: [calsify] review of draft-ietf-calext-eventpub-extensions-00
Daniel Migault <daniel.migault@ericsson.com> Tue, 22 November 2016 14:32 UTC
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E135129A2B for <calsify@ietfa.amsl.com>; Tue, 22 Nov 2016 06:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.139
X-Spam-Level:
X-Spam-Status: No, score=-2.139 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 bn4SJvTrZUDZ for <calsify@ietfa.amsl.com>; Tue, 22 Nov 2016 06:32:44 -0800 (PST)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2CA6129A27 for <calsify@ietf.org>; Tue, 22 Nov 2016 06:32:43 -0800 (PST)
Received: by mail-it0-x22f.google.com with SMTP id j191so13031887ita.1 for <calsify@ietf.org>; Tue, 22 Nov 2016 06:32:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=wzGyiQT71uaW/qHRMyR9t2LH7dDFW4lPIUoeqZQM1zw=; b=YCOGZLXhXTzRrtPh210Xfs4CDS1Vk2eLWnXA3+Ox2QtNU7Hj8jRafEPH5g1gwglZOH hd1NzrniSeyIzMjMzAseDsggUYnRYI1kQ4mESGlqgCrB+5Rg0RLp606UiNKrCm50vhg7 lRntRC4yHQiIbVYQ4Q9S2tfHJA0+1a/CYnuTG6rSSfghbYwEgqJ4laeJ3NGxcW6iRghw 2r0wpXFMVzeW6rS30S2phK/YgkVn1xkSXu2kTTj8GB1NyeZlm4ycgb/uP/ovhQXqn3Xr bSQyb9wM7QKMwlT9DnDzSQLYdwOj+a0hy3ayDExjOQZia5fGmgGNlX1dHt12DrUbdiRT gmQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=wzGyiQT71uaW/qHRMyR9t2LH7dDFW4lPIUoeqZQM1zw=; b=LK1hBsy6vgj30Sh8/azlcWDhfvL/1t/HVBlCTDmB9ep+DA/kxCca2xSAj3RtypsIHr wrh8NRdCwu64Fdbcg+F32F5SKBdkmH2SDMSdmdLbSOBx+sPWGc52knuD493M7/ZopFkq 5b+cB50eJrkNMSDIx3RpkuRRws863DyeTWUhtwAUU+Vj8E9IAAGj9OX68QAv30w63mtJ 0PjSM6Ln3pMQzdBCMxtsO4hxJR4neYrHmkJ404hx7I8SOugrcAZ2HkKVehLoAXOLp83A OtPICH6tL/NxSYMUokV+TvVObdsy2nTXL6alPi15J8OCb0klFjm2Sk0RHbAzUJyt1fde LCng==
X-Gm-Message-State: AKaTC01fYdE02giW4QK307v9ppk6jgSGaThwpiWzsyVWLa1hI/CJOOWMWVYtCHM4mwFxOPKLMEyGa/UvcD9vMA==
X-Received: by 10.36.19.67 with SMTP id 64mr2669073itz.120.1479825163306; Tue, 22 Nov 2016 06:32:43 -0800 (PST)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.107.32.10 with HTTP; Tue, 22 Nov 2016 06:32:42 -0800 (PST)
In-Reply-To: <2da96ddb-ba41-0074-01cc-309482679791@andrew.cmu.edu>
References: <CADZyTknz=cYREHPZunxmQHcT5+b=FfeWV3PQFxqoyzBv19rYUw@mail.gmail.com> <a2e1f1bb-91c1-f8f1-a843-8ecf69a2938f@gmail.com> <4700015a-bb03-f5c8-564f-690adb93aff8@andrew.cmu.edu> <33aceebe-624b-dc74-c23b-3bbbc4968a95@gmail.com> <2da96ddb-ba41-0074-01cc-309482679791@andrew.cmu.edu>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Tue, 22 Nov 2016 09:32:42 -0500
X-Google-Sender-Auth: KAbON6NxM6rYpKRxejrmDli05O8
Message-ID: <CADZyTkmZzqha1ejg6omaBjh5E+bRnQ5E4-YHTPA9OukKjYjyow@mail.gmail.com>
To: Ken Murchison <murch@andrew.cmu.edu>
Content-Type: multipart/alternative; boundary="001a11445368304c450541e4a5b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/P6TrfHvEe0jFEtQyF0Z6ONoUwBI>
Cc: "calsify@ietf.org" <calsify@ietf.org>
Subject: Re: [calsify] review of draft-ietf-calext-eventpub-extensions-00
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2016 14:32:48 -0000
Hi, Looks to me that issues have been at least partly solved... Do we think we have received sufficient inputs to have a 01 version ? Yours, Daniel On Wed, Oct 19, 2016 at 3:33 PM, Ken Murchison <murch@andrew.cmu.edu> wrote: > OK, understood. If future drafts will be using such a construct, we might > as well introduce it in this draft. > > > > On 10/19/2016 03:15 PM, Michael Douglass wrote: > >> >> >> On 10/19/16 12:29, Ken Murchison wrote: >> >>> Hi Mike, >>> >>> >>> On 10/19/2016 11:16 AM, Michael Douglass wrote: >>> >>>> Thanks for the comments - and sorry for the delay. >>>> >>>> I've added my responses to your comments below. >>>> >>>> I'll post a new draft in a short while: there are 2 issues at least >>>> I'd like to address: >>>> >>>> 1. Should the ASSOCIATE property really be a component? >>>> Other extensions to the iCalendar data model are requiring us to >>>> handle deeper nesting of components and in any case a component more >>>> closely matches XML and JSON representations >>>> >>> >>> I'm not opposed to making ASSOCIATE a component, but what other >>> meta-data would be needed for an ASSOCIATE beyond what is currently >>> specified to warrant the change? Do you have an example in mind that >>> you could flesh out? >>> >> >> So this is from https://tools.ietf.org/html/draft-apthorp-ical-tasks-01 >> >> >> 3.4.2. Relating comments to status >> >> The GROUP parameter is used with the STATUS or ATTENDEE properties to >> relate an associated COMMENT property. The COMMENT property can then >> be used to include additional human readable information about why >> the associated STATUS or ATTENDEE property changed. >> >> STATUS;REASON="http://example.com/reason/delivery-failed";SUBSTATE >> =ERROR;MODIFIED=20130212T120000Z;GROUP=G1:FAILED >> COMMENT;MODIFIED=20130226T110451Z;GROUP=G1:Breakdown >> >> ATTENDEE;PARTSTAT=FAILED;MODIFIED=20130226T1104510Z;GROUP=G2: >> REASON="http://example.com/reason/van-break-down":mailto: >> xxx@example.com >> COMMENT;MODIFIED=20130226T110451Z;GROUP=G2:Puncture >> >> (An aside - I think the example is faulty - a ":" wheer there should eb a >> ";") >> >> The problem we had to address here is that we wanted a bunch of >> properties to be related to a specific attendee - so we used the GROUP >> parameter. >> >> Significantly more readable and probably easier to manipulate is the >> approach of putting all that inside a component >> >> Inventing one... >> >> BEGIN VATTENDEE >> ATTENDEE:PARTSTAT=FAILED;MODIFIED=20130226T1104510Z:xxx@example.com >> REASON="http://example.com/reason/van-break-down" >> COMMENT;MODIFIED=20130226T110451Z:Puncture >> END VATTENDEE >> >> >> In fact any attendee attributes could be stored there. I think in vpoll >> we ended up adopting tha approach for the voter - which could also be an >> associate if we made it a component >> >> _______________________________________________ >> calsify mailing list >> calsify@ietf.org >> https://www.ietf.org/mailman/listinfo/calsify >> > > -- > Kenneth Murchison > Principal Systems Software Engineer > Carnegie Mellon University > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify >
- [calsify] review of draft-ietf-calext-eventpub-ex… Daniel Migault
- Re: [calsify] review of draft-ietf-calext-eventpu… Michael Douglass
- Re: [calsify] review of draft-ietf-calext-eventpu… Ken Murchison
- Re: [calsify] review of draft-ietf-calext-eventpu… Michael Douglass
- Re: [calsify] review of draft-ietf-calext-eventpu… Ken Murchison
- Re: [calsify] review of draft-ietf-calext-eventpu… Daniel Migault