Re: [salud] Shall we adopt draft-liess-dispatch-alert-info-urns-03 as a WG work item?
Paul Kyzivat <pkyzivat@cisco.com> Fri, 19 November 2010 04:21 UTC
Return-Path: <pkyzivat@cisco.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 5F2B93A672F for <salud@core3.amsl.com>; Thu, 18 Nov 2010 20:21:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.499
X-Spam-Level:
X-Spam-Status: No, score=-110.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 CPv5-M6zshwQ for <salud@core3.amsl.com>; Thu, 18 Nov 2010 20:21:37 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 9275C3A635F for <salud@ietf.org>; Thu, 18 Nov 2010 20:21:37 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAL6J5UxAZnwM/2dsb2JhbACUVo4BcaIamzaFSwSEWIYCgww
X-IronPort-AV: E=Sophos;i="4.59,221,1288569600"; d="scan'208";a="183671141"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 19 Nov 2010 04:22:26 +0000
Received: from [10.86.248.1] (bxb-vpn3-1.cisco.com [10.86.248.1]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id oAJ4MQDc020860 for <salud@ietf.org>; Fri, 19 Nov 2010 04:22:26 GMT
Message-ID: <4CE5FB81.2070903@cisco.com>
Date: Fri, 19 Nov 2010 12:22:25 +0800
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: salud@ietf.org
References: <CD5674C3CD99574EBA7432465FC13C1B2202288A32@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288A32@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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, 19 Nov 2010 04:21:38 -0000
I'm in favor of that. Thanks, Paul On 11/19/2010 3:49 AM, Worley, Dale R (Dale) wrote: > [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 > _______________________________________________ > salud mailing list > salud@ietf.org > https://www.ietf.org/mailman/listinfo/salud >
- [salud] Shall we adopt draft-liess-dispatch-alert… Worley, Dale R (Dale)
- Re: [salud] Shall we adopt draft-liess-dispatch-a… DRAGE, Keith (Keith)
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Peter Saint-Andre
- Re: [salud] Shall we adopt draft-liess-dispatch-a… R.Jesske
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Paul Kyzivat
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Shida Schubert
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Hutton, Andrew
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Worley, Dale R (Dale)
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Martin.Huelsemann
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Alan Johnston
- Re: [salud] Shall we adopt draft-liess-dispatch-a… Worley, Dale R (Dale)