
From mikeadouglass@gmail.com  Sat Nov  3 22:26:00 2012
Return-Path: <mikeadouglass@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 7326621F960C; Sat,  3 Nov 2012 22:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.598
X-Spam-Level: 
X-Spam-Status: No, score=-5.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ugk8LfrTHtgF; Sat,  3 Nov 2012 22:25:59 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 73B7221F9481; Sat,  3 Nov 2012 22:25:59 -0700 (PDT)
Received: by mail-qa0-f44.google.com with SMTP id 25so1600867qao.10 for <multiple recipients>; Sat, 03 Nov 2012 22:25:59 -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:subject :content-type; bh=NtS+ohssWJyvl/VrBWIXAEMMznEQhtgauu6C3xJ2rf0=; b=w5hvAP0xPTJgyCNA8zTbehBEysECNiTjeB0rhl4bHIHdE2SxSRxkbTTXiGXjUmLJR9 OzzY8thoaXaVxHDNnCjZemS2ZB7jTPrLfYpORsRzQAWsZn03BVmEwxO2aN8CfZsDq7T5 DOhehmEwJbK90728RuKd1AogrndXvrP6mzJ4QP09Fxi6A3jnkuQdze6E6c+dHqqu2/Wy 9Sw1BQK5RhpinDTk0PgHHN2BGSHqvx2273FAfcZTPsisBXVNAO19xZV26VE3yEhy0EpW uw0ub8p39o4VdSTs6uM2TvcpepFFTOSgHPAnfL+zWcjjSDp7/SdUdFAPL2is7JLYVFtY lkdw==
Received: by 10.49.58.212 with SMTP id t20mr10729521qeq.26.1352006758874; Sat, 03 Nov 2012 22:25:58 -0700 (PDT)
Received: from [192.168.1.117] (cpe-74-76-210-192.nycap.res.rr.com. [74.76.210.192]) by mx.google.com with ESMTPS id i9sm2555143qak.3.2012.11.03.22.25.57 (version=SSLv3 cipher=OTHER); Sat, 03 Nov 2012 22:25:58 -0700 (PDT)
Message-ID: <5095FC65.2080803@gmail.com>
Date: Sun, 04 Nov 2012 01:25:57 -0400
From: Mike Douglass <mikeadouglass@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: IETF Calsify <calsify@ietf.org>, CardDAV <vcarddav@ietf.org>
Content-Type: multipart/alternative; boundary="------------070204090402090402030604"
Subject: [calsify] Proposal for new VCARD OBJECTCLASS property
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 04 Nov 2012 05:26:00 -0000

This is a multi-part message in MIME format.
--------------070204090402090402030604
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

During discussions on the new vcard resource draft 
http://tools.ietf.org/html/draft-cal-resource-vcard-01 it seemed that we 
had significant overlap with the device specification

http://tools.ietf.org/html/draft-salgueiro-vcarddav-kind-device-02

  and also applications:

RFC6473

We also realized we have a subset of properties which could apply to any 
schedulable entity, e.g. autoschedule, booking window, calendar user 
addresss (cua) and so on.

We propose a new, multiply occurring property: OBJECTCLASS.

A vcard containing one or more occurrences of this property MUST conform 
to the related specification. So for example we might have

OBJECTCLASS: SCHEDULABLE

The appearance of this property and value requires that the cua be 
present but it also allows us to apply appropriate defaults when a 
property is absent. For example, our resource draft states that the 
absence of the AUTOSCHEDULE property implies that invitations are 
automatically accepted.

A further advantage is that it seems to facilitate mapping from ldap to 
vcard. There are many widely used ldap object classes which it would be 
useful to make visible in vcard.

It enables authors of specifications to worry less about areas in which 
they are not expert. Any entity which is schedulable can be made so 
simply by adding OBJECTCLASS: SCHEDULABLE to the entity (and any 
appropriate properties).

It also avoids trying to resolve strict hierarchies of 'thing'. A device 
is a resource but so is a room and both may or may not be schedulable.

This proposal does not appear to conflict with the current 
specifications. It does however appear to offer a way to enhance the 
usability of vcards and provide consumers of the information with the 
assurance that it was generated correctly.


-- 

Mike Douglass douglm@rpi.edu
Senior Systems Programmer
Communication & Collaboration Technologies      518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180


--------------070204090402090402030604
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-text-flowed" style="font-size: 14px;"
      lang="x-western">During discussions on the new vcard resource
      draft <a class="moz-txt-link-freetext"
        href="http://tools.ietf.org/html/draft-cal-resource-vcard-01">http://tools.ietf.org/html/draft-cal-resource-vcard-01</a>
      it seemed that we had significant overlap with the device
      specification
      <br>
      <br>
      <a class="moz-txt-link-freetext"
href="http://tools.ietf.org/html/draft-salgueiro-vcarddav-kind-device-02">http://tools.ietf.org/html/draft-salgueiro-vcarddav-kind-device-02</a>
      <br>
      <br>
      &nbsp;and also applications:
      <br>
      <br>
      RFC6473
      <br>
      <br>
      We also realized we have a subset of properties which could apply
      to any schedulable entity, e.g. autoschedule, booking window,
      calendar user addresss (cua) and so on.
      <br>
      <br>
      We propose a new, multiply occurring property: OBJECTCLASS.
      <br>
      <br>
      A vcard containing one or more occurrences of this property MUST
      conform to the related specification. So for example we might have
      <br>
      <br>
      OBJECTCLASS: SCHEDULABLE
      <br>
      <br>
      The appearance of this property and value requires that the cua be
      present but it also allows us to apply appropriate defaults when a
      property is absent. For example, our resource draft states that
      the absence of the AUTOSCHEDULE property implies that invitations
      are automatically accepted.
      <br>
      <br>
      A further advantage is that it seems to facilitate mapping from
      ldap to vcard. There are many widely used ldap object classes
      which it would be useful to make visible in vcard.
      <br>
      <br>
      It enables authors of specifications to worry less about areas in
      which they are not expert. Any entity which is schedulable can be
      made so simply by adding OBJECTCLASS: SCHEDULABLE to the entity
      (and any appropriate properties).
      <br>
      <br>
      It also avoids trying to resolve strict hierarchies of 'thing'. A
      device is a resource but so is a room and both may or may not be
      schedulable.
      <br>
      <br>
      This proposal does not appear to conflict with the current
      specifications. It does however appear to offer a way to enhance
      the usability of vcards and provide consumers of the information
      with the assurance that it was generated correctly.
      <br>
      <br>
      <br>
      <div class="moz-txt-sig"><span class="moz-txt-tag">--&nbsp;<br>
        </span>
        <br>
        Mike Douglass&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
          class="moz-txt-link-abbreviated" href="mailto:douglm@rpi.edu">douglm@rpi.edu</a>
        <br>
        Senior Systems Programmer
        <br>
        Communication &amp; Collaboration Technologies&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 518 276
        6780(voice) 2809
        <br>
        (fax)
        <br>
        Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180
        <br>
        <br>
      </div>
    </div>
  </body>
</html>

--------------070204090402090402030604--

From cyrus@daboo.name  Wed Nov 14 09:24:03 2012
Return-Path: <cyrus@daboo.name>
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 73EFB21F85C4; Wed, 14 Nov 2012 09:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2bQ2EUOlWXW3; Wed, 14 Nov 2012 09:24:03 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id F274721F85A5; Wed, 14 Nov 2012 09:24:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 3120E354FC82; Wed, 14 Nov 2012 12:24:02 -0500 (EST)
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 hUlvfD9DXr2S; Wed, 14 Nov 2012 12:23:56 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 1696C354FC76; Wed, 14 Nov 2012 12:23:55 -0500 (EST)
Date: Wed, 14 Nov 2012 12:23:52 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Calsify <calsify@ietf.org>, VCard <vcarddav@ietf.org>
Message-ID: <7A395F82BDDCFB1F9964AD8C@caldav.corp.apple.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1023
Subject: [calsify] New Version Notification for draft-kewisch-et-al-icalendar-in-json-00.txt (fwd)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 14 Nov 2012 17:24:03 -0000

FYI

------------ Forwarded Message -----------
Date: November 13, 2012 10:08:57 PM -0800
From: internet-drafts@ietf.org
To: mozilla@kewis.ch
cc: cyrus@daboo.name, douglm@rpi.edu
Subject: New Version Notification for 
draft-kewisch-et-al-icalendar-in-json-00.txt


A new version of I-D, draft-kewisch-et-al-icalendar-in-json-00.txt
has been successfully submitted by Philipp Kewisch and posted to the
IETF repository.

Filename:	 draft-kewisch-et-al-icalendar-in-json
Revision:	 00
Title:		 jCal: The JSON format for iCalendar
Creation date:	 2012-11-13
WG ID:		 Individual Submission
Number of pages: 29
URL:
http://www.ietf.org/internet-drafts/draft-kewisch-et-al-icalendar-in-json-0
0.txt Status:
http://datatracker.ietf.org/doc/draft-kewisch-et-al-icalendar-in-json
Htmlized:
http://tools.ietf.org/html/draft-kewisch-et-al-icalendar-in-json-00


Abstract:
   This specification defines "jCal", a JSON format for iCalendar data.





The IETF Secretariat


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



-- 
Cyrus Daboo


From Dave.Thewlis@calconnect.org  Fri Nov 16 12:44:02 2012
Return-Path: <Dave.Thewlis@calconnect.org>
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 89B4821F8ACA; Fri, 16 Nov 2012 12:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.964
X-Spam-Level: 
X-Spam-Status: No, score=-0.964 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MANGLED_NAIL=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q3GWcVxUKJPe; Fri, 16 Nov 2012 12:44:01 -0800 (PST)
Received: from outmail.svwh.net (outmail.svwh.net [67.207.201.11]) by ietfa.amsl.com (Postfix) with ESMTP id 82C7721F8956; Fri, 16 Nov 2012 12:43:58 -0800 (PST)
Received: from newredwood.morsemedia.net (newredwood.morsemedia.net [69.50.246.34]) by outmail.svwh.net (Postfix) with ESMTP id 257D99BCCC9; Fri, 16 Nov 2012 12:43:58 -0800 (PST)
Received: from cdm-75-109-136-191.asbnva.dh.suddenlink.net ([75.109.136.191]:42640 helo=[192.168.0.218]) by newredwood.morsemedia.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <Dave.Thewlis@calconnect.org>) id 1TZSlY-0001Dv-D0; Fri, 16 Nov 2012 12:43:56 -0800
From: Dave Thewlis <Dave.Thewlis@calconnect.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_097594D1-6B92-4965-B447-D8217FD2A6D6"
Date: Fri, 16 Nov 2012 12:43:55 -0800
To: calsify@ietf.org, IETF IETF vcarddav list <vcarddav@ietf.org>, caldav@ietf.org, ischedule list <ischedule@ietf.org>
Message-Id: <D8530408-0DD2-4DB7-82C1-613F1EC28229@calconnect.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-MorseMedia-MailScanner-Information: Please contact the ISP for more information
X-MorseMedia-MailScanner-ID: 1TZSlY-0001Dv-D0
X-MorseMedia-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MorseMedia-MailScanner-SpamCheck: 
X-MorseMedia-MailScanner-From: dave.thewlis@calconnect.org
Subject: [calsify] Registration is now open for CalConnect XXVI, January 28 - February 1, 2013, Santa Clara, California
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2012 20:44:02 -0000

--Apple-Mail=_097594D1-6B92-4965-B447-D8217FD2A6D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This notification is going to several calendaring-related mailing lists, =
which means that you are quite likely to receive it more than once, our =
apologies for the duplications.


Registration is now open for CalConnect XXVI,  January 28 - February 1, =
2013, hosted by Oracle in Santa Clara, California =20

As usual, Monday and Tuesday all day and Wednesday morning will be the =
Interoperability Test Event; Wednesday afternoon, Thursday, and Friday =
will be the CalConnect Roundtable Technical Conference.=20


About CalConnect:

For more information about CalConnect, The Calendaring and Scheduling =
Consortium, please see http://www.calconnect.org.


About CalConnect XXVI

Logistics information for this event may be found at =
http://www.calconnect.org/calconnect26.shtml including travel, =
preliminary hotel, and other planning information.  A general schedule =
is posted, but will be updated nearer to the event with the actual =
session schedule and with topical agendas for the schedule.

The meeting venue is on the Oracle campus at 4040 Palm Drive, Santa =
Clara, California. Hotel information is preliminary as we have not =
selected a conference hotel yet; there are a number of hotels in the =
area and a list provided by Oracle is available on the logistics page =
linked above. =20

I encourage you to register early for this event as well, as early =
registration helps us with event planning and logistics, in addition to =
restaurant reserfvations.  (Please remember that you need not pay when =
you register; if desired you may wait until the event and pay by credit =
card.)


About the Roundtable Technical Conference:

The exact schedule for TC Sessions is not yet fixed but should be =
determined by the beginning of January.  =20

Early registration for the Roundtable will be $350 through 11 January, =
2013, and $395 after that date.  Another reason to register early: you =
won't forget and miss the early registration deadline.  Please note that =
the early registration about applies so long as you register <=3D 11 =
January, even if you don't actually pay until the event. =20


About the Interoperability Test Event:

At this point we are planning testing in the following areas:
CalDAV testing:
access (basic operations of CalDAV)
scheduling
sync report
mobile
managed attachments
sharing
iSchedule:
Server discovery
DKIM security - latest changes for header normalization
Timezone Service Protocol (new JSON spec) and Timezones by Reference
VPOLL initial testing
Autodiscovery protocol
iCalendar richtext properties (and hashing)
iCalendar/iMIP/iTIP testing
jCal, the JSON Format for iCalendar
xCal, the XML Format for iCalendar
CardDAV testing: Sync report, mobile
CalWS-REST and CalWS-SOAP, the web services protocols for iCalendar and =
WS-Calendar
In addition, participants may have other areas they wish to test and we =
will be happy to include them in our planning; the test event =
registration form provides a place to indicate what you want to test.  n =
all cases at least two participating organizations must be interested in =
testing a particular area or scenario to form testing pairs.=20

The information page for the Interoperability Test event is at =
http://www.calconnect.org/iop1301.shtml. =20

Please note that the Interoperability Test Event registration fee for =
non-vendor members is now $350 per person.  Test Event registration fees =
for vendor members and for non-members remain unchanged at $1795 and =
$2795 respectively for the first two participants, and $150 per =
additional participant.


See you in Santa Clara!

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


--Apple-Mail=_097594D1-6B92-4965-B447-D8217FD2A6D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><meta http-equiv=3D"Content-Type" content=3D"text/html=
 charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><i>This notification is going to several calendaring-related =
mailing lists, which means that you are quite likely to receive it more =
than once, our apologies for the =
duplications.</i></div><div><br></div><div><br></div>Registration is now =
open for <font class=3D"Apple-style-span" face=3D"Arial"><b>CalConnect =
XXVI, &nbsp;January 28 - February 1, 2013, hosted by Oracle in Santa =
Clara, California</b></font>&nbsp;&nbsp;<div><br></div><div>As usual, =
Monday and Tuesday all day and Wednesday morning will be the =
Interoperability Test Event; Wednesday afternoon, Thursday, and Friday =
will be the CalConnect Roundtable Technical =
Conference.&nbsp;</div><div><div><div><br></div><div><b =
style=3D"font-family: Arial; "><br></b></div><div><b>About =
CalConnect:</b></div><div><b><br></b></div><div><font =
class=3D"Apple-style-span" face=3D"Arial">For more information about =
CalConnect, The Calendaring and Scheduling Consortium, please =
see&nbsp;</font><a =
href=3D"http://www.calconnect.org">http://www.calconnect.org</a><font =
class=3D"Apple-style-span" face=3D"Arial">.</font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><br></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><br></font></div><div><font =
face=3D"Arial"><b>About CalConnect =
XXVI</b></font></div><div><br></div><div>Logistics information for this =
event may be found at <a =
href=3D"http://www.calconnect.org/calconnect26.shtml">http://www.calconnec=
t.org/calconnect26.shtml</a> including travel, preliminary hotel, and =
other planning information. &nbsp;A general schedule is posted, but will =
be updated nearer to the event with the actual session schedule and with =
topical agendas for the schedule.</div><div><br></div><div>The meeting =
venue is on the Oracle campus at 4040 Palm Drive, Santa Clara, =
California. Hotel information is preliminary as we have not selected a =
conference hotel yet; there are a number of hotels in the area and a =
list provided by Oracle is available on the logistics page linked above. =
&nbsp;</div><div><br></div><div>I encourage you to register early for =
this event as well, as early registration helps us with event planning =
and logistics, in addition to restaurant reserfvations. &nbsp;(Please =
remember that you need not pay when you register; if desired you may =
wait until the event and pay by credit =
card.)</div><div><br></div><div><br></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><b>About the Roundtable =
Technical Conference:</b></font></div><div><font =
class=3D"Apple-style-span" =
face=3D"Arial"><b><br></b></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial">The exact schedule for TC =
Sessions is not yet fixed but should be determined by the beginning of =
January. &nbsp;&nbsp;</font></div><div><font class=3D"Apple-style-span" =
face=3D"Arial"><b><br></b></font></div><div>Early registration for the =
Roundtable will be $350 through 11 January, 2013, and $395 after that =
date. &nbsp;Another reason to register early: you won't forget and miss =
the early registration deadline. <font class=3D"Apple-style-span" =
face=3D"Arial"><i>&nbsp;Please note that the early registration about =
applies so long as you <u>register</u> &lt;=3D 11 January, even if you =
don't actually pay until the event. =
&nbsp;</i></font></div><div><br></div><div><br></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><b>About the Interoperability =
Test Event:</b></font></div><div><br><font face=3D"Arial">At this point =
we are planning testing in the following areas:</font></div><div><ul>
<li>CalDAV testing:
  <ul>
  <li>access (basic operations of CalDAV)</li>
  <li>scheduling</li>
  <li>sync report</li>
  <li>mobile</li>
  <li>managed attachments</li>
  <li>sharing</li>
  </ul>
</li>
<li>iSchedule:
  <ul>
  <li>Server discovery</li>
  <li>DKIM security - latest changes for header normalization</li>
  </ul>
</li>
<li>Timezone Service Protocol (new JSON spec) and Timezones by =
Reference</li>
<li>VPOLL initial testing</li>
<li>Autodiscovery protocol</li>
<li>iCalendar richtext properties (and hashing)</li>
<li>iCalendar/iMIP/iTIP testing</li>
<li>jCal, the JSON Format for iCalendar</li>
<li>xCal, the XML Format for iCalendar</li>
<li>CardDAV testing: Sync report, mobile</li>
<li>CalWS-REST and CalWS-SOAP, the web services protocols for iCalendar =
and WS-Calendar</li></ul><div>In addition, participants may have other =
areas they wish to test and we will be happy to include them in our =
planning; the test event registration form provides a place to indicate =
what you want to test. &nbsp;n all cases at least two participating =
organizations must be interested in testing
a particular area or scenario to form testing =
pairs.&nbsp;</div></div><div><br></div><div>The information page for the =
Interoperability Test event is at <a =
href=3D"http://www.calconnect.org/iop1301.shtml">http://www.calconnect.org=
/iop1301.shtml</a>. &nbsp;</div><div><br></div><div>Please note that the =
Interoperability Test Event registration fee for <font =
class=3D"Apple-style-span" face=3D"Arial"><u>non-vendor =
members</u></font> is now $350 per person. &nbsp;Test Event registration =
fees for <u>vendor members and for non-members</u> remain unchanged at =
$1795 and $2795 respectively for the first two participants, and $150 =
per additional participant.</div><div><br></div><div><br></div><div>See =
you in Santa Clara!</div><div><br></div><div>Dave =
Thewlis</div><div><br></div><div><br></div></div><br><div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>--</div><div><b>Dave =
Thewlis, Executive Director</b></div><div><b>CalConnect - The =
Calendaring and Scheduling Consortium</b></div><div>+1 707 840 9391 =
voice | +1 707 498 2238 mobile | +1 415 946 3454 fax</div><div><a =
href=3D"http://www.calconnect.org">http://www.calconnect.org</a> | <a =
href=3D"mailto:Dave.Thewlis@calconnect.org">Dave.Thewlis@calconnect.org</a=
></div></div>
</div>
<br></div></body></html>=

--Apple-Mail=_097594D1-6B92-4965-B447-D8217FD2A6D6--

From cyrus@daboo.name  Fri Nov 16 13:17:23 2012
Return-Path: <cyrus@daboo.name>
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 C489321F852B; Fri, 16 Nov 2012 13:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.366
X-Spam-Level: 
X-Spam-Status: No, score=-102.366 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENsE6wMkTbAO; Fri, 16 Nov 2012 13:17:23 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8E821F84B2; Fri, 16 Nov 2012 13:17:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 7A347357AC27; Fri, 16 Nov 2012 16:17:22 -0500 (EST)
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 A0p8AekiBJj7; Fri, 16 Nov 2012 16:17:17 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 328BA357AC17; Fri, 16 Nov 2012 16:17:15 -0500 (EST)
Date: Fri, 16 Nov 2012 16:17:12 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Calsify <calsify@ietf.org>, CardDAV <vcarddav@ietf.org>
Message-ID: <FA534C8B88E61DE9CA6DA4A9@caldav.corp.apple.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=631
Subject: [calsify] ID Tracker State Update Notice: <draft-daboo-ical-vcard-parameter-encoding-02.txt> (fwd)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2012 21:17:23 -0000

Hi folks,
The parameter encoding spec is now in IETF Last Call so this is (almost) 
your last chance to review and comment...

------------ Forwarded Message -----------
Date: November 16, 2012 1:13:43 PM -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Subject: ID Tracker State Update Notice: 
<draft-daboo-ical-vcard-parameter-encoding-02.txt>

Last call has been made for draft-daboo-ical-vcard-parameter-encoding and
state has been changed to In Last Call ID Tracker URL:
http://datatracker.ietf.org/doc/draft-daboo-ical-vcard-parameter-encoding/


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



-- 
Cyrus Daboo


From mikeadouglass@gmail.com  Fri Nov 16 13:21:16 2012
Return-Path: <mikeadouglass@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 DC73321F8B06 for <calsify@ietfa.amsl.com>; Fri, 16 Nov 2012 13:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSUWozzqBR0C for <calsify@ietfa.amsl.com>; Fri, 16 Nov 2012 13:21:16 -0800 (PST)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id ACD3121F8AF2 for <calsify@ietf.org>; Fri, 16 Nov 2012 13:21:15 -0800 (PST)
Received: by mail-qa0-f44.google.com with SMTP id c4so3288293qae.10 for <calsify@ietf.org>; Fri, 16 Nov 2012 13:21:15 -0800 (PST)
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:subject:references :in-reply-to:x-forwarded-message-id:content-type; bh=ExY7hMw7morRG9ykr8NzReJqiJF+erXSGuKy5oJB4eE=; b=R1c0y3f4v37Y+1CUGSjoshtYd+LJEa3twxeVBL/lXGQwbrW3xTVw+RwEJrxUVh2fVJ HoiRanQSvhVYFWX9mxO9zw9N3wPJdIK0AKyLVqNdXfdz6sUKGIs+eoAQpB/xUD9dOe1S d/43/dxPw2tybrOPjAvAHAnOqocYZA89bfUZkfP0M0NQUVgrYbUo9MqAmYSfoGhvddCA hU077C1muk36m7l4BjK3OjhmigsnN2yPTbrOjjI2JwMJ8+sSTJb2QX0WzKtdVXOUinf5 zIfb6bYBjYsx4D0u4V8aqqrW8UI51aQsGmylhhWWMWO2cQJA3euSRSxkNqyZqX+n3EKy 1TFA==
Received: by 10.224.189.65 with SMTP id dd1mr5565917qab.79.1353100875025; Fri, 16 Nov 2012 13:21:15 -0800 (PST)
Received: from ?IPv6:2620:0:2820:2:226:2dff:fefc:4f4a? ([2620:0:2820:2:226:2dff:fefc:4f4a]) by mx.google.com with ESMTPS id bc9sm1820859qab.2.2012.11.16.13.21.14 (version=SSLv3 cipher=OTHER); Fri, 16 Nov 2012 13:21:14 -0800 (PST)
Message-ID: <50A6AE49.2080908@gmail.com>
Date: Fri, 16 Nov 2012 16:21:13 -0500
From: Mike Douglass <mikeadouglass@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: IETF Calsify <calsify@ietf.org>
References: <20121116211748.25146.14269.idtracker@ietfa.amsl.com>
In-Reply-To: <20121116211748.25146.14269.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20121116211748.25146.14269.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------040004010406070200060404"
Subject: [calsify] Fwd: New Version Notification for draft-douglass-calendar-extension-02.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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, 16 Nov 2012 21:21:17 -0000

This is a multi-part message in MIME format.
--------------040004010406070200060404
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

This is a proposed extension to iCalendar (RFC5545) which adds some 
properties particularly useful to event publishers.

It also adds some property parameters (HASH and ID) which help 
publishers detect that related properties are no longer in synch.



-------- Original Message --------
Subject: 	New Version Notification for 
draft-douglass-calendar-extension-02.txt
Date: 	Fri, 16 Nov 2012 13:17:48 -0800
From: 	internet-drafts@ietf.org
To: 	douglm@rpi.edu



A new version of I-D, draft-douglass-calendar-extension-02.txt
has been successfully submitted by Michael Douglass and posted to the
IETF repository.

Filename:	 draft-douglass-calendar-extension
Revision:	 02
Title:		 Event Publishing Extensions to Icalendar
Creation date:	 2012-11-16
WG ID:		 Individual Submission
Number of pages: 21
URL:             http://www.ietf.org/internet-drafts/draft-douglass-calendar-extension-02.txt
Status:          http://datatracker.ietf.org/doc/draft-douglass-calendar-extension
Htmlized:        http://tools.ietf.org/html/draft-douglass-calendar-extension-02
Diff:            http://www.ietf.org/rfcdiff?url2=draft-douglass-calendar-extension-02

Abstract:
    This specification introduces a number of new iCalendar properties
    which are of particular use for event publishers and in social
    networking.

                                                                                   


The IETF Secretariat



-- 
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------

Teach CanIt if this mail (ID 54681430) is spam:
Spam:        http://respite.rpi.edu/b.php?c=s&i=54681430&m=b5e2044261f8
Not spam:    http://respite.rpi.edu/b.php?c=n&i=54681430&m=b5e2044261f8
Forget vote: http://respite.rpi.edu/b.php?c=f&i=54681430&m=b5e2044261f8
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS






--------------040004010406070200060404
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    This is a proposed extension to iCalendar (RFC5545) which adds some
    properties particularly useful to event publishers.<br>
    <br>
    It also adds some property parameters (HASH and ID) which help
    publishers detect that related properties are no longer in synch.<br>
    <br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>New Version Notification for
              draft-douglass-calendar-extension-02.txt</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Fri, 16 Nov 2012 13:17:48 -0800</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:douglm@rpi.edu">douglm@rpi.edu</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>A new version of I-D, draft-douglass-calendar-extension-02.txt
has been successfully submitted by Michael Douglass and posted to the
IETF repository.

Filename:	 draft-douglass-calendar-extension
Revision:	 02
Title:		 Event Publishing Extensions to Icalendar
Creation date:	 2012-11-16
WG ID:		 Individual Submission
Number of pages: 21
URL:             <a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-douglass-calendar-extension-02.txt">http://www.ietf.org/internet-drafts/draft-douglass-calendar-extension-02.txt</a>
Status:          <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-douglass-calendar-extension">http://datatracker.ietf.org/doc/draft-douglass-calendar-extension</a>
Htmlized:        <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-douglass-calendar-extension-02">http://tools.ietf.org/html/draft-douglass-calendar-extension-02</a>
Diff:            <a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-douglass-calendar-extension-02">http://www.ietf.org/rfcdiff?url2=draft-douglass-calendar-extension-02</a>

Abstract:
   This specification introduces a number of new iCalendar properties
   which are of particular use for event publishers and in social
   networking.

                                                                                  


The IETF Secretariat



-- 
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------

Teach CanIt if this mail (ID 54681430) is spam:
Spam:        <a class="moz-txt-link-freetext" href="http://respite.rpi.edu/b.php?c=s&amp;i=54681430&amp;m=b5e2044261f8">http://respite.rpi.edu/b.php?c=s&amp;i=54681430&amp;m=b5e2044261f8</a>
Not spam:    <a class="moz-txt-link-freetext" href="http://respite.rpi.edu/b.php?c=n&amp;i=54681430&amp;m=b5e2044261f8">http://respite.rpi.edu/b.php?c=n&amp;i=54681430&amp;m=b5e2044261f8</a>
Forget vote: <a class="moz-txt-link-freetext" href="http://respite.rpi.edu/b.php?c=f&amp;i=54681430&amp;m=b5e2044261f8">http://respite.rpi.edu/b.php?c=f&amp;i=54681430&amp;m=b5e2044261f8</a>
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS


</pre>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------040004010406070200060404--

From cyrus@daboo.name  Fri Nov 30 08:05:19 2012
Return-Path: <cyrus@daboo.name>
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 7D90521F8B50 for <calsify@ietfa.amsl.com>; Fri, 30 Nov 2012 08:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.874
X-Spam-Level: 
X-Spam-Status: No, score=-101.874 tagged_above=-999 required=5 tests=[AWL=0.725, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G6zexI2a1gmd for <calsify@ietfa.amsl.com>; Fri, 30 Nov 2012 08:05:14 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5A60C21F8B4A for <calsify@ietf.org>; Fri, 30 Nov 2012 08:05:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 1710C369632C for <calsify@ietf.org>; Fri, 30 Nov 2012 11:05:07 -0500 (EST)
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 ZcZjREkV23Ys for <calsify@ietf.org>; Fri, 30 Nov 2012 11:05:06 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 3697F369631F for <calsify@ietf.org>; Fri, 30 Nov 2012 11:05:05 -0500 (EST)
Date: Fri, 30 Nov 2012 11:05:02 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: IETF Calsify <calsify@ietf.org>
Message-ID: <A4C4083A7F0FFA0A5922CBAA@caldav.corp.apple.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=601
Subject: [calsify] Timezone service draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Nov 2012 16:05:19 -0000

Hi folks,
We have posted a new version of the timezone service draft: 
<https://datatracker.ietf.org/doc/draft-douglass-timezone-service/> and 
would greatly appreciate reviews of this as we intend to ask the IETF/IESG 
to start the process of review/approval/publication.

There has been one big change in this new version: the switch to using JSON 
for the responses from the server rather than XML. This was something we 
had been considering for a while - primarily because we think the most 
common "light weight" clients wanting to use this protocol will be 
web/browser based.

-- 
Cyrus Daboo


From sla@ucolick.org  Fri Nov 30 11:57:48 2012
Return-Path: <sla@ucolick.org>
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 987CE21F89F1 for <calsify@ietfa.amsl.com>; Fri, 30 Nov 2012 11:57:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HzFTlqa7x5ut for <calsify@ietfa.amsl.com>; Fri, 30 Nov 2012 11:57:47 -0800 (PST)
Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234]) by ietfa.amsl.com (Postfix) with ESMTP id CBD6221F85C2 for <calsify@ietf.org>; Fri, 30 Nov 2012 11:57:25 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 8810A28B5; Fri, 30 Nov 2012 11:57:25 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.ucolick.org (Postfix) with ESMTP id 7784A2834; Fri, 30 Nov 2012 11:57:25 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (8.14.4/8.13.8) with ESMTP id qAUJvPKE031752; Fri, 30 Nov 2012 11:57:25 -0800
Received: (from sla@localhost) by geneva.ucolick.org (8.14.4/8.14.4/Submit) id qAUJvO3u031751; Fri, 30 Nov 2012 11:57:24 -0800
Date: Fri, 30 Nov 2012 11:57:24 -0800
From: Steve Allen <sla@ucolick.org>
To: IETF Calsify <calsify@ietf.org>
Message-ID: <20121130195724.GO12287@ucolick.org>
References: <A4C4083A7F0FFA0A5922CBAA@caldav.corp.apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A4C4083A7F0FFA0A5922CBAA@caldav.corp.apple.com>
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [calsify] Timezone service draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Nov 2012 19:57:48 -0000

On Fri 2012-11-30T11:05:02 -0500, Cyrus Daboo hath writ:
> We have posted a new version of the timezone service draft:
> <https://datatracker.ietf.org/doc/draft-douglass-timezone-service/>
> and would greatly appreciate reviews of this as we intend to ask the
> IETF/IESG to start the process of review/approval/publication.

I do not find that the draft contains any mechanism for distributing
the content of the leapseconds file which is part of the IANA time
zone database.

It is currently the case that the UTC time scale is defined by ITU-R
recommendation TF.460-6 which is available at
http://www.itu.int/rec/R-REC-TF.460-6-200202-I/en
It looks as if in this internet draft the connection to the definition
of UTC is via RFC 5545 which references ISO 8601 which references the
defining documents and responsible agencies for UTC.

As of February 2012 the ITU-R had issued
Administrative Circular CA/201
http://www.itu.int/md/R00-CA-CIR-0201/en
in which Resolution 653 [COM6/20] (WRC-12) was designated as
WRC-15 Agenda item 1.14.  That calls upon its working party to remain
engaged in a process which may result in a redefinition of UTC and/or
of the broadcast time scale which underlies the implementation of
clocks in computing systems.

It is clearly not possible for this draft to include the results of
ITU-R decisions which will not be made until year 2015.  It is clear
that any result from the ITU-R, and the reactions of governmental
agencies responsible for local times, will be consistent with the
current contents of IANA tz/zoneinfo database -- if the leapseconds
file is included as part of the scheme.

The current draft has section "4.1.7.  Extensions" which will allow
for subsequent inclusion of the data from the leapseconds file.  The
usual pattern from the ITU-R is to allow a five year period between
announcement of change and implementation of change.  Nevertheless, if
the information in the leapseconds file can be included into the
protocols of this internet draft then standards bodies and developers
will be much less rushed to implement any change that may be decreed.

--
Steve Allen                 <sla@ucolick.org>                WGS-84 (GPS)
UCO/Lick Observatory--ISB   Natural Sciences II, Room 165    Lat  +36.99855
1156 High Street            Voice: +1 831 459 3046           Lng -122.06015
Santa Cruz, CA 95064        http://www.ucolick.org/~sla/     Hgt +250 m

From cyrus@daboo.name  Fri Nov 30 12:35:52 2012
Return-Path: <cyrus@daboo.name>
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 6AE5F21F8B72 for <calsify@ietfa.amsl.com>; Fri, 30 Nov 2012 12:35:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.237
X-Spam-Level: 
X-Spam-Status: No, score=-102.237 tagged_above=-999 required=5 tests=[AWL=0.363, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MloDKEEKnpvv for <calsify@ietfa.amsl.com>; Fri, 30 Nov 2012 12:35:51 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 700F921F8709 for <calsify@ietf.org>; Fri, 30 Nov 2012 12:35:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id A3F4E369A625; Fri, 30 Nov 2012 15:35:50 -0500 (EST)
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 9IqxM5WDjzmM; Fri, 30 Nov 2012 15:35:49 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 1AEF1369A61A; Fri, 30 Nov 2012 15:35:48 -0500 (EST)
Date: Fri, 30 Nov 2012 15:35:45 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Steve Allen <sla@ucolick.org>, IETF Calsify <calsify@ietf.org>
Message-ID: <0EC0253C28D64AFECE64232A@caldav.corp.apple.com>
In-Reply-To: <20121130195724.GO12287@ucolick.org>
References: <A4C4083A7F0FFA0A5922CBAA@caldav.corp.apple.com> <20121130195724.GO12287@ucolick.org>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1351
Subject: Re: [calsify] Timezone service draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Nov 2012 20:35:52 -0000

Hi Steve,

--On November 30, 2012 11:57:24 AM -0800 Steve Allen <sla@ucolick.org> 
wrote:

>> We have posted a new version of the timezone service draft:
>> <https://datatracker.ietf.org/doc/draft-douglass-timezone-service/>
>> and would greatly appreciate reviews of this as we intend to ask the
>> IETF/IESG to start the process of review/approval/publication.
>
> I do not find that the draft contains any mechanism for distributing
> the content of the leapseconds file which is part of the IANA time
> zone database.

Correct - however, calendaring and scheduling clients (which are the ones 
we are initially targeting for this service) don't need leap second 
information as they typically rely on  OS level time apis to get UTC or 
local time.

That said, in the longer term we would like to see this service being used 
to distribute the equivalent of "zoneinfo" files (or something easily 
converted into zoneinfo) - doing that will likely involve developing a more 
"generic" format for timezone data (e.g., a JSON representation of IANA 
tzdb). At that point, a way to get the leap seconds list would be good too.

So yes leap seconds are not available, but I don't believe that is a 
handicap for the initial target audience. We have designed the protocol to 
be extensible so adding leap seconds is easy after the fact.

-- 
Cyrus Daboo

