[AVT] Comments on draft-ietf-avt-mime-h224-02.txt
"kae" <k.hsueh@comcast.net> Wed, 03 August 2005 04:00 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0AQQ-00056I-Vy; Wed, 03 Aug 2005 00:00:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0AQO-00051x-3t for avt@megatron.ietf.org; Wed, 03 Aug 2005 00:00:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05504 for <avt@ietf.org>; Wed, 3 Aug 2005 00:00:08 -0400 (EDT)
Message-Id: <200508030400.AAA05504@ietf.org>
Received: from rwcrmhc13.comcast.net ([216.148.227.118] helo=rwcrmhc12.comcast.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0Awy-0000kr-Vq for avt@ietf.org; Wed, 03 Aug 2005 00:33:54 -0400
Received: from lining (pcp02403314pcs.reston01.va.comcast.net[68.84.10.31]) by comcast.net (rwcrmhc13) with SMTP id <2005080303173001500hvn3se>; Wed, 3 Aug 2005 03:17:30 +0000
From: kae <k.hsueh@comcast.net>
To: "'Even, Roni'" <roni.even@polycom.co.il>
Date: Tue, 02 Aug 2005 23:17:29 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcV7R/olOsc1rsf/QCK+/d+ny5Qk5AB78D3ABqfZ1pA=
In-Reply-To: <144ED8561CE90C41A3E5908EDECE315C01E9D703@IsrExch01.israel.polycom.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: 'IETF AVT WG' <avt@ietf.org>
Subject: [AVT] Comments on draft-ietf-avt-mime-h224-02.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
Roni, I am not sure if we should continue using Annex Q for FECC particular in SIP based systems. My concerns are: 1. Adding a new RTP stream will make NAT/FW traversal more difficult than it is today even with helps from ICE/STUN/TURN. 2. From security point of view, we do not want to open too many ports. In additions, FECC is general used a couple times during a video call. Most of time there are no packet flows. Most of NAT/FW will close the channel after 1 min of inactivity. 3. I think we should keep the principle that RTP is for medium not for control. If we allow non real time traffic to use RTP, it will make QoS more difficult. A lot of devices are marking DiffServ Code Point based on RTP. If we start to use RTP for non-real time stuff, QoS devices will have to look into payloads which is not scalable. (Please note that we cannot trust end point's DiffServ marking) 4. Using Annex Q/H.224, it makes certain architecture assumptions. I think the medium processing function and call control/feature functions should be separate either logically or physically. Given the fact that control paths do not use RTP. This draft will break this principle (except the case controller and media processor are physically the same) and ask the medium process to process FECC functions. Do you think it will be easier just send a SIP based message to the controller directly? This is my humble opions. Kae _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Comments on draft-ietf-avt-mime-h224-02.txt Magnus Westerlund
- [AVT] RE: Comments on draft-ietf-avt-mime-h224-02… Even, Roni
- [AVT] Re: Comments on draft-ietf-avt-mime-h224-02… Magnus Westerlund
- Re: [AVT] RE: Comments on draft-ietf-avt-mime-h22… Tom Taylor
- RE: [AVT] RE: Comments on draft-ietf-avt-mime-h22… Even, Roni
- RE: [AVT] RE: Comments on draft-ietf-avt-mime-h22… Even, Roni
- [AVT] Comments on draft-ietf-avt-mime-h224-02.txt kae
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… Even, Roni
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… Gunnar Hellstrom
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… kae
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… kae
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… Even, Roni
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… Even, Roni
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… kae
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… kae
- RE: [AVT] Comments on draft-ietf-avt-mime-h224-02… Gunnar Hellstrom