IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] ical server issue

Lou Berger <lberger@labn.net> Fri, 11 September 2015 18:03 UTC

Return-Path: <lberger@labn.net>
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 617481B2E2C for <tools-development@ietfa.amsl.com>; Fri, 11 Sep 2015 11:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level:
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, 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 XJcFIVjQ2uVH for <tools-development@ietfa.amsl.com>; Fri, 11 Sep 2015 11:03:14 -0700 (PDT)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by ietfa.amsl.com (Postfix) with SMTP id 4B54D1A1AB6 for <tools-development@ietf.org>; Fri, 11 Sep 2015 11:03:14 -0700 (PDT)
Received: (qmail 13644 invoked by uid 0); 11 Sep 2015 18:03:13 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy2.mail.unifiedlayer.com with SMTP; 11 Sep 2015 18:03:13 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id Fu361r00v2SSUrH01u39sz; Fri, 11 Sep 2015 12:03:12 -0600
X-Authority-Analysis: v=2.1 cv=EbVbHpWC c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=N659UExz7-8A:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=ff-B7xzCdYMA:10 a=48vgC7mUAAAA:8 a=jp4_KYY9MebklCigUNAA:9 a=pILNOxqGKmIA:10 a=G9WWXeuLwC8A:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=5db6E4gp8RXFPfkhx6xd+Q9ZfuA1P2NRMcz2KXP1oK0=; b=EK7MJrPzptNHwjHs2ZRyEiBxk/eVCkPuHHB2mEBGSwescMJHrvgBfIf/GSPrEBOcR8PULhzsFQKuGgPejVylXIF8WphsYrMzm5Q3s8U1+Ze5iTcKlObS+gNoS3SVjSq4;
Received: from box313.bluehost.com ([69.89.31.113]:60827 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1ZaSfD-0003CD-5H; Fri, 11 Sep 2015 12:03:07 -0600
To: Russ Housley <housley@vigilsec.com>
References: <55F2EAA4.3040503@labn.net> <E16CB3D1-4027-477D-BF5F-81F536234C47@vigilsec.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <55F31754.2020701@labn.net>
Date: Fri, 11 Sep 2015 14:03:00 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <E16CB3D1-4027-477D-BF5F-81F536234C47@vigilsec.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/Uj5qIPbvxcmTlvyCuanfWLyxrGk>
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
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 18:03:15 -0000

On 9/11/2015 1:05 PM, Russ Housley wrote:
> Lou:
>
>> 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.
> How can it be a problem with the server that two different clients are displaying different results?  I assume the entries are provided by the server in UTC and that the conversion is done by the client.

Both calendars use the standard and valid TZID property and VTIMEZONE
component to provide times in local TZ.  One note, it looks like some
versions of outlook required the TZ names to be quoted (which isn't the
standard).  Perhaps there's something related happening...

> Russ
>
>

v2.23.0 | Report a Bug | By Email