W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2015

Mechanics of interfacing WebRTC API and JSEP

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Mon, 2 Nov 2015 12:35:49 +0100
To: public-webrtc@w3.org
Message-ID: <56374A95.4050900@w3.org>

As part of discussing https://github.com/w3c/webrtc-pc/issues/337 at the 
WebRTC F2F last week, we came to the conclusion that we needed a better 
mechanism to link from the WebRTC API to the JSEP draft, and I 
volunteered to work with EKR on finding the right mechanism for that.

Having looked quickly in the tools used to build the JSEP draft, I can 
imagine the following options:
* we link directly to the "latest" version of JSEP posted at 
https://rtcweb-wg.github.io/jsep/ — this one has semantic anchors (e.g. 
https://rtcweb-wg.github.io/jsep/#sec-create-offer) so it's easy to do 
and requires little or no machinery to work; but it's not the official URL

* we extract "live" the matching of semantic anchors to section numbers 
from that same document, and use these to build full links to ietf.org 
URLs; the extraction can be done live since the doc is CORS'd; fairly 
easy to do, but requires some understanding and commitment of the 
alignment between https://rtcweb-wg.github.io/jsep/ and 
https://tools.ietf.org/html/draft-ietf-rtcweb-jsep ; also, it will make 
the WebRTC spec slower to load

* we set up a (automated?) process whereby each time the JSEP draft is 
updated, we run a tool that extract the mapping between semantic anchors 
and section numbers; I'm not sure how we integrate with the updates to 
JSEP draft (is there an IETF webhook for that?)

Any reaction or preference?

Received on Monday, 2 November 2015 11:35:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:10 UTC