RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4

"Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se> Wed, 29 December 2004 08:52 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20230 for <sipping-web-archive@ietf.org>; Wed, 29 Dec 2004 03:52:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjZkP-0008M6-0g for sipping-web-archive@ietf.org; Wed, 29 Dec 2004 04:04:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CjZY8-0002Dz-CU; Wed, 29 Dec 2004 03:51:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CjZVJ-0001cA-7l for sipping@megatron.ietf.org; Wed, 29 Dec 2004 03:48:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19704 for <sipping@ietf.org>; Wed, 29 Dec 2004 03:48:23 -0500 (EST)
Received: from mail3.pi.se ([195.7.64.137] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjZgO-00086r-5x for sipping@ietf.org; Wed, 29 Dec 2004 03:59:52 -0500
Received: from vit (136.240.13.217.in-addr.dgcsystems.net [217.13.240.136]) (authenticated (0 bits)) by mail3.pi.se (8.12.10/8.11.2) with ESMTP id iBT8m95p025933; Wed, 29 Dec 2004 09:48:10 +0100 (CET)
From: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
To: IETF Sipping <sipping@ietf.org>, Peter Ridler <ridler@softrac.ca>
Subject: RE: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
Date: Wed, 29 Dec 2004 09:48:20 +0100
Message-ID: <GHEPIJKACEKDGLKODIGJEELDDMAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <BAYC1-PASMTP040A545B270EFD4E6085A5ED9A0@cez.ice>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: 7bit
Cc: Toip list <toip@snowshore.com>
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>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit

Peter,
I am glad you are looking at details of sipping-toip.

The figure 1000 in the sdp line
>      a=rtpmap:98 t140/1000
is indeed a clock rate.

You can read more about it in:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2793bis-09.txt
Where some requirements are stated for handling the timestamps.

Even if it has little meaning for a text packet where text characters are stored at the
moment they are created rather than by being sampled, we did not want to deviate from
normal RTP usage of that parameter.

The clock is used for setting the timestamp of the text packets, and for calculation of
time offset for redundant text, and can thus be used if there is a desire to time the
display of characters.

------

Do you see a need for negotiation of the transmission interval?

Regards

Gunnar

-------------------------------------------
Gunnar Hellstrom
Omnitor AB
Renathvagen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
--------------------------------------------


>-----Original Message-----
>From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org]On
>Behalf Of Peter Ridler
>Sent: Tuesday, December 28, 2004 6:08 PM
>To: IETF Sipping
>Subject: [Sipping] draft-ietf-sipping-ToIP-00 - Section 8.4
>
>
>Hi,
>
>In section 8.4 of this draft states::
>
>--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
>
>Text capability SHOULD be announced in SDP by a declaration in
>line with this example:
>
>      m=text 11000 RTP/AVP 98 100
>      a=rtpmap:98 t140/1000
>      a=rtpmap:100 red/1000
>      a=fmtp:100 98/98/98
>
>Characters SHOULD BE buffered for transmission and transmitted
>every 300 ms.
>
>--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--.--
>
>On SDP line 2 (a=rtpmap:98 t140/1000) what does the 1000 stand for?
>
>Nominally it is the clock rate.  If just a filler, could it be the
>Timeout value i.e. 1000 = 1000ms or better yet (a=rtpmap:98 t140/300)
>300 = 300ms timeout value?
>
>Thanks
>Peter
>
>
>
>_______________________________________________
>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
>



_______________________________________________
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