Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-07.txt - Some editorial comments on section 5

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 11 February 2014 18:12 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 40FB81A0696 for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 10:12: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 u-R0oUludGqM for <rtcweb@ietfa.amsl.com>; Tue, 11 Feb 2014 10:12:43 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 6E2661A0694 for <rtcweb@ietf.org>; Tue, 11 Feb 2014 10:12:42 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-42-52fa68188d6b
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 5F.2F.04853.8186AF25; Tue, 11 Feb 2014 19:12:41 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0387.000; Tue, 11 Feb 2014 19:12:40 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-07.txt - Some editorial comments on section 5
Thread-Index: Ac8nU+WsE4W5K/avTLyRu1AtQ1+x3g==
Date: Tue, 11 Feb 2014 18:12:39 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D16D2A3@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPLMWRmVeSWpSXmKPExsUyM+Jvja5kxq8gg5mz+S3W/mtnd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxuIflxgLFvNWLJ6xlqmBsZOri5GTQ0LAROLywc/MELaYxIV7 69m6GLk4hAROMEpMOrGRGcJZzChx810rSxcjBwebgIVE9z9tkAYRAXWJyw8vsIPYwgIFEivv fmAHKRERKJR4MjsQokRPom3CSiYQm0VAVWJVywUWEJtXwFdiyeLtrCA2I9De76fWgNUwC4hL 3HoynwniHgGJJXvOQ90mKvHy8T9WCFtJ4seGSywQ9ToSC3Z/YoOwtSWWLXzNDDFfUOLkzCcs ExiFZyEZOwtJyywkLbOQtCxgZFnFKFmcWlycm25koJebnluil1qUmVxcnJ+nV5y6iREY6Ae3 /DbawXhyj/0hRmkOFiVx3uusNUFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGAVlTPU9Zu1e te/uhTLLWJZ+x57p4l/855/7vFPlVKeE/slzadlWpw5f5V6j6fh6fklZgaVM2vOVLIoLglUt d1vM8nKfrsLT5HPfvuxfbnBK5stf9nY31sSwHfYQVzvIe7v57PEFmepqNY4OYiwJ5ZI7Cw3X /9l5PeZcQ8TU5CcLvP0cEj25lViKMxINtZiLihMB8/uUhEICAAA=
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-channel-07.txt - Some editorial comments on section 5
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: Tue, 11 Feb 2014 18:12:44 -0000

Hi,

Some editorial comments:

Q1:

Section 5 says:

	"SCTP as specified in [RFC4960] MUST be used in
   	combination with the extension defined in [RFC3758] and provides the
   	following interesting features for transporting non-media data
   	between browsers:"

I suggest to say:

	"The SCTP extension defined in [RFC3758] MUST be supported, and
     	provides the following features:


Q2:

Section 5 says:

	"Each SCTP user message contains a so called Payload Protocol
   	Identifier (PPID) that is passed..."

I suggest to remove "so called".


Q3:

Section 5 says:

	"This value can be used to multiplex multiple protocols
   	over a single SCTP association.  The sender provides for each
   	protocol a specific PPID and the receiver can demultiplex the
   	messages based on the received PPID."

I think we discussed this earlier. The PPID value CAN NOT (at least not as used by WebRTC) be used to multiplex multiple protocols over a single SCTP association. If you create multiple channels, for multiple protocols, the same PPID values may be used for each protocol.

 The PPID CAN, however, be used within a data channel, e.g. to demultiplex the DCP from channel data.


Q4:

Section 5 says:

	"When using DTLS as the lower layer, only single homed SCTP
   	associations MUST be used, since DTLS does not expose any address
   	management to its upper layer."

I suggest to change "MUST be used" to "are supported".


Q5:

Sometimes you say "SCTP" and sometimes "SCTP as defined in [RFC4960]".

I suggest to e.g. use the reference on the first occurrence, and then only use "SCTP".


Regards,

Christer