Re: [yam] scheduling conflicts for upcoming YAM meeting

Barry Leiba <barryleiba.mailing.lists@gmail.com> Sat, 06 February 2010 20:50 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79FEF28C13A for <yam@core3.amsl.com>; Sat, 6 Feb 2010 12:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level:
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[AWL=-0.298, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgxBhZf8iR8l for <yam@core3.amsl.com>; Sat, 6 Feb 2010 12:50:09 -0800 (PST)
Received: from mail-fx0-f225.google.com (mail-fx0-f225.google.com [209.85.220.225]) by core3.amsl.com (Postfix) with ESMTP id 7840028C133 for <yam@ietf.org>; Sat, 6 Feb 2010 12:50:09 -0800 (PST)
Received: by fxm25 with SMTP id 25so2437123fxm.32 for <yam@ietf.org>; Sat, 06 Feb 2010 12:51:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SvhhPerG63m3URU9HO/5j5WS13Elg8RoTD27cY7uRTs=; b=l2MOyDxeVSZVo8u+Uor3GZYC9cRXP+07DnhaLrNeUgGrO0GCDiwV0vv54sYxezZJ7O k6qVUgbi4buXKApeeaY4DA8ORRYRBBn08WVQgNXtSBV7VnRnVoYHx2XUM6ZQqluxkPfw OP/KeyUfG8MbE3VpKFy5Iqmu7ns8EoApy/RsY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=CyePHL+j6QHSqGuKCadUxSUpdumbhwdbMKlWiJQgaZZ1/XM0PDutsV/pv7fw7oTlVR IJSfBgvHq7F/Fxl3FUG6E378p/3WSj8lwYbijLPMuZX00Fu4FTr/ZwVt9tJ22plo0UHv UmlJIlRTvq9Dynkrct9P4m+zlrWjeskWxBt90=
MIME-Version: 1.0
Received: by 10.223.144.71 with SMTP id y7mr5223142fau.54.1265489459942; Sat, 06 Feb 2010 12:50:59 -0800 (PST)
In-Reply-To: <4B6DCB29.8060104@att.com>
References: <4B6DCB29.8060104@att.com>
Date: Sat, 06 Feb 2010 15:50:59 -0500
Message-ID: <6c9fcc2a1002061250l6051ce38qda7488fcc9f6da3e@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Tony Hansen <tony@att.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Yet Another Mail Working Group <yam@ietf.org>
Subject: Re: [yam] scheduling conflicts for upcoming YAM meeting
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2010 20:50:10 -0000

>   primary
>        APP     apparea
>        APP     httpbis
>        APP     idnabis
>        APP     morg
>        APP     sieve
>        SEC     sasl
>        SEC     dkim
>        APP     eai
>        RAI     xmpp
>        APP     alto
>
>   secondary
>        APP     ogpx
>        APP     vcarddav
>        APP     oauth

Add "marf" to primary.  There is no such WG as "ogpx"; change it to
"vwrap".  And in "other", specify "any app-area BOFs".

There are two other new app-area WGs (besides marf): iri and hybi.  I
don't see a need to include them, but perhaps others might.

Barry