
From yakushev@google.com  Tue Jan 14 01:30:12 2014
Return-Path: <yakushev@google.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 C73B41AE06A for <calsify@ietfa.amsl.com>; Tue, 14 Jan 2014 01:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=unavailable
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 VzsjnzbxTE1G for <calsify@ietfa.amsl.com>; Tue, 14 Jan 2014 01:30:09 -0800 (PST)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1EB1AE058 for <calsify@ietf.org>; Tue, 14 Jan 2014 01:30:09 -0800 (PST)
Received: by mail-qe0-f51.google.com with SMTP id a11so1026380qen.24 for <calsify@ietf.org>; Tue, 14 Jan 2014 01:29:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=v52X06pO7uLQMFRfJLqcdkF7Z58KmAeG1xHZJt2ls3w=; b=ONpch2pk+eqWKN59MjtqodMaWOk/oalJvD0DiMb6K0LlLjbpIgmu1/PBe1C152Xt+2 5Wr1O9uV0ntWcXfNwngdT4qRbLQV0P2ABCfKqAGGV/a6HWp9Yd6G8h3aN0u8RIg5i0ea 3/idwtPGeRwmO5vPa2OyjiQR7ZFA4xJpdCDvuKDRY0NtEqTgyzJQHvEBH89XlwzWHslO g669UlJCXZOn8fvfxi7sm5hto2fVfIcB8VpBA5lEiKMQHCvcueJ3r0nkY0hwN9FEsaOd iLhcux5vSQKzlX9NHFEtJ93g/UKS1AoLA9u68Ec0pjaekNdsGvRXy1y0CekNSZLOnrz+ FIIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=v52X06pO7uLQMFRfJLqcdkF7Z58KmAeG1xHZJt2ls3w=; b=guxouUSVt/ENuZ2Nw5nkXZIJ88Q63rq+WKE7EIiqSjiL+7MEL19ZiDoh8lX++er2VP oNIHIg2Fz52BO9kUI5vX3UniGOJKS6P7uOUrYzLGxOB2rNvDArmoSjspkx93iTXHdw+h 4tj6oD61f9qZGslcKCkSpRw8Fsjy+usJou4eb4WKdsG3qnjXs/da6FbbSGENI5tF8kiD gQs3bi6dqHZMI7rkh+Ei8KcGMVybu8baMHoMHV+I9YsghQYb5XsKORB4jBgwwKB2wBCz bODyc4EonnTg1710B8wsLvottg5KNrRwD/3xv0Y8EMx5PUDiEUb5i4gQkRnHLF6IHN0R Bo4w==
X-Gm-Message-State: ALoCoQlRmXvRn81q7RpThO/TXxpIW9cOBc5S5u5g3YA9LtLH5SAV1tLwpX3+UP7xhky8mu9pW6CoEMfsDRmVBAAF0miIsthkpREC9udOdAwuNq7ngC56nIV0/S4VwToAQpr9ACiE6KH4mryNErelFEmMdZEoUm2KKMhX51Ttjg6nj50+d9x5oYOUn+EU7Als+G7ipv71KLGr
MIME-Version: 1.0
X-Received: by 10.229.84.201 with SMTP id k9mr972903qcl.18.1389691797218; Tue, 14 Jan 2014 01:29:57 -0800 (PST)
Received: by 10.229.140.135 with HTTP; Tue, 14 Jan 2014 01:29:57 -0800 (PST)
Date: Tue, 14 Jan 2014 10:29:57 +0100
Message-ID: <CAJxDCqUXWiMexON+ya-2mA2hF4gMK0D+8iY_kvvPEzLeF0BNig@mail.gmail.com>
From: Gregory Yakushev <yakushev@google.com>
To: Calsify <calsify@ietf.org>, ietf@ietf.org, Cyrus Daboo <cyrus@daboo.name>
Content-Type: multipart/alternative; boundary=001a1134536eebbeb504efead541
Subject: [calsify] Last Call <draft-daboo-icalendar-rscale> (Non-Gregorian Recurrence Rules in iCalendar) to Proposed Standard
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, 14 Jan 2014 09:30:13 -0000

--001a1134536eebbeb504efead541
Content-Type: text/plain; charset=UTF-8

This is last call for
http://tools.ietf.org/html/draft-daboo-icalendar-rscale . The draft was
extensively discussed at CalConnect (http://calconnect.org/), previous IETF
discussion is on calsify@ietf.org .

The draft functionality is currently fully implemented in Google Calendar. You
can try it out using proprietary Google Calendar API:
1. Follow this link: http://goo.gl/tKTUQZ
2. Click on Oauth2.0 trigger in the upper right corner to authenticate
3. Enter your Google Calendar e-mail into calendarId field
4. Click Execute, you should get 200 OK
5. Now your non-Gregorian recurring event is visible in UI, embedded
calendar, and any client that doesn't do recurrence expansion by itself

Your comments are welcome,
Grisha

--001a1134536eebbeb504efead541
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This is last call for=C2=A0<a href=3D"http://tools.ietf.or=
g/html/draft-daboo-icalendar-rscale">http://tools.ietf.org/html/draft-daboo=
-icalendar-rscale</a> . The draft was extensively discussed at CalConnect (=
<a href=3D"http://calconnect.org/">http://calconnect.org/</a>), previous IE=
TF discussion is on <a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a=
> .=C2=A0<div>
<br><div>The draft functionality is currently fully implemented in Google C=
alendar.=C2=A0<span style=3D"font-family:arial,sans-serif;font-size:13px">Y=
ou can try it out using proprietary Google Calendar API:</span></div><div><=
div style=3D"font-family:arial,sans-serif;font-size:13px">
1. Follow this link:=C2=A0<a href=3D"http://goo.gl/tKTUQZ" target=3D"_blank=
">http://goo.gl/tKTUQZ</a></div><div style=3D"font-family:arial,sans-serif;=
font-size:13px">2. Click on Oauth2.0 trigger in the upper right corner to a=
uthenticate</div>
<div style=3D"font-family:arial,sans-serif;font-size:13px">3. Enter your Go=
ogle Calendar e-mail into calendarId field</div><div style=3D"font-family:a=
rial,sans-serif;font-size:13px">4. Click Execute, you should get 200 OK</di=
v>
<div style=3D"font-family:arial,sans-serif;font-size:13px">5. Now your non-=
Gregorian recurring event is visible in UI, embedded calendar, and any clie=
nt that doesn&#39;t do recurrence expansion by itself</div></div><div><br>
</div></div><div>Your comments are welcome,</div><div>Grisha</div></div>

--001a1134536eebbeb504efead541--

From barryleiba.mailing.lists@gmail.com  Mon Jan 20 10:28:15 2014
Return-Path: <barryleiba.mailing.lists@gmail.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 AC2C91A022B; Mon, 20 Jan 2014 10:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.621
X-Spam-Level: 
X-Spam-Status: No, score=0.621 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 6OnLuNHhjvDR; Mon, 20 Jan 2014 10:28:13 -0800 (PST)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4321A021A; Mon, 20 Jan 2014 10:28:13 -0800 (PST)
Received: by mail-ve0-f176.google.com with SMTP id oz11so1853929veb.7 for <multiple recipients>; Mon, 20 Jan 2014 10:28:13 -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:date:message-id:subject :from:to:cc:content-type; bh=mRLrudKQP5g5HsORdCzgikX9aU3aYyDvZRqMJgKc2fA=; b=B/QP2nNhybuwtKPBIEAG9825T4DSw/iYPkRM40YqgNNL7odTLUu2gMUdmSUtRMxMBM tNHIBvUe+NafVz1V67Df4e8BJy3+LGAPBnAiRzGN5kJcdflRLOQ4UbpcNkmmIT+ZT1HS /9rbvbSTY+7lU2dqvbMy/HN4+71IkVM8gpgOrVOpibXpsSMkmn6pmYuigKRoK9urcNne stxW6QEyIDggtE2WddT6oQffXOsu0d3lcD4Fq5bZp+MePQQyIDtqdD2Q2PfEF3Oai5Ph SQou9wkxuXDPi8A+3JKE7X/ID9lgSECQSKFmlvuQB62CGsBYg4jb6AkDxb2wfcE/hiG6 sKdA==
MIME-Version: 1.0
X-Received: by 10.220.98.204 with SMTP id r12mr36810vcn.48.1390242492832; Mon, 20 Jan 2014 10:28:12 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.170.71 with HTTP; Mon, 20 Jan 2014 10:28:12 -0800 (PST)
In-Reply-To: <CAJxDCqUXWiMexON+ya-2mA2hF4gMK0D+8iY_kvvPEzLeF0BNig@mail.gmail.com>
References: <CAJxDCqUXWiMexON+ya-2mA2hF4gMK0D+8iY_kvvPEzLeF0BNig@mail.gmail.com>
Date: Mon, 20 Jan 2014 13:28:12 -0500
X-Google-Sender-Auth: 0NsZUnFmVfkAuJWCU5BC5l_Nxsc
Message-ID: <CAC4RtVDFVYcOqa_H6n8ys2FV+92P0yZLdB4He7_h3h_nB3OM8Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Gregory Yakushev <yakushev@google.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Calsify <calsify@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: [calsify] Last Call <draft-daboo-icalendar-rscale> (Non-Gregorian Recurrence Rules in iCalendar) to Proposed Standard
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: Mon, 20 Jan 2014 18:28:15 -0000

I need to point out that the subject message (below) is NOT an
official IETF Last Call message, though the subject makes it look like
one.  It is a last call by the authors for comments, before they move
their document into the formal IETF process (most likely, getting an
AD to sponsor the document).

That said, as Grisha says: your comments are welcome.  It's always
better to get them in earlier.  Assuming that the authors pursue this
as a Standards Track document, a proper IETF Last Call will eventually
appear.

Barry, Applications AD

On Tue, Jan 14, 2014 at 4:29 AM, Gregory Yakushev <yakushev@google.com> wrote:
> This is last call for
> http://tools.ietf.org/html/draft-daboo-icalendar-rscale . The draft was
> extensively discussed at CalConnect (http://calconnect.org/), previous IETF
> discussion is on calsify@ietf.org .
>
> The draft functionality is currently fully implemented in Google Calendar.
> You can try it out using proprietary Google Calendar API:
> 1. Follow this link: http://goo.gl/tKTUQZ
> 2. Click on Oauth2.0 trigger in the upper right corner to authenticate
> 3. Enter your Google Calendar e-mail into calendarId field
> 4. Click Execute, you should get 200 OK
> 5. Now your non-Gregorian recurring event is visible in UI, embedded
> calendar, and any client that doesn't do recurrence expansion by itself
>
> Your comments are welcome,
> Grisha
