Re: Status of SIPPING App Interaction Framework (Re: [Sipping] SIPPING WG Status)

Jonathan Rosenberg <jdrosen@cisco.com> Fri, 20 July 2007 21:45 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IC0IN-0006NH-Fi; Fri, 20 Jul 2007 17:45:55 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1IC0IM-0006Mv-NS for sipping-confirm+ok@megatron.ietf.org; Fri, 20 Jul 2007 17:45:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IC0IM-0006Mn-Df for sipping@ietf.org; Fri, 20 Jul 2007 17:45:54 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IC0IK-0000TK-V1 for sipping@ietf.org; Fri, 20 Jul 2007 17:45:54 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 20 Jul 2007 14:45:34 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CALXJoEarR7MV/2dsb2JhbAA
X-IronPort-AV: i="4.16,564,1175497200"; d="scan'208"; a="387214251:sNHT2682290662"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l6KLjY6J030126; Fri, 20 Jul 2007 14:45:34 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6KLjYA0022809; Fri, 20 Jul 2007 21:45:34 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Jul 2007 14:45:34 -0700
Received: from [10.32.241.147] ([10.32.241.147]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Jul 2007 14:45:33 -0700
Message-ID: <46A12D04.6010906@cisco.com>
Date: Fri, 20 Jul 2007 17:45:40 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: peter_blatherwick@mitel.com
Subject: Re: Status of SIPPING App Interaction Framework (Re: [Sipping] SIPPING WG Status)
References: <OF41182805.19D7D469-ON8525731E.00565AE4-8525731E.0056F812@mitel.com>
In-Reply-To: <OF41182805.19D7D469-ON8525731E.00565AE4-8525731E.0056F812@mitel.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jul 2007 21:45:33.0739 (UTC) FILETIME=[4CD9FFB0:01C7CB17]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1120; t=1184967934; x=1185831934; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20Re=3A=20Status=20of=20SIPPING=20App=20Interaction=20Framework =20(Re=3A=20[Sipping]=20SIPPING=0A=20WG=09Status) |Sender:=20; bh=Wf/0MCnFwItBQ+wr6tVp33SB5d/WgGBVCNIa+51tJ/w=; b=CPexIjEN9nkcZ6lQ7s5BcGkBI0qbgFwLwSGN/gu4PNnsyCuwLnhJNW0ojott6aVOpMRAsKuY P22oELRwSjEia1zYX6wGKsufrND7S2ZfaYMqBaNn0V2XLHMratKqRYNbWzwFQYL4VRxM+HM1Oo lNGzxIio7DYSrCXbDtJGDLCZE=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: sipping@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

inline.

peter_blatherwick@mitel.com wrote:
> 
> Hi,
> 
> I'd like to understand the status of the App Interaction Framework doc. 
>  Most recent I believe is 
> draft-ietf-sipping-app-interaction-framework-05.   According to the I-D 
> Tracker tool, the spec is in the RFC Editor's queue, meaning it is up 
> for publication.  Given most recent rev is 2005, this seems odd. 
>  According to RFC Editors Queue, it appears to be waiting for a 
> dependency on SIP GRUU, which in turn I believe is near completion (now 
> in IESG Last Call).   Correct?  

Yes. Its been sitting waiting on GRUU for a LOOOONNNNGGG time.

> 
> So, is it safe to assume that once GRUU completes, that the App 
> Interaction Framework will also go to RFC in short order?  

Yes.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP