Re: How to discover a WHEP URL

This looks like a case for HTTP Content-Type negotiation.  For example, a video client that supports DASH, HLS, WHEP, and raw WebM could send a request header like

Accept: audio/mpegurl, application/vnd.apple.mpegurl, application/dash+xml, application/example-whep, video/webm

and the response could choose one in the Content-Type header.

--Ben

________________________________
From: Nils Ohlmeier <ietf@ohlmeier.org>
Sent: Friday, January 3, 2025 6:15 PM
To: ietf-http-wg@w3.org <ietf-http-wg@w3.org>
Cc: wish@ietf.org <wish@ietf.org>
Subject: How to discover a WHEP URL

Hello HTTP experts, The WISH working group is working on finalizing the WHEP draft https: //datatracker. ietf. org/doc/draft-ietf-wish-whep/ During the Dublin meeting the group discussed the issue how clients can determine/identify how to handle

Hello HTTP experts,

The WISH working group is working on finalizing the WHEP draft https://datatracker.ietf.org/doc/draft-ietf-wish-whep/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-wish-whep/__;!!Bt8RZUm9aw!7-eLkB9ABaRST7R5ck6ATFGVRuBJ8DDmcwlPlrDCI0dJC2Arf4ecrmhC29DvHyZMXRo7Efe53A$>

During the Dublin meeting the group discussed the issue how clients can determine/identify how to handle a WHEP URL, but unfortunately without a good resolution.
The basic question is: if a user copies a URL into a media player, e.g. VLC, how can the media player figure out that this URL is a WHEP resource?

Proposals so far were:
 - a new URL scheme, which we all understand is probably not a good idea.
 - mandate that the URL needs to have a certain "file" ending like other existing media URLs; probably also not a great solution

We have an open issue for this question https://github.com/wish-wg/webrtc-http-egress-protocol/issues/15

Any ideas and/or feedback on this topic would be appreciated.

Best regards
  Nils Ohlmeier
  WISH WG co-chair