[rtcweb] 答复: RTP Usage: Is RTP Retransmission REQUIRED or RECOMMENDED

Lishitao <lishitao@huawei.com> Thu, 05 July 2012 02:42 UTC

Return-Path: <lishitao@huawei.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741ED11E808D for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 19:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.879
X-Spam-Level: ***
X-Spam-Status: No, score=3.879 tagged_above=-999 required=5 tests=[AWL=-2.543, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, CN_BODY_509=0.029, CN_BODY_832=0.004, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9y2GVCfrL5gU for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 19:42:07 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE4211E8073 for <rtcweb@ietf.org>; Wed, 4 Jul 2012 19:42:03 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHL19791; Wed, 04 Jul 2012 22:42:15 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Jul 2012 19:40:45 -0700
Received: from SZXEML440-HUB.china.huawei.com (10.72.61.75) by dfweml408-hub.china.huawei.com (10.193.5.134) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 4 Jul 2012 19:40:42 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.243]) by SZXEML440-HUB.china.huawei.com ([10.72.61.75]) with mapi id 14.01.0323.003; Thu, 5 Jul 2012 10:40:39 +0800
From: Lishitao <lishitao@huawei.com>
To: Roman Shpount <roman@telurix.com>, "Olle E. Johansson" <oej@edvina.net>
Thread-Topic: [rtcweb] RTP Usage: Is RTP Retransmission REQUIRED or RECOMMENDED
Thread-Index: AQHNVVdzkH+KQgSjwk+Xd9991iicxZcQVB2AgACOBACABDhPgIAA1GGAgAC75ACAAhMTgIAAC1yAgAA/nICAAPfqgA==
Date: Thu, 05 Jul 2012 02:40:39 +0000
Message-ID: <DA165A8A2929C6429CAB403A76B573A5146743F4@szxeml534-mbx.china.huawei.com>
References: <4FEAB80A.7040207@ericsson.com> <4E5389B4-F54C-4060-952E-8319A801FDC3@iii.ca> <4FED4E81.7000607@ericsson.com> <B7F8286E-BDB0-4033-991C-A54A0A1227EB@iii.ca> <A8D45DD6-4E82-413F-8978-C6A80B2806DA@edvina.net> <CAOJ7v-1SwvqDrzOGGSwFjkmnqPmF8PVvbOoGrtbtx6qk2T_R-w@mail.gmail.com> <208EC80D-D101-43CC-9ED7-5BA3E2F39A87@edvina.net> <CAD5OKxtyMr4Z-g+o3WwuWULNRhWjSnPspWVX53cTkivE99UoVA@mail.gmail.com> <190327B0-72B8-4F9C-8A37-D932A2871879@edvina.net> <CAD5OKxszD1ia=8SwH0fSFDatfQxAMQ500y7ZYBhXqGgNSj28nA@mail.gmail.com>
In-Reply-To: <CAD5OKxszD1ia=8SwH0fSFDatfQxAMQ500y7ZYBhXqGgNSj28nA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.73.39]
Content-Type: multipart/related; boundary="_004_DA165A8A2929C6429CAB403A76B573A5146743F4szxeml534mbxchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [rtcweb] 答复: RTP Usage: Is RTP Retransmission REQUIRED or RECOMMENDED
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 02:42:08 -0000

I got some questions about this RTP Retransmission staff, is there a capability negotiation mechanism provided in RTP Retransmission, like negotiate the capability in the first offer/answer transition. (I don’t find that in the documents, or if I miss somewhere)



I also find  in RFC 4588, it mentioned that there are two ways for Retransmission, one is Session-Multiplexing, another is SSRC-Multiplexing, does those two mechanism both need to be supported for implementation?



Regards

shitao



________________________________

华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]

Phone:
Fax:
Mobile:
Email:
地址:深圳市龙岗区坂田华为基地 邮编:518129
Huawei Technologies Co., Ltd.
Bantian, Longgang District,Shenzhen 518129, P.R.China
http://www.huawei.com
________________________________
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中
的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
发件人: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] 代表 Roman Shpount
发送时间: 2012年7月5日 3:40
收件人: Olle E. Johansson
抄送: rtcweb@ietf.org
主题: Re: [rtcweb] RTP Usage: Is RTP Retransmission REQUIRED or RECOMMENDED


On Wed, Jul 4, 2012 at 11:52 AM, Olle E. Johansson <oej@edvina.net<mailto:oej@edvina.net>> wrote:

4 jul 2012 kl. 17:11 skrev Roman Shpount:

>
> I think this train left the station long time ago. WebRTC is not going to interoperate with anything of significance currently deployed in SIP world. Between DTLS-SRTP, ICE, AVPF and now RTP retransmissions you will need an application layer gateway. I guess the overall hope is that SIP implementations will catch up implementing features required to work with WebRTC in the future and gateways would be acceptable for current implementations.
Doesn't that mean that the IETF work on SIP over websockets will not lead anywhere?

Unless we have a SIP end point that supports DTLS-SRTP  and ICE, understands AVPF profile, and knows how to negotiate RTP retransmissions and other RTP extensions, then I would say SIP over websockets will not help in communications between SIP and WebRTC. There are a few SIP endpoints that claim to support some of those specifications, but anything massively deployed in real life, like IP phones, PBXs, SBCs, PSTN gateways, and soft-phones,  almost universally do not support or use any of those standards.

SIP over websockets might be useful on its own though, for instance as a replacement for SIP-outbound, which fails to address even basic operational requirements for SIP clients behind NAT. Hopefully though, WebRTC will replace SIP on the client, and will remove the need for SIP behind NAT support altogether, making SIP over websockets completely irrelevant.
_____________
Roman Shpount