Re: [Jcardcal] RFC 7265 on jCal: The JSON Format for iCalendar
Michael Angstadt <mike.angstadt@gmail.com> Tue, 03 June 2014 18:23 UTC
Return-Path: <mike.angstadt@gmail.com>
X-Original-To: jcardcal@ietfa.amsl.com
Delivered-To: jcardcal@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86A121A0269 for <jcardcal@ietfa.amsl.com>; Tue, 3 Jun 2014 11:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, 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 jJG7W2AmQHT9 for <jcardcal@ietfa.amsl.com>; Tue, 3 Jun 2014 11:23:12 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C9831A0313 for <jcardcal@ietf.org>; Tue, 3 Jun 2014 11:23:12 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id 63so13883801qgz.2 for <jcardcal@ietf.org>; Tue, 03 Jun 2014 11:23:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DBYKCinzji0aYVAS2IwP8obmseFYDAAKlSnFInyq/nk=; b=zElldDHNbg2LVoe1qyWiH7UL0GmgB4s/otJDOWtJ35VUwOHu827RJw8LB52JofDAnK H+3cED1jQ7AwJFD6JTYcyafdxBg0p/c4wCdvtn0I00uZYebTbPHv4rYoztkPAUKIGheT coQkp3aC2o28zPgLb15qMV+1HBrMXUnUecMDzOPalmanL5FADQndQjtD4M/nohHKPtm7 N1nwouSs0KChYZcp/Q1I50ARNWQtAu+ifrV5IALfosn6wucRz4PCJgo3nTZgq6xtUcFg WH+E4L9sX4OOb1PI+h0kxv1un03m/xuMme5nAf+16ip6OkhYSDXcc7PxsvXlYkeQzcht djbQ==
MIME-Version: 1.0
X-Received: by 10.140.27.245 with SMTP id 108mr58449905qgx.18.1401819786140; Tue, 03 Jun 2014 11:23:06 -0700 (PDT)
Received: by 10.140.109.225 with HTTP; Tue, 3 Jun 2014 11:23:06 -0700 (PDT)
In-Reply-To: <46A1DF3F04371240B504290A071B4DB63E5A8C3D@SZXEMA510-MBX.china.huawei.com>
References: <20140530214655.586C1180016@rfc-editor.org> <5388FCCD.5030201@stpeter.im> <46A1DF3F04371240B504290A071B4DB63E5A8C3D@SZXEMA510-MBX.china.huawei.com>
Date: Tue, 03 Jun 2014 14:23:06 -0400
Message-ID: <CAJNb_g2W18E=hRqmJGBc=z+mfdXzVqQ7Ek8NfrVTxnMEi4t_PQ@mail.gmail.com>
From: Michael Angstadt <mike.angstadt@gmail.com>
To: Bert Greevenbosch <Bert.Greevenbosch@huawei.com>
Content-Type: multipart/alternative; boundary="001a11c1526064618204faf29a60"
Archived-At: http://mailarchive.ietf.org/arch/msg/jcardcal/wyjIn_HgRNB0Yphtjh0YjRJP5cY
Cc: "jcardcal@ietf.org" <jcardcal@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Jcardcal] RFC 7265 on jCal: The JSON Format for iCalendar
X-BeenThere: jcardcal@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: JSON data formats for vCard and iCalendar WG <jcardcal.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jcardcal/>
List-Post: <mailto:jcardcal@ietf.org>
List-Help: <mailto:jcardcal-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 18:23:14 -0000
I've already updated my iCalendar library to reference the new RFC. Thanks for your hard work! -Mike On Tue, Jun 3, 2014 at 5:34 AM, Bert Greevenbosch < Bert.Greevenbosch@huawei.com> wrote: > +1, excellent job! Glad that both jCard and jCal have succesfully become > RFCs! > > Best regards, > Bert > > > > -----Original Message----- > > From: jcardcal [mailto:jcardcal-bounces@ietf.org] On Behalf Of Peter > > Saint-Andre > > Sent: 31 May 2014 05:49 > > To: jcardcal@ietf.org > > Subject: Re: [Jcardcal] RFC 7265 on jCal: The JSON Format for iCalendar > > > > Good work, authoring team! :-) > > > > On 5/30/14, 3:46 PM, rfc-editor@rfc-editor.org wrote: > > > A new Request for Comments is now available in online RFC libraries. > > > > > > > > > RFC 7265 > > > > > > Title: jCal: The JSON Format for iCalendar > > > Author: P. Kewisch, C. Daboo, M. Douglass > > > Status: Standards Track > > > Stream: IETF > > > Date: May 2014 > > > Mailbox: mozilla@kewis.ch, > > > cyrus@daboo.name, > > > douglm@rpi.edu > > > Pages: 31 > > > Characters: 56274 > > > Updates/Obsoletes/SeeAlso: None > > > > > > I-D Tag: draft-ietf-jcardcal-jcal-10.txt > > > > > > URL: http://www.rfc-editor.org/rfc/rfc7265.txt > > > > > > This specification defines "jCal", a JSON format for iCalendar data. > > > The iCalendar data format is a text format for capturing and > > > exchanging information normally stored within a calendaring and > > > scheduling application, for example, tasks and events. JSON is a > > > lightweight, text-based, language-independent data interchange format > > > commonly used in Internet applications. > > > > > > This document is a product of the JSON data formats for vCard and > > iCalendar Working Group of the IETF. > > > > > > This is now a Proposed Standard. > > > > > > STANDARDS TRACK: This document specifies an Internet standards track > > > protocol for the Internet community,and requests discussion and > > suggestions > > > for improvements. Please refer to the current edition of the > > Internet > > > Official Protocol Standards (STD 1) for the standardization state and > > > status of this protocol. Distribution of this memo is unlimited. > > > > > > This announcement is sent to the IETF-Announce and rfc-dist lists. > > > To subscribe or unsubscribe, see > > > http://www.ietf.org/mailman/listinfo/ietf-announce > > > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > > > > > For searching the RFC series, see http://www.rfc-editor.org/search > > > For downloading RFCs, see http://www.rfc-editor.org/rfc.html > > > > > > Requests for special distribution should be addressed to either the > > > author of the RFC in question, or to rfc-editor@rfc-editor.org. > > Unless > > > specifically noted otherwise on the RFC itself, all RFCs are for > > > unlimited distribution. > > > > > > > > > The RFC Editor Team > > > Association Management Solutions, LLC > > > > > > > > > _______________________________________________ > > > jcardcal mailing list > > > jcardcal@ietf.org > > > https://www.ietf.org/mailman/listinfo/jcardcal > > > > > > > _______________________________________________ > > jcardcal mailing list > > jcardcal@ietf.org > > https://www.ietf.org/mailman/listinfo/jcardcal > > _______________________________________________ > jcardcal mailing list > jcardcal@ietf.org > https://www.ietf.org/mailman/listinfo/jcardcal >
- [Jcardcal] RFC 7265 on jCal: The JSON Format for … rfc-editor
- Re: [Jcardcal] RFC 7265 on jCal: The JSON Format … Peter Saint-Andre
- Re: [Jcardcal] RFC 7265 on jCal: The JSON Format … Bert Greevenbosch
- Re: [Jcardcal] RFC 7265 on jCal: The JSON Format … Michael Angstadt
- Re: [Jcardcal] RFC 7265 on jCal: The JSON Format … Pete Resnick
- Re: [Jcardcal] RFC 7265 on jCal: The JSON Format … Philipp Kewisch