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

+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