Re: [rtcweb] Non-media data service consensus and requirements

[Cullen Jennings <[e-mail]>]

On Jun 27, 2011, at 1:36 AM, Magnus Westerlund wrote:
> 
> Does anyone like to add additional use cases?

BFCP 

I'm interested in the use cases that have real time requirements and latency is an issue.

> 
> 
> Are you supporting the inclusion of a unreliable datagram service
> directly between peers?
yes

> Please provide your view and any additional
> statements of motivation that you desire to provide.
> 
> Secondly, there is a question if there needs to have something that
> provides reliable message (of arbitrary size) or byte stream oriented
> data transport between the peers.
I don't have a big need for this but don't have a problem with it if others need it 

> I personally foresee that people will
> build JS libraries for this on top of a unreliable datagram service. If
> you desire reliable data service as part of the standardized solution
> please provide motivation and use case and requirements.
> 
> I also want to take a stab on what I personally see as the requirements
> that exist on unreliable datagram service in the context of RTCWEB.
> 
> - Unreliable data transmission
+1 

> - Datagram oriented
>   * Size limited by MTU
>     - Path MTU discovery needed
+1

>   * Fragmentation by the application
+1

> - Low latency, i.e. Peer to Peer preferable
+5

> - Congestion Controlled, to be
>   * Network friendly
+1
>   * Not become a Denial of Service tool
+1

> - Security
>  * Confidentiality
+1
>  * Integrity Protected
+1
>  * Source Authenticated (at least bound to the signalling peer)
+1 - I might phrase this a bit differently but I think we are getting at the same thing. If we are going to have encryption, there no point in encrypting something if you have no idea you our sending encrypted data to and from. We need some sort of identity / autehntication

>  * Ensure consent to receive data
+5

In addition to your, I'd like to add that I am trying to maximize the odds of it making though the various NATs and Firewalls involved with and enterprise or home user. 

Cullen in my individual contributor role.