Re: [TOOLS-DEVELOPMENT] ical server issue

Glen <glen@amsl.com> Fri, 11 September 2015 17:00 UTC

Return-Path: <glen@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF1B71B4F55 for <tools-development@ietfa.amsl.com>; Fri, 11 Sep 2015 10:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.587
X-Spam-Level:
X-Spam-Status: No, score=-103.587 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 78dCDOq1TL6W for <tools-development@ietfa.amsl.com>; Fri, 11 Sep 2015 10:00:56 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id EA5A01B4F59 for <tools-development@ietf.org>; Fri, 11 Sep 2015 10:00:55 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id BF6F11E5A14 for <tools-development@ietf.org>; Fri, 11 Sep 2015 10:00:35 -0700 (PDT)
Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by c8a.amsl.com (Postfix) with ESMTPSA id 9C74C1E59E6 for <tools-development@ietf.org>; Fri, 11 Sep 2015 10:00:35 -0700 (PDT)
Received: by obbbh8 with SMTP id bh8so65399314obb.0 for <tools-development@ietf.org>; Fri, 11 Sep 2015 10:00:55 -0700 (PDT)
X-Received: by 10.60.177.129 with SMTP id cq1mr670129oec.26.1441990855325; Fri, 11 Sep 2015 10:00:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.93.193 with HTTP; Fri, 11 Sep 2015 10:00:36 -0700 (PDT)
In-Reply-To: <CABL0ig5fUgUK=Ewi3EtWVkyMqnWxddWkRVpF4Or7x7sg9CnPvw@mail.gmail.com>
References: <55F2EAA4.3040503@labn.net> <CABL0ig5fUgUK=Ewi3EtWVkyMqnWxddWkRVpF4Or7x7sg9CnPvw@mail.gmail.com>
From: Glen <glen@amsl.com>
Date: Fri, 11 Sep 2015 10:00:36 -0700
Message-ID: <CABL0ig5i0T3Zum-B=NypPfqC7T9gThT++fer50sqfm-x+9Xx8g@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary="089e01184a14b38473051f7ba8e3"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/6GGysx3jANPG0gVxeg8Cxkv47SA>
Cc: IETF Tools Development <tools-development@ietf.org>
Subject: Re: [TOOLS-DEVELOPMENT] ical server issue
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: glen@amsl.com
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Sep 2015 17:00:58 -0000

Here's an interesting data point:

If I download the file at the https://ical.ietf.org/public.php/IAOC/calendar
URL manually, and save it as an ICS file on my desktop, and then I "Import"
that file into Google, the times display correctly.

It is only if I ask Google to "subscribe" to the URL in live-feed mode that
it seems to incorrectly compute the times.

As there is no difference in the data flow or what is pulled (since the
Calendar server sends everything via HTTP in the same way), I wonder if
something in Google's subscription processor is tripping on something
somewhere.

That's not a solution - because you obviously want the live feed - but it
does provide an additional point of validation, if you like, of the data.

Glen







On Fri, Sep 11, 2015 at 9:52 AM, Glen <glen@amsl.com> wrote:

> Hi Lou -
>
> AMS (ietf-action@ietf.org) would be the correct place to report a problem
> with the calendar *server* - for example, if the calendar server were down,
> or you couldn't get access, or something like that.
>
> But I confess I have no idea how or where to "report" the problem you're
> encountering.
>
> When I view the feed you mention, I see the meeting coded as:
>
> DTEND;TZID=America/New_York:20150910T130000
> DTSTART;TZID=America/New_York:20150910T120000
>
> So the calendar server appears to be delivering it correctly, as you point
> out.
>
> The question seems to be why Google calendar is misinterpreting the coding
> here.
>
> I also use Gogole calendar, and it is also misinterpreting the coding for
> me.... but I cannot tell why, nor would I know to whom that should be
> reported.
>
> I welcome thoughts on this matter!
>
> Glen
> Glen Barney
> IT Director
> AMS (IETF Secretariat)
>
>
>
> On Fri, Sep 11, 2015 at 7:52 AM, Lou Berger <lberger@labn.net> wrote:
>
>> So what's the right way to report an issue with ical.ietf.org?
>>
>> I see an issue with a meeting from yesterday 9/10/15 on
>> https://ical.ietf.org/public.php/IAOC/calendar and it looks like the
>> issues is also there for future meetings.
>>
>> The meeting correctly shows in Thunderbird as occurring at noon ET, but
>> on google calendar it shows at 10am ET.  Interesting, this has not been
>> an issue for other calendars, e.g., finance.
>>
>> Thanks,
>> Lou
>>
>>
>>
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development
>>
>
>