Re: [salud] Shall we adopt draft-liess-dispatch-alert-info-urns-03 as a WG work item?

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 03 December 2010 18:26 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: salud@core3.amsl.com
Delivered-To: salud@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 632ED28C104 for <salud@core3.amsl.com>; Fri, 3 Dec 2010 10:26:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qPD30Zx3nB1c for <salud@core3.amsl.com>; Fri, 3 Dec 2010 10:25:52 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 268DC28C138 for <salud@ietf.org>; Fri, 3 Dec 2010 10:25:48 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj8HAMvE+EzGmAcF/2dsb2JhbACjOWsGqi0CmQ2FSASEXok5
X-IronPort-AV: E=Sophos;i="4.59,294,1288584000"; d="scan'208";a="48375736"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 03 Dec 2010 13:27:06 -0500
X-IronPort-AV: E=Sophos;i="4.59,294,1288584000"; d="scan'208";a="549615660"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 Dec 2010 13:27:05 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 3 Dec 2010 13:27:05 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "salud@ietf.org" <salud@ietf.org>
Date: Fri, 03 Dec 2010 13:27:04 -0500
Thread-Topic: [salud] Shall we adopt draft-liess-dispatch-alert-info-urns-03 as a WG work item?
Thread-Index: AQHLh1oMcpP69GiPsEath4HT7oi295OPHjWh
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288A84@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B2202288A32@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288A32@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [salud] Shall we adopt draft-liess-dispatch-alert-info-urns-03 as a WG work item?
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Dec 2010 18:26:02 -0000

[as chair]

Since 9 people expressed support for adopting draft-liess-dispatch-alert-info-urns as a work group item, and nobody has ever expressed opposition, I will go ahead and set up draft-liess-dispatch-alert-info-urns-03 as a work group item.

Dale