[Dmsp] SigComp in IMS
"Engelsma Jonathan-QA2678" <Jonathan.Engelsma@motorola.com> Fri, 10 February 2006 16:02 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7ajC-0002HA-V4; Fri, 10 Feb 2006 11:02:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7ajB-0002Gi-J6 for dmsp@megatron.ietf.org; Fri, 10 Feb 2006 11:02:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01698 for <dmsp@ietf.org>; Fri, 10 Feb 2006 11:00:43 -0500 (EST)
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7aw5-000631-DB for dmsp@ietf.org; Fri, 10 Feb 2006 11:15:54 -0500
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k1AGGxuJ003842 for <dmsp@ietf.org>; Fri, 10 Feb 2006 09:16:59 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id k1AGGHt1010974 for <dmsp@ietf.org>; Fri, 10 Feb 2006 10:16:17 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Feb 2006 11:01:59 -0500
Message-ID: <6806C66D71ED9241BAECC0478173B71F515AA9@de01exm69.ds.mot.com>
Thread-Topic: SigComp in IMS
Thread-Index: AcYuW1Ms9mEb4sIgSAuMmj+cF18wLw==
From: Engelsma Jonathan-QA2678 <Jonathan.Engelsma@motorola.com>
To: dmsp@ietf.org
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Subject: [Dmsp] SigComp in IMS
X-BeenThere: dmsp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Multimodal Synchronization Protocol <dmsp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dmsp>
List-Post: <mailto:dmsp@ietf.org>
List-Help: <mailto:dmsp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dmsp>, <mailto:dmsp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0196829082=="
Sender: dmsp-bounces@ietf.org
Errors-To: dmsp-bounces@ietf.org
All, Just wanted to point out the reference I mentioned on our call regarding IMS requiring SigComp: 3GPP TS 24.229: IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3 (Release 5) With regard to the terminal (UE in IMS speak), see Section 8.1: "The UE shall support SigComp as specified in RFC 3320." With regard to the server, see Section 8.2: "The P-CSCF shall support SigComp as specified in RFC 3320." -jre
_______________________________________________ Dmsp mailing list Dmsp@ietf.org https://www1.ietf.org/mailman/listinfo/dmsp
- [Dmsp] SigComp in IMS Engelsma Jonathan-QA2678