Re: [apps-discuss] Request for adoption of iSchedule as a WG work item
Ken Murchison <murch@andrew.cmu.edu> Tue, 28 May 2013 14:58 UTC
Return-Path: <murch@andrew.cmu.edu>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB7D21F8EC1 for <apps-discuss@ietfa.amsl.com>; Tue, 28 May 2013 07:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YoARp0ibHFmv for <apps-discuss@ietfa.amsl.com>; Tue, 28 May 2013 07:58:44 -0700 (PDT)
Received: from smtp.andrew.cmu.edu (SMTP.ANDREW.CMU.EDU [128.2.11.95]) by ietfa.amsl.com (Postfix) with ESMTP id C8ACE21F8E2C for <apps-discuss@ietf.org>; Tue, 28 May 2013 07:58:44 -0700 (PDT)
Received: from [68.245.171.115] (160.sub-174-254-177.myvzw.com [174.254.177.160]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.4/8.14.4) with ESMTP id r4SEwSrh017857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <apps-discuss@ietf.org>; Tue, 28 May 2013 10:58:43 -0400
Message-ID: <51A4C62E.9000201@andrew.cmu.edu>
Date: Tue, 28 May 2013 10:58:54 -0400
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <32031_1369751656_r4SEYFTw020097_4F5FFFB33B6673887C6A5ADF@cyrus.local>
In-Reply-To: <32031_1369751656_r4SEYFTw020097_4F5FFFB33B6673887C6A5ADF@cyrus.local>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.5.19.222118
X-SMTP-Spam-Clean: 10% ( TO_IN_SUBJECT 0.5, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1800_1899 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, RDNS_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_SPECIFIC 0, RDNS_WIRELESS 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __RDNS_POOLED_6 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NO_MAILTO 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0)
X-SMTP-Spam-Score: 10%
X-Scanned-By: MIMEDefang 2.60 on 128.2.11.95
Subject: Re: [apps-discuss] Request for adoption of iSchedule as a WG work item
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 14:58:49 -0000
On 5/28/2013 10:34 AM, Cyrus Daboo wrote: > Hi folks, > After consultation with Apps Area ADs and Apps Area WG chairs I would > like to request that the Apps Area WG adopt iSchedule > (<https://datatracker.ietf.org/doc/draft-desruisseaux-ischedule/>) as > a working group item. > > iSchedule is a cross-domain calendaring and scheduling protocol based > on iCalendar (RFC5545), iTIP (RFC5546) and HTTP. The goal is to allow > efficient, secure and timely exchange of scheduling messages between > servers. > > The calendaring aspects of this protocol are pretty straightforward. > The hard part is security - in effect what we have is a messaging > protocol akin to email and what we want to avoid are all the problems > inherent in email (spoofing, spam etc). To that end we have adapted > DKIM (RFC6376) for use within our protocol (with the primary goal of > solving only the issues we need for iSchedule as opposed to developing > a generic solution for signing HTTP messages). > > iSchedule originated with work done at the Calendaring and Scheduling > Consortium (CalConnect) and has been developed over the last several > years via IETF drafts. There are already a number of prototype > implementations and CalConnect has been holding regular interop events > to test those and weed out issues with the spec. > > At this point we want to move forward with the draft with more > rigorous review, specifically of the security piece, and ultimately > move forward with publication as a proposed standard. > > So this is a call to see who in this WG would be willing to work on > this document, and whether the WG should adopt it I am in favor of appsawg adopting this draft and I will continue to help work on it. -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University
- [apps-discuss] Request for adoption of iSchedule … Cyrus Daboo
- Re: [apps-discuss] Request for adoption of iSched… Ken Murchison
- Re: [apps-discuss] Request for adoption of iSched… Mike Douglass