Apps Area Architecture Workshop announcement

Lisa Dusseault <lisa@osafoundation.org> Thu, 15 November 2007 22:03 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ismnx-0003kW-RT; Thu, 15 Nov 2007 17:03:21 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Ismnw-0003fk-BX for discuss-confirm+ok@megatron.ietf.org; Thu, 15 Nov 2007 17:03:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ismnv-0003bN-GC for discuss@apps.ietf.org; Thu, 15 Nov 2007 17:03:19 -0500
Received: from laweleka.osafoundation.org ([204.152.186.98]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ismnr-0008Sz-8D for discuss@apps.ietf.org; Thu, 15 Nov 2007 17:03:19 -0500
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 526FB142207; Thu, 15 Nov 2007 14:03:15 -0800 (PST)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ky3+m8MsxXYB; Thu, 15 Nov 2007 14:03:09 -0800 (PST)
Received: from [10.1.1.107] (unknown [157.22.41.236]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id BCB2F1421FC; Thu, 15 Nov 2007 14:03:09 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F7CF3E83-FD69-454F-8E17-491834C65F56@osafoundation.org>
Content-Transfer-Encoding: 7bit
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Apps Area Architecture Workshop announcement
Date: Thu, 15 Nov 2007 14:03:07 -0800
To: Apps Discuss <discuss@apps.ietf.org>, iesg@ietf.org, IAB IAB <iab@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: -4.0 (----)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Chris Newman <Chris.Newman@Sun.COM>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

On Feb 11 and 12, there will be an Applications Area Architecture  
workshop somewhere in the Bay Area.  We hope to nail down a venue  
once we've got a better idea of attendance.  We are going to look for  
a host, but if there are a few expenses not covered, we may ask for a  
few 100$ attendance fee.  If we need to charge a small fee we'll ask  
in advance of the actual meeting.

Position papers are required of all attendees by Dec 14.  These  
should be a few pages of text on some topic related to Applications  
area architectural issues.  Since the group of attendees is expected  
to span HTTP and AtomPub, email, IM, calendaring, directories and  
more, issues should be of interest to more than one of these groups.   
Some existing Applications architecture "modules" that already are  
reused  include SASL, URLs, MIME types, XML and XML schemas and  
namespaces, HTTP as a substrate, TLS, ABNF, BEEP.

A position paper could describe a problem or make a proposal to solve  
a problem.  The paper could be a prelude to an I-D of any kind or to  
a WG charter, or might simply educate and persuade.  An ideal  
position paper would seed new work or make progress towards solving a  
problem that would benefit Apps protocol designers, implementors or  
users.

Participants may send position papers directly to Lisa and Chris,  
although you can send position papers directly to the Apps Discuss  
list (we'll be circulating the papers publicly anyway).

Since the due date for papers is Dec 14, if you'd like to flesh out  
an idea, the Vancouver IETF meeting might be a handy place to grab  
people and do so.

In advance of Dec 14, we'd still appreciate early RSVPs.

Lisa