Re: [rtcweb] ALPN question - other labels?

[Paul Kyzivat <[e-mail]>]

On 8/7/14 10:41 PM, Martin Thomson wrote:
>
> On Aug 7, 2014 7:25 PM, "Paul Kyzivat" <[e-mail]
> <mailto:[e-mail]>> wrote:
>  > My primary question is how is a browser expected to behave if some
> other label is offered? Will it still support use of the JSEP APIs?
>
> ALPN requires that a peer in the server role reject the connection if it
> can't select a protocol. That is what Firefox will do, though it will
> tolerate no ALPN extension as long as it doesn't have confidential media.

Are you saying that the offering and acceptance of ALPN values is 
controlled totally by the browser, without any influence by the JS app?

>  > And, for interop reasons, will there be a way to get a browser to
> offer another label and still support the JSEP APIs if the other end
> accepts it?
>
> That is an interesting question. You would need to teach the browser
> that other protocol, I guess.

IMO this would only be interesting if other values can also be used in 
the server role.

For now I think it is more important that you be very clear what you 
intend.

I think it means that CLUE implementations will always need to use 
"webrtc" as the ALPN for the CLUE data channel, so that it will be right 
when interoperating with WebRTC. That is possible, though it seems weird 
when not interoperating.

(I'm struggling to figure out what c-webrtc means for a native clue 
device, such as an MCU.)

	Thanks,
	Paul