From nobody Thu Nov 10 18:23:21 2016 Return-Path: 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 05FDF129517 for ; Thu, 10 Nov 2016 18:23:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.497 X-Spam-Level: X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net 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 xO2kLxiOCW_2 for ; Thu, 10 Nov 2016 18:23:18 -0800 (PST) Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC4491294C0 for ; Thu, 10 Nov 2016 18:23:18 -0800 (PST) Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-07v.sys.comcast.net with SMTP id 51UkcW6ecff8q51UscPOGP; Fri, 11 Nov 2016 02:23:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1478830998; bh=PjCm/aDn6Td7lTw7/F7Gk44ShVJ/CS10IEzdrq5vNyk=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=Farf8tRCojcAXuSjnb09lOP8/QFDLrlCQiY1NaJWw8KJPPF+XF5nEx5B0A+12GTu0 P/CwOS+d3yrj4IJHVFKPnqXlKh52SeGWvZxdzBooozsqq5xqWkGHa/sQezaU7M0Eee 9arSEOymXIBIT4hVshlz5X1LUjWfX2gzOuuFYDTyZx0jFTs97PiIXt3DPqSKhsY6hZ e6PEcYe0jxieBKDuWNHAdpN6azKDN87GlGUOCoZjk2B+O/LJKi2B5tTxyNVSTqtCjC stjPE46m7DZW4Y1iAXvF2AahL+AZ92+z90WSHhijGrE1n7lqEvHcVAaHJbCGAOZ0Ef M3jTL7fOKGKsA== Received: from THARE ([73.42.15.222]) by resomta-ch2-09v.sys.comcast.net with SMTP id 51UqcCS5K0vPt51Urc3zAt; Fri, 11 Nov 2016 02:23:18 +0000 From: "Tim Hare" To: Date: Thu, 10 Nov 2016 21:23:14 -0500 Message-ID: <01a701d23bc2$8f56f2a0$ae04d7e0$@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdI7woegHpwmVgBSRe69dBpYe45pUA== Content-Language: en-us X-CMAE-Envelope: MS4wfD4ntQFmNFR4Ae4agGlW5YyHDIpntFbrN+9uEU12Q1+13Bz+2U9PErNDzRUlefiOXcKjzTnoFlKQMZcwcSZ/T+YO91uxZlwDZxulpxMI28HCSQke5Yu0 6Qu6fP9cdvE6M8qYZkQgt775IVFMHCar/cg= Archived-At: Subject: [calsify] timezone article, possibly of interest to the group X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 02:23:20 -0000 http://www.nytimes.com/2016/11/06/opinion/sunday/time-to-dump-time-zones.htm l?_r=0 From nobody Mon Nov 14 12:54:33 2016 Return-Path: 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 A83DA12946E for ; Mon, 14 Nov 2016 12:54:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no 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 oCzV5-tmBONQ for ; Mon, 14 Nov 2016 12:54:30 -0800 (PST) Received: from oak.morsemedia.net (oak.morsemedia.net [162.213.2.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6CE7127A91 for ; Mon, 14 Nov 2016 12:54:30 -0800 (PST) Received: from 47-208-67-174.erkacmtk02.res.dyn.suddenlink.net ([47.208.67.174]:43516 helo=[192.168.0.218]) by oak.morsemedia.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1c6OGm-001oWN-Sx; Mon, 14 Nov 2016 12:54:24 -0800 From: Dave.Thewlis@calconnect.org Content-Type: multipart/alternative; boundary="Apple-Mail=_4EA1978D-5942-4711-BA18-60383271ADED" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Mon, 14 Nov 2016 12:54:24 -0800 Message-Id: <53D20B40-1191-429B-B7F2-D8C290C7E83A@calconnect.org> To: "calsify@ietf.org" X-Mailer: Apple Mail (2.3251) X-MorseMedia-MailScanner-Information: Please contact the ISP for more information X-MorseMedia-MailScanner-ID: 1c6OGm-001oWN-Sx X-MorseMedia-MailScanner: Found to be clean X-MorseMedia-MailScanner-SpamCheck: X-MorseMedia-MailScanner-From: dave.thewlis@calconnect.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - oak.morsemedia.net X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - calconnect.org X-Get-Message-Sender-Via: oak.morsemedia.net: authenticated_id: dave@dcta.com X-Authenticated-Sender: oak.morsemedia.net: dave@dcta.com X-Source: X-Source-Args: X-Source-Dir: Archived-At: Subject: [calsify] [Calconnect-l] Registration is open and hotel rooms can be booked for CalConnect XXXVIII in Irvine, California, February 13-17, 2017, hosted by the University of California, Irvine X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 20:54:32 -0000 --Apple-Mail=_4EA1978D-5942-4711-BA18-60383271ADED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This message has gone to multiple mailing lists; our apologies if you = receive it more than once. =20 Registration is now open and hotel rooms may be booked for CalConnect = XXXVIII Irvine, California, February 13-17, 2017, hosted by the = University of California, Irvine . The CalConnect XXXVIII web page is located at = https://www.calconnect.org/events/calconnect-xxxviii-february-13-17-2017 = = and contains hotel information and booking, airport and transfer = information, meeting venue, international travel information, etc. =20 The meeting venue is the UCI Conference Center, located in the Student = Center = building. It is within a few miles of the = conference hotel. The Conference Hotel is the Hotel Irvine = which is also within a few miles of the = nearest airport, Johne Wayne Airport (SNA).=20 You may book the Conference Hotel via a web page link noted on the event = web page, or via a telephone call or e-mail. We are offered a special = UCI rate of $153 for most nights (Friday and Saturday are $119), which = includes breakfast. =20 The Interoperability Test Event and Developers Forum will take place on = our usual schedule beginning Monday morning and going through Wednesday = noon. The Conference will begin Wednesday after lunch and run through = Friday afternoon. =20 We will be posting schedules and agenda as soon as possible on the event = web page, and expect that they may evolve over time.=20 Registration information is at = https://www.calconnect.org/events/event-registration-payment = and is = linked from the event web page. Note that this is the first event with = the new event fees announced last summer and at the Dresden event. As = noted at the time, the conference fees had remained essentially = unchanged since 2005 while the costs associated with the events = continued to rise until the fees no long covered the cost of the event. On remote access: We may be able to allow remote access for the Test = Event via Slack and etherpads. We will not attempt to offer remote = attendance at the conference. =20 As always, please let me know if you have any questions. =20 See you in Irvine, California! Dave Thewlis -- Dave Thewlis, Executive Director CalConnect - The Calendaring and Scheduling Consortium +1 707 840 9391 voice | +1 707 498 2238 mobile | +1 415 946 3454 fax http://www.calconnect.org | = Dave.Thewlis@calconnect.org _______________________________________________ calconnect-l mailing list calconnect-l@lists.calconnect.org http://lists.calconnect.org/listinfo.cgi/calconnect-l-calconnect.org --Apple-Mail=_4EA1978D-5942-4711-BA18-60383271ADED Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
This message has gone to multiple mailing lists; our = apologies if you receive it more than once.  

Registration is now open and hotel rooms may be = booked for CalConnect XXXVIII Irvine, California, February 13-17, 2017, = hosted by the University of California, Irvine.

The CalConnect XXXVIII = web page is located at https://www.calconnect.org/events/calconnect-xxxviii-february-1= 3-17-2017 and contains hotel information and booking, airport = and transfer information, meeting venue, international travel = information, etc.  

The  meeting venue is the UCI Conference Center, located = in the Student = Center building.  It is within a few miles of the = conference hotel. The Conference Hotel is the Hotel Irvine  = which is also within a few miles of the nearest airport, Johne Wayne = Airport (SNA). 

You may book the Conference Hotel via a web page link noted = on the event web page, or via a telephone call or e-mail. We are offered = a special UCI rate of $153 for most nights (Friday and Saturday are = $119), which includes breakfast.  

The Interoperability Test Event and = Developers Forum will take place on our usual schedule beginning Monday = morning and going through Wednesday noon.  The Conference will = begin Wednesday after lunch and run through Friday afternoon. =  

We will = be posting schedules and agenda as soon as possible on the event web = page, and expect that they may evolve over time. 

Registration information is at https://www.calconnect.org/events/event-registration-payment and is linked from the event web page.  Note that this is = the first event with the new event fees announced last summer and at the = Dresden event.  As noted at the time, the conference fees had = remained essentially unchanged since 2005 while the costs associated = with the events continued to rise until the fees no long covered the = cost of the event.

On remote access:  We may be able to = allow remote access for the Test Event via  Slack and etherpads. =  We will not attempt to offer remote attendance at the conference. =  

As = always, please let me know if you have any questions.  

See you in Irvine, = California!

Dave= Thewlis


--
Dave Thewlis, Executive = Director
CalConnect - The = Calendaring and Scheduling Consortium
+1 707 = 840 9391 voice | +1 707 498 2238 mobile | +1 415 946 3454 fax
http://www.calconnect.org | Dave.Thewlis@calconnect.org


_________________________________= ______________
calconnect-l mailing list
calconnect-l@lists.calconnect.org
http://lists.calconnect.org/listinfo.cgi/calconnect-l-calconnec= t.org
= --Apple-Mail=_4EA1978D-5942-4711-BA18-60383271ADED-- From nobody Tue Nov 22 06:32:52 2016 Return-Path: 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 ; 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 ; 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 ; Tue, 22 Nov 2016 06:32:43 -0800 (PST) Received: by mail-it0-x22f.google.com with SMTP id j191so13031887ita.1 for ; 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: <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 Date: Tue, 22 Nov 2016 09:32:42 -0500 X-Google-Sender-Auth: KAbON6NxM6rYpKRxejrmDli05O8 Message-ID: To: Ken Murchison Content-Type: multipart/alternative; boundary=001a11445368304c450541e4a5b4 Archived-At: Cc: "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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 14:32:48 -0000 --001a11445368304c450541e4a5b4 Content-Type: text/plain; charset=UTF-8 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 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 > --001a11445368304c450541e4a5b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Looks to me that issues have b= een at least partly solved... Do we think we have received sufficient input= s to have a 01 version ?

Yours,
Daniel

On Wed, Oct 19,= 2016 at 3:33 PM, Ken Murchison <murch@andrew.cmu.edu> wr= ote:
OK, understood.=C2=A0 If future draf= ts will be using such a construct, we might as well introduce it in this dr= aft.



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?=C2=A0 Do you have an example in mind that<= br> you could flesh out?

So this is from https://tools.ietf.org/html/d= raft-apthorp-ical-tasks-01


3.4.2. Relating comments to status

=C2=A0 =C2=A0The GROUP parameter is used with the STATUS or ATTENDEE proper= ties to
=C2=A0 =C2=A0relate an associated COMMENT property. The COMMENT property ca= n then
=C2=A0 =C2=A0be used to include additional human readable information about= why
=C2=A0 =C2=A0the associated STATUS or ATTENDEE property changed.

STATUS;REASON=3D"http://example.com/reason/delive= ry-failed";SUBSTATE
=C2=A0 =C2=A0 =C2=A0 =C2=A0=3DERROR;MODIFIED=3D20130212T120000Z;GROUP= =3DG1:FAILED
=C2=A0 =C2=A0 =C2=A0 COMMENT;MODIFIED=3D20130226T110451Z;GROUP=3DG1:Br= eakdown

ATTENDEE;PARTSTAT=3DFAILED;MODIFIED=3D20130226T1104510Z;GROUP=3DG= 2:
=C2=A0 =C2=A0 =C2=A0 =C2=A0REASON=3D"http://example.com= /reason/van-break-down":mailto:
=C2=A0 =C2=A0 =C2=A0 =C2=A0xxx@example.com
=C2=A0 =C2=A0 =C2=A0 COMMENT;MODIFIED=3D20130226T110451Z;GROUP=3DG2:Pu= ncture

(An aside - I think the example is faulty - a ":" wheer there sho= uld 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 approa= ch of putting all that inside a component

Inventing one...

BEGIN VATTENDEE
ATTENDEE:PARTSTAT=3DFAILED;MODIFIED=3D20130226T1104510Z:xxx@example= .com
REASON=3D"http://example.com/reason/van-break-down= "
COMMENT;MODIFIED=3D20130226T110451Z: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 assoc= iate if we made it a component

_______________________________________________
calsify mailing list
calsify@ietf.org<= br> https://www.ietf.org/mailman/listinfo/calsify<= br>

--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

_______________________________________________
calsify mailing list
calsify@ietf.org<= br> https://www.ietf.org/mailman/listinfo/calsify<= br>

--001a11445368304c450541e4a5b4-- From nobody Tue Nov 22 14:33:59 2016 Return-Path: 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 6F85412949D for ; Tue, 22 Nov 2016 14:33:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.399 X-Spam-Level: X-Spam-Status: No, score=-2.399 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, 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 Xp--oXM7wcb4 for ; Tue, 22 Nov 2016 14:33:56 -0800 (PST) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 6FFEC129412 for ; Tue, 22 Nov 2016 14:33:56 -0800 (PST) Received: by mail-io0-x22c.google.com with SMTP id a124so13106260ioe.2 for ; Tue, 22 Nov 2016 14:33:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to; bh=mMCQwR19wI2Pn2xj1dJJAumoQYhjAnTSu2+R8vamYY8=; b=slSZhApvvo1hgMHmdJ6yKlKR7j6oMm40ubGI/34C5kIV8vZNC1uu+8txf3U8vrDTxO op455ViNxEHEoaR9CbxmXkRQS/LnpVo+urYZohA2AM1Tr0/jTRWGZ6fBVoGJ2nlHd8qZ 1XSTsOjAzjVY8jxGqzCIEsiGvRqj5vqEUN1TzK90rBokjAonXr+82Ahxf9/fY6/r9yqC qSIBmCrGGsr/8IhgcfZYuxzpD6kQV7YFA14DWtepFA+XsHsTKm+S5GdfgZzPs4TpQipy G1Tgst83VjFF/uYuWzawBXUW7hy8gFuPAavpOYHrAb9GeNOqQZV0omQw7+abCJBStGkQ MY+g== 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:from:date:message-id:subject :to; bh=mMCQwR19wI2Pn2xj1dJJAumoQYhjAnTSu2+R8vamYY8=; b=lYUrNBZxS8YZnOT2ieRi+OosYNo93XHjkb0j7cgHZ+1Axkjh9Lz40XVHWACLFGRX3+ 2eJqEg5PMHs6dJ5Q45FsTfArogmaM4HWgySsCs725rFpmsIlBS4BD43C7AOn3J/RQL5S PQA5fxhF4+hdHZGELjyGpMQkDEe58+gnreVCLCCUjHPc5Y64N25s3z4MWI07vPKzFPtJ GVm5mJVw70lMKkHkWf3pYCB100umt3IC62MDwd0EjaGBBPFjp22rO90eITFGhowZQyu1 7cHN7w5sHAKNl0n8/1f/WT60T02Bs7RiUML+iVuxAP9uk92dMuLwE4AYjtg8Tf6vTlfe Bpdw== X-Gm-Message-State: AKaTC01jjXao143p9ETRjCrY1Tmm8BFYq3WZsa6axL4J+U32aVaJxHymXIb3Ncm4POEEJTJGklsOAxqHdmBHaw== X-Received: by 10.36.181.9 with SMTP id v9mr4571733ite.48.1479854035337; Tue, 22 Nov 2016 14:33:55 -0800 (PST) MIME-Version: 1.0 Sender: mglt.ietf@gmail.com Received: by 10.107.32.10 with HTTP; Tue, 22 Nov 2016 14:33:54 -0800 (PST) From: Daniel Migault Date: Tue, 22 Nov 2016 17:33:54 -0500 X-Google-Sender-Auth: xsMHCYwGGTiL-aLfnoPS17IGBn4 Message-ID: To: calsify@ietf.org Content-Type: multipart/alternative; boundary=f403045d99161885350541eb5e64 Archived-At: Subject: [calsify] Fwd: NomCom 2016-2017: LastCall for Feedback X-BeenThere: calsify@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 22:33:58 -0000 --f403045d99161885350541eb5e64 Content-Type: text/plain; charset=UTF-8 Hi, You are more than welcome to provide feedback for the current Nominees! Yours, Daniel -------- Forwarded Message -------- Subject: NomCom 2016-2017: LastCall for Feedback Date: Tue, 22 Nov 2016 10:38:07 -0800 From: NomCom Chair 2016 Reply-To: ietf@ietf.org To: IETF Announcement List CC: ietf@ietf.org Just a reminder that feedback for the current Nominees for IETF and IAB leadership is due by 23:59 UTC on Thursday, November 24, 2016. You can view the list of nominees and enter feedback via the datatracker: https://datatracker.ietf.org/nomcom/2016/feedback/ or you can provide your input by sending email to: nomcom-2016 @ ietf.org You can also send general feedback about Areas, the IESG, The IAB, and the IAOC to the same email address. The NomCom is particularly interested in your feedback on the IAOC and the current nominees given the discussion of IASA 2.0 as outlined in plenary at IETF 97. We would also like to encourage feedback on all of the nominees. Please take a few moments to comment on the full range of nominees in areas where you are active. We have good responses for some but not all of our pool and would appreciate additional input. Lucy Lynch NomCom Chair 2016-2017 llynch @ civil-tongue.net --f403045d99161885350541eb5e64 Content-Type: text/html; charset=UTF-8
Hi,

You are more than welcome to provide feedback for the current Nominees!

Yours,

Daniel
-------- Forwarded Message --------
Subject: NomCom 2016-2017: LastCall for Feedback
Date: Tue, 22 Nov 2016 10:38:07 -0800
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
Reply-To: ietf@ietf.org
To: IETF Announcement List <ietf-announce@ietf.org>
CC: ietf@ietf.org

Just a reminder that feedback for the current Nominees for IETF and IAB leadership is due by 23:59 UTC on Thursday, November 24, 2016.

You can view the list of nominees and enter feedback via the datatracker:

https://datatracker.ietf.org/nomcom/2016/feedback/

or you can provide your input by sending email to:

nomcom-2016 @ ietf.org

You can also send general feedback about Areas, the IESG, The IAB, and
the IAOC to the same email address.

The NomCom is particularly interested in your feedback on the IAOC and the current nominees given the discussion of IASA 2.0 as outlined in
plenary at IETF 97. We would also like to encourage feedback on all of
the nominees. Please take a few moments to comment on the full range
of nominees in areas where you are active. We have good responses for some but not all of our pool and would appreciate additional input.

Lucy Lynch
NomCom Chair 2016-2017
llynch @ civil-tongue.net


--f403045d99161885350541eb5e64--