Re: [rtcweb] Comments on draft-ietf-rtcweb-data-protocol-03 - Protocol IANA registration information
Christer Holmberg <christer.holmberg@ericsson.com> Mon, 24 February 2014 20:07 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 7A2E81A02B6 for <rtcweb@ietfa.amsl.com>; Mon, 24 Feb 2014 12:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 FCLBNJG08jGz for <rtcweb@ietfa.amsl.com>; Mon, 24 Feb 2014 12:07:43 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 31FC11A02AD for <rtcweb@ietf.org>; Mon, 24 Feb 2014 12:07:43 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-23-530ba68d84d6
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 23.B9.04249.D86AB035; Mon, 24 Feb 2014 21:07:41 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0387.000; Mon, 24 Feb 2014 21:07:40 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [rtcweb] Comments on draft-ietf-rtcweb-data-protocol-03 - Protocol IANA registration information
Thread-Index: Ac8xnA0wyaOYJez3T5i7IuW8nBbppw==
Date: Mon, 24 Feb 2014 20:07:41 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1B59BB@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: fi-FI
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUyM+JvjW7vMu5ggym7zS0uNi1htFix4QCr xdp/7ewOzB5/339g8liy5CeTx4aWHUwBzFFcNimpOZllqUX6dglcGcuv9DEW/GOteHFuPmsD 4yOWLkZODgkBE4mvz3+wQ9hiEhfurWfrYuTiEBI4wijRtv8PI4SzhFHiZ2sbaxcjBwebgIVE 9z9tkAYRgViJy583sIHYzALqEncWnwMbJCyQL/Gw7Tg7RE2BxIyjp9ggbD2JM7ebmEHGsAio SnxYpg4S5hXwlVi+dzZYCSPQDd9PrWGCGCku8eHgdWaI2wQkluw5D2WLSrx8/I8VwlaSWHt4 OwtEvY7Egt2foM7Rlli28DUzxHxBiZMzn7BMYBSZhWTsLCQts5C0zELSsoCRZRUjR3FqcVJu upHBJkZgHBzc8ttiB+PlvzaHGKU5WJTEeT++dQ4SEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnV wOi6uHXttTXTZgYvlTVKk7/ZuzG8+J/AxKUB/0rY8883ZTjFPf19kFnAr2FBpivvqUVvYi8m BnUWN51iLBL8nVDKYx75REd7dryCdMIG9aMF+s2O91n07rzhYY7RXVu746PxnsqpSbGOLySq z+VsDamcUvG71ntxqaSVhUF6sOXcytMVn6wTlViKMxINtZiLihMBrMiLglECAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/-gjHxa33Sfi4hkVKr2UIDoUfR9Y
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Comments on draft-ietf-rtcweb-data-protocol-03 - Protocol IANA registration information
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, 24 Feb 2014 20:07:45 -0000
Hi, >> * Section 8.4: >> >> ISTM there ought to be a template of the minimum information that the >> specification for a registered (sub)protocol MUST (SHOULD?) include. >> E.g., >> >> - what Channel Type(s) are valid for this (sub)protocol >> I assumed all... >> - A contact for more information about this protocol > You need to provide a reference for the protocol. Isn't that enough? The question is what information that reference needs to contain. For example, if a protocol requires reliability, the reference needs to specify that a reliable data channel must be opened. The protocol may also define procedures regarding who is responsible for opening the data channel. Etc etc etc. Regards, Christer
- Re: [rtcweb] Comments on draft-ietf-rtcweb-data-p… Christer Holmberg