[rtcweb] I-D Action: draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt - the data channel's state and the SCTP association
"Liuyan (Scarlett)" <scarlett.liuyan@huawei.com> Mon, 17 February 2014 11:30 UTC
Return-Path: <scarlett.liuyan@huawei.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 303761A03D3 for <rtcweb@ietfa.amsl.com>; Mon, 17 Feb 2014 03:30:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level:
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2tAyz0Pa9hl for <rtcweb@ietfa.amsl.com>; Mon, 17 Feb 2014 03:30:31 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 000AD1A0125 for <rtcweb@ietf.org>; Mon, 17 Feb 2014 03:30:30 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDR06528; Mon, 17 Feb 2014 11:30:28 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 11:30:14 +0000
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 17 Feb 2014 11:30:19 +0000
Received: from SZXEMA503-MBX.china.huawei.com ([169.254.5.104]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Mon, 17 Feb 2014 19:30:08 +0800
From: "Liuyan (Scarlett)" <scarlett.liuyan@huawei.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt - the data channel's state and the SCTP association
Thread-Index: AQHPK9Oc/rbk1aaTTk+rVISc1Uc90g==
Date: Mon, 17 Feb 2014 11:30:08 +0000
Message-ID: <E97C33E5D67C2843AFA535DE2E5B80C157392931@SZXEMA503-MBX.china.huawei.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1730E7@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1730E7@ESESSMB209.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.137.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/EacSR8ovoF-YZMevCiugx8OYMrs
Subject: [rtcweb] I-D Action: draft-ejzak-dispatch-webrtc-data-channel-sdpneg-00.txt - the data channel's state and the SCTP association
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 17 Feb 2014 11:30:33 -0000
Hi, Section 5.5.2 does say: "o As described in Section 4.2.2, if the SCTP association is not yet established, then the newly created data channels are in the Connecting state, else if the SCTP association is already established, then the newly created data channels are in the Open state." ..... It is not clear that if the SCTP association is failed to establish, how to we deal with the newly created data channels. Furthermore, how long the valid duration of the connecting state of the newly created data channels are before the SCTP association has not yet established ? Section 5.5.3 does say: "5.2.3. Closing a data channel When the application requests the closing of a data channel that was externally negotiated, the browser always performs an in-band SSN reset for this channel. It is specific to the sub-protocol whether this closing must in addition be signaled to the peer via a new SDP offer/answer exchange. The application must also close any data channel that was externally negotiated, for which the stream identifiers are not listed in an incoming SDP offer." ... When there are multiple data channels with different sub-protocol per a SCTP association, Maybe it needs to identify how to close a single data channel, how to close all data channels with the same sub-protocol and how to close a SCTP association. Of course, closing a SCTP association can just set SCTP port number zero.:-) Regards, Scarlett _______________________________________________ rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-0… Christer Holmberg
- [rtcweb] I-D Action: draft-ejzak-dispatch-webrtc-… Liuyan (Scarlett)
- Re: [rtcweb] I-D Action: draft-ejzak-dispatch-web… Richard Ejzak
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-0… Justin Uberti
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-0… Christer Holmberg
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-0… Justin Uberti
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-jsep-0… Christer Holmberg