[Jcardcal] RFC 7265 on jCal: The JSON Format for iCalendar

rfc-editor@rfc-editor.org Fri, 30 May 2014 21:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 461981A8880; Fri, 30 May 2014 14:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 GECqViNZhaGo; Fri, 30 May 2014 14:47:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD691A886F; Fri, 30 May 2014 14:47:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 586C1180016; Fri, 30 May 2014 14:46:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140530214655.586C1180016@rfc-editor.org>
Date: Fri, 30 May 2014 14:46:55 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/jcardcal/OuQ4Ot9RamUWLKAKyneY7qW_OI8
Cc: drafts-update-ref@iana.org, jcardcal@ietf.org, rfc-editor@rfc-editor.org
Subject: [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: Fri, 30 May 2014 21:47:44 -0000

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