Re: [rtcweb] draft-jesup-rtcweb-data-00 posted

Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 25 October 2011 08:02 UTC

Return-Path: <HKaplan@acmepacket.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 E48C121F8AEA for <rtcweb@ietfa.amsl.com>; Tue, 25 Oct 2011 01:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599]
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 Yn-bdBd+3JNu for <rtcweb@ietfa.amsl.com>; Tue, 25 Oct 2011 01:02:49 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 4897121F8AE9 for <rtcweb@ietf.org>; Tue, 25 Oct 2011 01:02:49 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 25 Oct 2011 04:02:48 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Tue, 25 Oct 2011 04:02:48 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Randell Jesup <randell-ietf@jesup.org>
Thread-Topic: [rtcweb] draft-jesup-rtcweb-data-00 posted
Thread-Index: AQHMkux7p3eML1qZxUCx8kT0lNDE/g==
Date: Tue, 25 Oct 2011 08:02:47 +0000
Message-ID: <D3C41C1C-3586-4A22-8040-C7F0E22B41A7@acmepacket.com>
References: <4EA5EA46.1010803@jesup.org>
In-Reply-To: <4EA5EA46.1010803@jesup.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7D336C06A696F04994A4A5AD6FCD8F9D@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] draft-jesup-rtcweb-data-00 posted
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: Tue, 25 Oct 2011 08:02:50 -0000

Hi Randell,
What do you think about the following additional requirements:

Req. 7: Data streams MUST provide fragmentation at a layer above UDP, such that IP-layer fragmentation does not occur no matter how large a message/buffer the Javascript application passes down to the Browser to be sent out.

Req. 8: The data stream transport protocol MUST NOT encode IP addresses inside its protocol fields; doing so reveals potentially private information, and leads to failure if the address is depended upon. 

Req. 9: The data stream protocol SHOULD support unbounded-length "messages" (i.e., a virtual socket stream) at the application layer, for such things as image-file-transfer; or else it MUST support at least a maximum application-layer message size of 4GB.

Req. 10: The data stream packet format/encoding MUST be such that it is impossible for a malicious Javascript to generate an application message crafted such that it could be interpreted as a native protocol over UDP - such as UPnP, RTP, SNMP, STUN, etc. 


I believe SCTP can do 7+8+9 the above if its options are chosen right, and of course TCP can.
And I'm guessing DTLS will satisfy 10 above, as would websockets-style masking.

-hadriel


On Oct 24, 2011, at 6:44 PM, Randell Jesup wrote:

> A new version of I-D, draft-jesup-rtcweb-data-00.txt has been successfully submitted by Randell Jesup and posted to the IETF repository.
> 
> Filename:	 draft-jesup-rtcweb-data
> Revision:	 00
> Title:		 RTCWeb Datagram Connection
> Creation date:	 2011-10-25
> WG ID:		 Individual Submission
> Number of pages: 11
> 
> Abstract:
>   This document investigates the possibilities for designing a generic
>   transport service that allows Web Browser to exchange generic data in
>   a peer to peer way.  Different transport protocols and their
>   properties are investigated in order to identify the most appropriate
>   one.
> 
> 
> URL:  http://www.ietf.org/id/draft-jesup-rtcweb-data-00.txt
> 
> -- 
> Randell Jesup
> randell-ietf@jesup.org
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb