Re: [rtcweb] Open data channel issues
Christer Holmberg <christer.holmberg@ericsson.com> Wed, 26 February 2014 22:21 UTC
Return-Path: <christer.holmberg@ericsson.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 3A5FA1A0763 for <rtcweb@ietfa.amsl.com>; Wed, 26 Feb 2014 14:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 pVnn9g0J2Usk for <rtcweb@ietfa.amsl.com>; Wed, 26 Feb 2014 14:21:42 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC031A072D for <rtcweb@ietf.org>; Wed, 26 Feb 2014 14:21:41 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-48-530e68f38ffa
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 6F.F5.04853.3F86E035; Wed, 26 Feb 2014 23:21:39 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.02.0387.000; Wed, 26 Feb 2014 23:21:38 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Open data channel issues
Thread-Index: AQHPMoOZ4jU/ikTW1ES5S7sUcSYm2ZrH4hIAgAAUIoCAABIhAIAAE9bQ
Date: Wed, 26 Feb 2014 22:21:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1BE0E0@ESESSMB209.ericsson.se>
References: <31B9253D-E826-4D07-A8A1-1B062B50F163@lurchi.franken.de> <530E4568.6090402@alum.mit.edu> <530E564B.9070103@jesup.org> <530E6580.4080804@alum.mit.edu>
In-Reply-To: <530E6580.4080804@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUyM+Jvje7nDL5ggxczzCxWbDjAarH2Xzu7 A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJXx7tZltoIDwhXrNnxkbGA8xt/FyMkhIWAi ceXSI0YIW0ziwr31bF2MXBxCAicYJR5sWMMI4SxhlPh54TdzFyMHB5uAhUT3P22QBhEBX4ne y+cYQcLCAnoSU86pQIT1JTZeWMYMYbtJ3L/TyA5iswioSlxZ1cACYvMCtXZ+n8UGYgsJLGWU 6F8nCGJzCuhI/JzxEuweRqB7vp9awwRiMwuIS9x6Mp8J4k4BiSV7zjND2KISLx//Y4WwlSQW 3f4MVa8jsWD3JzYIW1ti2cLXzBB7BSVOznzCMoFRdBaSsbOQtMxC0jILScsCRpZVjJLFqcXF uelGBnq56bkleqlFmcnFxfl5esWpmxiB0XJwy2+jHYwn99gfYpTmYFES573OWhMkJJCeWJKa nZpakFoUX1Sak1p8iJGJg1OqgZE7+q+O7Iry47Pn5ag+/e6SrzYvs1b715sv52+Gv/glNPeT SK7w3Ix9fROrAjQ+pC4pYZ6z4ajxTlPx6frzrxSFOsgLOtuJXF0ewzEx99w9R/HnG9wUE3Y8 VmdKOZJczNCjtv3fC5n3lZ37LW/2JEbt/R06R6c1iyPq9rKDvl/eFXJdmW9mG6vEUpyRaKjF XFScCACL6eSnZAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/LSzhTjg-E6SbAO-tvG_vcsYo_pc
Subject: Re: [rtcweb] Open data channel issues
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: Wed, 26 Feb 2014 22:21:44 -0000
Hi, >>> * Section 6.5 >>> >>> This section contains: >> >> Data channels can be opened by using internal or external >> negotiation. The details are out of scope of this document. >> >> A simple protocol for internal negotiation is specified in >> [I-D.ietf-rtcweb-data-protocol] and MUST be supported. >> >>> But internal and external negotiation are not defined in this document. >>> >> >> > I *thought* that internal negotiation was by definition negotiation >> by use of > rtcweb-data-protocol. >> (draft-ejzak-mmusic-data-channel-sdpneg-00 >> thinks so too, >> > but calls it "in-band negotiation".) There should be a good >> definition of these > terms, or reference to one. And more discussion >> if there can be other kinds of > internal negotiation. (If so, how >> would one be chosen?) >> >> Well, the text above says that ietf-rtcweb-data-protocol specifies an >> internal negotiation protocol, so it's not that far off. The split >> does allow someone to use an alternative negotiation protocol >> (internal or external). >> >> How about: >> >> Data channels can be opened by using negotiation within the SCTP >> association or external >> negotiation. External negotiation is defined as any method which >> results in an agreement >> as to the parameters of a channel and the creation thereof. >> The details are out of scope of this document. >> >> A simple protocol for negotiation within the SCTP association is >> specified in >> [I-D.ietf-rtcweb-data-protocol] and MUST be supported. >> >> Perhaps someone can wordsmith "external negotiation" better. > >ISTM the issue is that Internal vs. External isn't the key distinction. >What is key is that there is one method that MUST be *supported* but need not be the only one >used. Other mechanisms may be used. It doesn't really matter whether they are conducted >internally (over the SCTP association) or externally (anything else). I think the MUST-be-supported-method is a separate question. >E.g., I could use DCEP to establish one channel, and then use my own private protocol over that to >negotiate other channels. Would that be internal or external negotiation? Does it matter? I guess they would both be in-band methods. Maybe using in-band and out-of-band terminology would be more clear - and more aligned with existing terminology. Regards, Christer
- [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Magnus Westerlund
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Paul Kyzivat
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Paul Kyzivat
- Re: [rtcweb] Open data channel issues Christer Holmberg
- Re: [rtcweb] Open data channel issues Paul Kyzivat
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Stefan HÃ¥kansson LK
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Karl Stahl
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Justin Uberti
- Re: [rtcweb] Open data channel issues Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Michael Tuexen
- Re: [rtcweb] Open data channel issues Randell Jesup
- Re: [rtcweb] Open data channel issues Martin Thomson
- Re: [rtcweb] Open data channel issues Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] Open data channel issues Makaraju, Maridi Raju (Raju)