[sip] Comment to draft-agrawal-sip-h323-interworking-reqs-06.txt about text support
"Gunnar Hellstrom" <gunnar.hellstrom@omnitor.se> Sat, 28 February 2004 23:24 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10241 for <sip-archive@odin.ietf.org>; Sat, 28 Feb 2004 18:24:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxDom-0001OG-DH for sip-archive@odin.ietf.org; Sat, 28 Feb 2004 18:24:25 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1SNOOBe005284 for sip-archive@odin.ietf.org; Sat, 28 Feb 2004 18:24:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AxDoP-0001Lu-Pg; Sat, 28 Feb 2004 18:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwpTM-0006bu-Vi for sip@optimus.ietf.org; Fri, 27 Feb 2004 16:24:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25248 for <sip@ietf.org>; Fri, 27 Feb 2004 16:24:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwpTL-0000ET-00 for sip@ietf.org; Fri, 27 Feb 2004 16:24:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwpSO-000090-00 for sip@ietf.org; Fri, 27 Feb 2004 16:23:40 -0500
Received: from mail3.pi.se ([195.7.64.137] ident=root) by ietf-mx with esmtp (Exim 4.12) id 1AwpRp-00003F-00; Fri, 27 Feb 2004 16:23:06 -0500
Received: from vit (h161n2fls31o265.telia.com [217.208.189.161]) (authenticated (0 bits)) by mail3.pi.se (8.12.10/8.11.2) with ESMTP id i1RLKlQe009566; Fri, 27 Feb 2004 22:20:49 +0100 (CET)
From: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
To: sip@ietf.org, Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Cc: Toip list <toip@snowshore.com>, "'Sipping@Ietf. Org'" <sipping@ietf.org>
Subject: [sip] Comment to draft-agrawal-sip-h323-interworking-reqs-06.txt about text support
Date: Fri, 27 Feb 2004 22:22:48 +0100
Message-ID: <BHEHLFPKIPMLPFNFAHJKMEMLDLAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mail3.pi.se id i1RLKlQe009566
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
In section 6.1.5 of the sip-h323-interworking spec, there is a sentence: "The IWF SHOULD be able to map the common audio, video and application format names supported in H.323 to and from the equivalent RTP/AVP [RFC3550] names." It is good practice to always mention how the three main media of video, audio and text shall be handled in real time applications. audio and video are mentioned explicitly. It may not be evident to everybody that real time interactive text is capability declared in H.323 Annex G / H.245 by DataApplicationCapability.application = t140 So, in fact it is covered in the sentence requiring that "application" format namnes shall be mapped. The mapping should correspond to the RTP/AVP name text/t140 and corresponding names for inclusion of protection against loss. I seek your guidance how it can be made more clear that "text" capabilities can be expressed in both H.323 and SIP systems and should be mapped. ( the spec is at http://www.ietf.org/internet-drafts/draft-agrawal-sip-h323-interworking-reqs -06.txt ) Regards Gunnar ------------------------------------------- Gunnar Hellström Omnitor AB Renathvägen 2 SE 121 37 Johanneshov SWEDEN +46 8 556 002 03 Mob: +46 708 204 288 www.omnitor.se Gunnar.Hellstrom@Omnitor.se -------------------------------------------- _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [sip] Comment to draft-agrawal-sip-h323-interwork… Gunnar Hellstrom