Re: [Sipping] Liaison Statement on offer/answer procedures

Paul Kyzivat <pkyzivat@cisco.com> Thu, 08 May 2008 15:32 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB5883A728B; Thu, 8 May 2008 08:32:15 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D94A23A7246 for <sipping@core3.amsl.com>; Thu, 8 May 2008 08:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.834
X-Spam-Level:
X-Spam-Status: No, score=-5.834 tagged_above=-999 required=5 tests=[AWL=0.765, 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 vxbIk-Pk+2vr for <sipping@core3.amsl.com>; Thu, 8 May 2008 08:32:09 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id AB98728D25F for <sipping@ietf.org>; Thu, 8 May 2008 06:52:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,454,1204531200"; d="scan'208";a="25862643"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 08 May 2008 05:49:57 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m48CnvZE020990; Thu, 8 May 2008 05:49:57 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m48CnvL3023142; Thu, 8 May 2008 12:49:57 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 May 2008 08:49:57 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 May 2008 08:49:56 -0400
Message-ID: <4822F717.7030903@cisco.com>
Date: Thu, 08 May 2008 08:50:31 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <4822983A.2090906@ericsson.com>
In-Reply-To: <4822983A.2090906@ericsson.com>
X-OriginalArrivalTime: 08 May 2008 12:49:56.0753 (UTC) FILETIME=[04BFD810:01C8B10A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1498; t=1210250997; x=1211114997; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sipping]=20Liaison=20Statement=20on=20 offer/answer=20procedures |Sender:=20; bh=+lBBaRtWxT5lEmEii2N8FFVnqQ0tOhOGZzNS2gJMgSM=; b=EBd1OdpmKezZcbsJTNomYHIc7iDoigfLrVck0AAdTw7xhzWwSUV3IObpqD wkktYoY2bQZD3EiBR7Xau2nQphFpSdTpwUPdFr0dPH+mXilgKXcPw+DVgslJ r3i++xHO6o;
Authentication-Results: sj-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: mmusic-chairs@tools.ietf.org, sipping <sipping@ietf.org>, Mary Barnes <mary.barnes@nortel.com>
Subject: Re: [Sipping] Liaison Statement on offer/answer procedures
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

I agree that sipping is the right place for the work, and that it ought 
to be done, eventually. It hasn't seemed like especially pressing, but 
apparently 3gpp thinks otherwise.

I agree that, at least on the surface, it is less important which 
solution is chosen than it is that *some* solution be chosen. But there 
are pros and cons to the two obvious approaches, so it is best to do 
more than just flip a coin.

	Thanks,
	Paul

Gonzalo Camarillo wrote:
> Folks,
> 
> the SIPPING WG has received the following LS from 3GPP:
> 
> https://datatracker.ietf.org/liaison/444/
> 
> We have talked to the MMUSIC chairs (MMUSIC was in the cc: of this LS) 
> and they are OK with working on this LS in SIPPING. In any case, we will 
> send our answer to the MMUSIC folks for comments before getting back to 
> 3GPP.
> 
> This LS has to do with the offer/answer method, which was developed by 
> MMUSIC, but is also related to the SIP machinery associated to 
> offer/answer (i.e., rejected re-INVITEs). That is why we consider 
> SIPPING the right place to discuss it.
> 
> Comments on this LS are appreciated.
> 
> Thanks,
> 
> Gonzalo
> SIPPING co-chair
> _______________________________________________
> Sipping mailing list  https://www.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
> 
_______________________________________________
Sipping mailing list  https://www.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