IETF Logo Mail Archive

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

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 18 November 2010 19:51 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 F414428C0E1 for <salud@core3.amsl.com>; Thu, 18 Nov 2010 11:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.457
X-Spam-Level:
X-Spam-Status: No, score=-102.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 4kMfkviSEnnz for <salud@core3.amsl.com>; Thu, 18 Nov 2010 11:51:07 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 42BE428C0D8 for <salud@ietf.org>; Thu, 18 Nov 2010 11:51:07 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPoR5UzGmAcF/2dsb2JhbACiVnGmGwKZJ4VLBIRaiSY
X-IronPort-AV: E=Sophos;i="4.59,218,1288584000"; d="scan'208";a="250800289"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 Nov 2010 14:51:54 -0500
X-IronPort-AV: E=Sophos;i="4.59,218,1288584000"; d="scan'208";a="542200439"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Nov 2010 14:51:54 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Thu, 18 Nov 2010 14:51:54 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "salud@ietf.org" <salud@ietf.org>
Date: Thu, 18 Nov 2010 14:49:10 -0500
Thread-Topic: Shall we adopt draft-liess-dispatch-alert-info-urns-03 as a WG work item?
Thread-Index: AQHLh1oMcpP69GiPsEath4HT7oi29w==
Message-ID: <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: [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: Thu, 18 Nov 2010 19:51:08 -0000

[as chair]

Now that we have a revised version of the Liess draft, shall we adopt it as a WG work item, that is, as the base for completing the work of this working group?

Dale

v2.23.0 | Report a Bug | By Email