RE: [EME] SIP signalling and 3GPP

Paul Francis <francis@cs.cornell.edu> Mon, 16 July 2007 19:55 UTC

Return-path: <eme-bounces@irtf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAWfg-00059d-0B; Mon, 16 Jul 2007 15:55:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAWfe-00059W-AL for eme@irtf.org; Mon, 16 Jul 2007 15:55:50 -0400
Received: from mail-hub-2.cs.cornell.edu ([128.84.103.139] helo=exch-hub2.cs.cornell.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAWfa-0000Y9-1N for eme@irtf.org; Mon, 16 Jul 2007 15:55:50 -0400
Received: from exchfe1.cs.cornell.edu (128.84.97.33) by mail-hub.cs.cornell.edu (128.84.103.140) with Microsoft SMTP Server id 8.0.730.1; Mon, 16 Jul 2007 15:55:45 -0400
Received: from EXCHANGE2.cs.cornell.edu ([128.84.96.44]) by exchfe1.cs.cornell.edu with Microsoft SMTPSVC(6.0.3790.3959); Mon, 16 Jul 2007 15:55:40 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [EME] SIP signalling and 3GPP
Date: Mon, 16 Jul 2007 15:55:37 -0400
Message-ID: <E6F7A586E0A3F94D921755964F6BE006DAD036@EXCHANGE2.cs.cornell.edu>
In-Reply-To: <OFD2C272FC.396D66F6-ON8525731A.0061DD3C@notesgw.hns.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [EME] SIP signalling and 3GPP
Thread-Index: AcfH07zIbILTsnCBRP+IuUChfe1lrgAD3Rlw
From: Paul Francis <francis@cs.cornell.edu>
To: Gaguk Zakaria <gzakaria@hns.com>, <eme@irtf.org>
X-OriginalArrivalTime: 16 Jul 2007 19:55:40.0317 (UTC) FILETIME=[4936A4D0:01C7C7E3]
Received-SPF: None (mail-hub.cs.cornell.edu: francis@cs.cornell.edu does not designate permitted sender hosts)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc:
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Errors-To: eme-bounces@irtf.org

EME isn't the right place to discuss this (we are, for now anyway, designing
from scratch).

Presumably you need to ask someone in 3gpp itself...

PF 

> -----Original Message-----
> From: Gaguk Zakaria [mailto:gzakaria@hns.com] 
> Sent: Monday, July 16, 2007 2:04 PM
> To: eme@irtf.org
> Subject: [EME] SIP signalling and 3GPP
> 
> 
> Hi
> I have question regarding SIP signalling and its application 
> at 3gpp IMS 
> 1. In almost all examples in the 3GPP doc regarding SIP 
> signalling, when a UA sends an INVITE message, the called 
> party usually replies it with a provisional response 183 
> Session Progress.   My question is that if the INVITE message 
> consists of only ONE media type, meaning there is no need of 
> media negotiation,  does the called party still need to reply 
> it with 183 Session Progress. Can the called party just reply 
> with 200 OK or nor acceptable? 
> 2.  Does the P-CSCF require the arrival of 183 Session 
> Progress message, as the provisional response of the INVITE, 
> to authorize reource (authorize QoS). Can P-CSCF authorize 
> resource (QoS) based on the INVITE message if the INVITE 
> message consists of only one media type. 
> 
> Gaguk 
> 
> 

_______________________________________________
EME mailing list
EME@irtf.org
https://www1.ietf.org/mailman/listinfo/eme