[sip-http-events] Implementations or plans?
"Scott Lawrence" <scott.lawrence@nortel.com> Fri, 18 December 2009 11:55 UTC
Return-Path: <scott.lawrence@nortel.com>
X-Original-To: sip-http-events@core3.amsl.com
Delivered-To: sip-http-events@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C93AF3A68B3 for <sip-http-events@core3.amsl.com>; Fri, 18 Dec 2009 03:55:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.242
X-Spam-Level:
X-Spam-Status: No, score=-6.242 tagged_above=-999 required=5 tests=[AWL=0.357, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 0eVg9eyod-W8 for <sip-http-events@core3.amsl.com>; Fri, 18 Dec 2009 03:55:06 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id E75313A6819 for <sip-http-events@ietf.org>; Fri, 18 Dec 2009 03:55:05 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id nBIBsjV29334 for <sip-http-events@ietf.org>; Fri, 18 Dec 2009 11:54:46 GMT
Received: from [127.0.0.1] ([47.17.25.99]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 18 Dec 2009 06:54:45 -0500
From: Scott Lawrence <scott.lawrence@nortel.com>
To: SIP HTTP Subscription Package <sip-http-events@ietf.org>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 18 Dec 2009 06:54:44 -0500
Message-Id: <1261137284.12725.5.camel@scott>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 (2.24.5-2.fc10)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Dec 2009 11:54:45.0841 (UTC) FILETIME=[E4998410:01CA7FD8]
Subject: [sip-http-events] Implementations or plans?
X-BeenThere: sip-http-events@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP HTTP Events <sip-http-events.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-http-events>, <mailto:sip-http-events-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-http-events>
List-Post: <mailto:sip-http-events@ietf.org>
List-Help: <mailto:sip-http-events-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-http-events>, <mailto:sip-http-events-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2009 11:55:06 -0000
If anyone has actually implemented this draft (or parts of it), or has plans to do so that they can share, please let me know (on list or off). This is for the report to the IESG and the wider IETF community as part of submitting this for publication as an RFC... For my part, I can report that this draft forms a key part of the SIP Forum User Agent Configuration Recommendation (currently in SIP Forum Last Call), and that I hope to have both client and server implementations of that Recommendation at the next SIPit.
- [sip-http-events] Implementations or plans? Scott Lawrence