
From nobody Mon Jun  9 19:07:04 2014
Return-Path: <alfiej@fastmail.fm>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B931A032E for <calsify@ietfa.amsl.com>; Mon,  9 Jun 2014 19:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 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, 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 pMs0P3Oasl6w for <calsify@ietfa.amsl.com>; Mon,  9 Jun 2014 19:07:00 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 118DA1A0338 for <calsify@ietf.org>; Mon,  9 Jun 2014 19:06:59 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 53C3F20874 for <calsify@ietf.org>; Mon,  9 Jun 2014 22:06:52 -0400 (EDT)
Received: from betaweb1 ([10.202.2.10]) by compute3.internal (MEProxy); Mon, 09 Jun 2014 22:06:52 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:reply-to:date; s=mesmtp; bh=j5UpPdAEc9uANr zkY0zWkjYYZiI=; b=lad3DEGsD5vlUByAxjRrzucGoKq4RQiZKiBSS+MkoeLZ0T m6msRSsUtvXPSxF5NvaYuttiggqxT82Qql+DtYBtP+Q56xNWvwVw4VcL9GYA95cn ReCYipkiaf0lRJx+TM5HB2dqrZBbwTCDzaoDNOcnf8c3+A1dI/oqRtCxwzlxo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:reply-to:date; s=smtpout; bh=j5UpPdAEc9uANrzkY0zWkjYYZiI=; b=UEmC2JxKaVEgbXr/w Xhgjn9eOSOcT9jgSlybTPPSWIFDZ4JHJXmOV9PSvZuedWu/ha5PvIayCs8gMOTiI 3wj/494Dqn1Sk5bSAVTKqJBR8uJ2/1+KYCPOmrk0QFGqYcn0pg5oYxPP1pQ2VJbb XHbEa2ZKgCKzUufO94BmP+x7qA=
Received: by betaweb1.nyi.mail.srv.osa (Postfix, from userid 99) id 27D2E7400CA; Mon,  9 Jun 2014 22:06:52 -0400 (EDT)
Message-Id: <1402366012.26517.126967005.5C301572@webmail.messagingengine.com>
X-Sasl-Enc: QdltSZIkPa6QcaSbTvOCRUaPWlVJ7dcPS9cOJGZ8uyZC 1402366012
From: Alfie John <alfiej@fastmail.fm>
To: calsify@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
Date: Tue, 10 Jun 2014 14:06:52 +1200
Archived-At: http://mailarchive.ietf.org/arch/msg/calsify/OOtAinAea6zDEDmhW-MPxuobt7c
Subject: [calsify] Proposal for new (SEQUENCE and DTSTAMP) ATTENDEE property parameters
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: alfiej@fastmail.fm
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 10 Jun 2014 02:07:02 -0000

Hi guys,

As the ATTENDEE property is already storing the attendee's participation
status via the PROPSTAT property parameter, I thought it would also make
sense to store the participation status' SEQUENCE and DTSTAMP here as
well. This makes sense (to me anyway) as RFC 5546 2.1.5 says:

  "Furthermore, for each "ATTENDEE" property of a component, "Organizer"
  CUAs will need to persist the "SEQUENCE" and "DTSTAMP" property values
  associated with the "Attendee's" last response, so that any earlier
  responses from an "Attendee" that are received out of order (e.g., due
  to a delay in the transport) can be correctly discarded."

e.g:
ATTENDEE;SEQUENCE=42;DTSTAMP=20140610T120600Z;PARTSTAT=ACCEPTED:mailto:alfiej@fastmail.fm

Thoughts?

Alfie

-- 
  Alfie John
  alfiej@fastmail.fm


From nobody Tue Jun 10 07:07:34 2014
Return-Path: <bernard.desruisseaux@oracle.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20E7C1B27A9 for <calsify@ietfa.amsl.com>; Tue, 10 Jun 2014 07:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 rZulqyM81uSs for <calsify@ietfa.amsl.com>; Tue, 10 Jun 2014 07:07:18 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 803DC1B27A8 for <calsify@ietf.org>; Tue, 10 Jun 2014 07:07:18 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s5AE6uMv005825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 10 Jun 2014 14:06:56 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s5AE6tfe002690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Jun 2014 14:06:55 GMT
Received: from abhmp0015.oracle.com (abhmp0015.oracle.com [141.146.116.21]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s5AE6s3a010409; Tue, 10 Jun 2014 14:06:54 GMT
Received: from [10.156.45.76] (/10.156.45.76) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 10 Jun 2014 07:06:54 -0700
Message-ID: <539710FD.1090806@oracle.com>
Date: Tue, 10 Jun 2014 10:06:53 -0400
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: alfiej@fastmail.fm, calsify@ietf.org
References: <1402366012.26517.126967005.5C301572@webmail.messagingengine.com>
In-Reply-To: <1402366012.26517.126967005.5C301572@webmail.messagingengine.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Archived-At: http://mailarchive.ietf.org/arch/msg/calsify/1GWagUWrznEEy7H9slsYVcuGVtk
Subject: Re: [calsify] Proposal for new (SEQUENCE and DTSTAMP) ATTENDEE property parameters
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 10 Jun 2014 14:07:21 -0000

Hi Alfie,

Prior to the redesign of CalDAV Scheduling (draft -05) two iCalendar 
property parameters had been proposed for this purpose.

See: http://tools.ietf.org/html/draft-desruisseaux-caldav-sched-04#section-7

In a context (e.g., CalDAV Schedule post drafit-05) where the processing 
of incoming scheduling messages is handled by a server (i.e., 
centralized) there is no need to expose that information to the clients 
in the calendar object resources.

In a context (e.g., iMIP) where the processing of incoming scheduling 
messages is handled by clients (perhaps multiple clients) there would be 
a need to have this information persisted in the calendar object resources.

Cheers,
Bernard

On 09/06/2014 10:06 PM, Alfie John wrote:
> Hi guys,
>
> As the ATTENDEE property is already storing the attendee's participation
> status via the PROPSTAT property parameter, I thought it would also make
> sense to store the participation status' SEQUENCE and DTSTAMP here as
> well. This makes sense (to me anyway) as RFC 5546 2.1.5 says:
>
>    "Furthermore, for each "ATTENDEE" property of a component, "Organizer"
>    CUAs will need to persist the "SEQUENCE" and "DTSTAMP" property values
>    associated with the "Attendee's" last response, so that any earlier
>    responses from an "Attendee" that are received out of order (e.g., due
>    to a delay in the transport) can be correctly discarded."
>
> e.g:
> ATTENDEE;SEQUENCE=42;DTSTAMP=20140610T120600Z;PARTSTAT=ACCEPTED:mailto:alfiej@fastmail.fm
>
> Thoughts?
>
> Alfie
>


From nobody Fri Jun 20 09:08:20 2014
Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 226D61B281D; Fri, 20 Jun 2014 09:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 Q1WQlJZtxrSc; Fri, 20 Jun 2014 09:08:13 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84E4A1B2857; Fri, 20 Jun 2014 09:07:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 354206A26A3F; Fri, 20 Jun 2014 12:07:48 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2zR6WK-pJzuL; Fri, 20 Jun 2014 12:07:45 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 00DB36A26A2D; Fri, 20 Jun 2014 12:07:43 -0400 (EDT)
Date: Fri, 20 Jun 2014 12:07:38 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: IETF-Calsify <calsify@ietf.org>, IETF-CalDAV <caldav@ietf.org>
Message-ID: <DF36F5800D58329CED9A0F92@caldav.corp.apple.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========290457C43E0F7AC934B5=========="
Archived-At: http://mailarchive.ietf.org/arch/msg/calsify/elfSgOGnjqSJ-Kg1sSMIq4bapYI
Cc: TC-Timezone <tc-timezone-l@calconnect.org>, CalConnect <calconnect-l@calconnect.org>
Subject: [calsify] Proposed working group: Timezone Data Distribution Service (tzdist) (fwd)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 20 Jun 2014 16:08:18 -0000

--==========290457C43E0F7AC934B5==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1099

Hi,
This is likely of interest to all iCalendar/CalDAV etc folks. Discussion of 
the proposed working group charter should initially take place on the 
apps-discuss list.

------------ Forwarded Message -----------
Date: June 20, 2014 at 11:06:51 AM -0400
From: Barry Leiba <barryleiba@computer.org>
To: Apps Discuss <apps-discuss@ietf.org>
cc: Cyrus Daboo <cyrus@daboo.name>
Subject: Proposed working group: Timezone Data Distribution Service (tzdist)

Cyrus Daboo has proposed a new working group in the Applications Area,
and I'm initiating charter discussion on it:

https://datatracker.ietf.org/doc/charter-ietf-tzdist/

We'll have the charter discussion here on apps-discuss.  Assuming a
working group comes out of this, we'll create a new mailing list for
the actual work, once the charter is done.

Comments on this charter are welcome.  I expect to put it on the 10
July IESG telechat for initial approval, after which it will go out
for IETF and external review.  So, comments here by 4 July, please.

Barry, Applications AD

---------- End Forwarded Message ----------



-- 
Cyrus Daboo

--==========290457C43E0F7AC934B5==========
Content-Type: message/rfc822;
 name="Proposed working group: Timezone Data Distribution Service (tzdist)"

Return-Path: <barryleiba@gmail.com>
Delivered-To: cyrusdaboo@daboo.name
Received: from localhost (localhost [127.0.0.1])
	by daboo.name (Postfix) with ESMTP id DFF956A256FA
	for <cyrusdaboo@daboo.name>; Fri, 20 Jun 2014 11:07:03 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Authentication-Results: daboo.name (amavisd-new); dkim=pass (2048-bit key)
	header.d=gmail.com
Received: from daboo.name ([127.0.0.1])
	by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9jJwFwDJB3pw for <cyrusdaboo@daboo.name>;
	Fri, 20 Jun 2014 11:06:59 -0400 (EDT)
Received: from mail-la0-f42.google.com (mail-la0-f42.google.com [209.85.215.42])
	by daboo.name (Postfix) with ESMTPS id 98D956A256EB
	for <cyrus@daboo.name>; Fri, 20 Jun 2014 11:06:59 -0400 (EDT)
Received: by mail-la0-f42.google.com with SMTP id pn19so2489720lab.15
        for <cyrus@daboo.name>; Fri, 20 Jun 2014 08:06:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:date:message-id:subject:from:to:cc:content-type;
        bh=XDzvFCuoU27s137FK8+dY8hCjN1EvE8aMFtWXOA2yqc=;
        b=CoeL8W3hV0oGkPSyR46Q/QgoasUXyepCExI0k1qEqW80azkvQWgQjI2FJERsqa+HK2
         BDsNI/gTf7EOZtJ1V2f8+Yu36y4TWsqQdWoSFHQUa+IruGgnCB6PiUK1DMg1+yQoXTSj
         ON9yoqR0a0ZHJMHhoCmEwiVaVvFteqee2qa5ij+ur11qD6ant5psBHg5kHDUlPNeXu9w
         NyLFiW1r1h4A5GPDu2GPZuYa6E/n7qsuZAoID2yoDdHWaYNd8PgFU5+Hm4Xr6NadTMvf
         mODTIcQpqEhIaKWK2EshQOPMmEOBInQ2ojyXxcBisIi+OF1ND9n+9DcW6uuwW3W8ePab
         IG0g==
MIME-Version: 1.0
X-Received: by 10.112.157.130 with SMTP id wm2mr2806803lbb.38.1403276811102;
 Fri, 20 Jun 2014 08:06:51 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.152.104.80 with HTTP; Fri, 20 Jun 2014 08:06:51 -0700 (PDT)
Date: Fri, 20 Jun 2014 11:06:51 -0400
X-Google-Sender-Auth: mizEke5InA6EwPkrtJl6UWhFTBs
Message-ID: <CALaySJ+EdD1ND1u=batWL+dhMufKsixkdB-VNps0JV_02KuuAw@mail.gmail.com>
Subject: Proposed working group: Timezone Data Distribution Service (tzdist)
From: Barry Leiba <barryleiba@computer.org>
To: Apps Discuss <apps-discuss@ietf.org>
Cc: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset=ISO-8859-1

Cyrus Daboo has proposed a new working group in the Applications Area,
and I'm initiating charter discussion on it:

https://datatracker.ietf.org/doc/charter-ietf-tzdist/

We'll have the charter discussion here on apps-discuss.  Assuming a
working group comes out of this, we'll create a new mailing list for
the actual work, once the charter is done.

Comments on this charter are welcome.  I expect to put it on the 10
July IESG telechat for initial approval, after which it will go out
for IETF and external review.  So, comments here by 4 July, please.

Barry, Applications AD

--==========290457C43E0F7AC934B5==========--


From nobody Fri Jun 20 13:27:15 2014
Return-Path: <timhare@comcast.net>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F089E1B290A for <calsify@ietfa.amsl.com>; Fri, 20 Jun 2014 13:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 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, RP_MATCHES_RCVD=-0.651, 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 q3KeViDVptgg for <calsify@ietfa.amsl.com>; Fri, 20 Jun 2014 13:27:07 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:17]) by ietfa.amsl.com (Postfix) with ESMTP id A82A11B2909 for <calsify@ietf.org>; Fri, 20 Jun 2014 13:27:07 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta10.westchester.pa.mail.comcast.net with comcast id GkMT1o0081c6gX85AkT7JY; Fri, 20 Jun 2014 20:27:07 +0000
Received: from THARE ([156.75.186.150]) by omta23.westchester.pa.mail.comcast.net with comcast id GkSp1o00d3F7N4C3jkSsvN; Fri, 20 Jun 2014 20:27:05 +0000
From: "Tim Hare" <TimHare@comcast.net>
To: "'Cyrus Daboo'" <cyrus@daboo.name>, "'IETF-Calsify'" <calsify@ietf.org>, "'IETF-CalDAV'" <caldav@ietf.org>
References: <DF36F5800D58329CED9A0F92@caldav.corp.apple.com>
In-Reply-To: <DF36F5800D58329CED9A0F92@caldav.corp.apple.com>
Date: Fri, 20 Jun 2014 16:26:22 -0400
Message-ID: <009f01cf8cc5$efebd5d0$cfc38170$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac+ModzbQ3UCijKFS7+FFw8ekITlFAAIyLSg
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1403296027; bh=zlgTEscJVYdMD7EzTwm1L2WCc4PR4rRbC8NMRuQS4Jk=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=s8DOhcOhHy/1hEzDZ/6R/veMuj1kF18VSR3euh+aP0MR/KLXiXu4+0ftguMqeU4cY btL0dqFFM4T5Y0oyXDnBcBQbYbFsdoR+dKjx4gJDGUL4fLK29ejPpUssx4gwurqJ06 IRvg+icUGZoI2Ls+4PS572e9spMn1EMTO4Jt0TwhXbHQ6LDx6Tqq8yvwybkoPQOxLs ZNooMG4MpzImpBXUQ/I2I7XRjuM4vWCt7DgiSQVbJId35VBOyfMiK+Nt9t7O35MLww hIE595pgVLxXXUUh5sNGF3n+WjUOMxvja3WOA6c4AiQV4jlGe8LHvmVVM8PtN5ugtQ tvzvH7juoUojA==
Archived-At: http://mailarchive.ietf.org/arch/msg/calsify/vUtfJyE7VDYOK1y6qHO2S4xefLo
Cc: 'TC-Timezone' <tc-timezone-l@calconnect.org>, 'CalConnect' <calconnect-l@calconnect.org>
Subject: Re: [calsify] [caldav] Proposed working group: Timezone Data Distribution Service (tzdist) (fwd)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 20 Jun 2014 20:27:10 -0000

I think this has long been needed.  One thought re: scaling - could the
existing NTP/SNTP hierarchy be used to also hold and distribute the timezone
data? That way the time servers also could be the timezone servers;  the
data changes fairly infrequently but when it does it is with short notice,
it would be nice to have it spread out through a tree structure fairly
quickly.  I don't think the update would cause significant load to the
servers, and the hierarchical nature of NTP/SNTP would, it seems to me, make
sure queries are handled as locally as possible.

Tim Hare
Interested Bystander, Non-Inc.

-----Original Message-----
From: caldav [mailto:caldav-bounces@ietf.org] On Behalf Of Cyrus Daboo
Sent: Friday, June 20, 2014 12:08 PM
To: IETF-Calsify; IETF-CalDAV
Cc: TC-Timezone; CalConnect
Subject: [caldav] Proposed working group: Timezone Data Distribution Service
(tzdist) (fwd)

Hi,
This is likely of interest to all iCalendar/CalDAV etc folks. Discussion of
the proposed working group charter should initially take place on the
apps-discuss list.

------------ Forwarded Message -----------
Date: June 20, 2014 at 11:06:51 AM -0400
From: Barry Leiba <barryleiba@computer.org>
To: Apps Discuss <apps-discuss@ietf.org>
cc: Cyrus Daboo <cyrus@daboo.name>
Subject: Proposed working group: Timezone Data Distribution Service (tzdist)

Cyrus Daboo has proposed a new working group in the Applications Area, and
I'm initiating charter discussion on it:

https://datatracker.ietf.org/doc/charter-ietf-tzdist/

We'll have the charter discussion here on apps-discuss.  Assuming a working
group comes out of this, we'll create a new mailing list for the actual
work, once the charter is done.

Comments on this charter are welcome.  I expect to put it on the 10 July
IESG telechat for initial approval, after which it will go out for IETF and
external review.  So, comments here by 4 July, please.

Barry, Applications AD

---------- End Forwarded Message ----------



--
Cyrus Daboo

