From 8f70a731db995fb9a6e191363a6c3d125b8726a5 Mon Sep 17 00:00:00 2001 From: Christer Holmberg Date: Tue, 19 Jan 2021 21:59:51 +0200 Subject: [PATCH] Adding note regarding JSEP and BUNDLE inconsistency --- ...-ietf-mmusic-sdp-bundle-negotiation-54.xml | 30 +++++++++++++++++-- 1 file changed, 28 insertions(+), 2 deletions(-) diff --git a/draft-ietf-mmusic-sdp-bundle-negotiation-54.xml b/draft-ietf-mmusic-sdp-bundle-negotiation-54.xml index 9f6daf4..180d785 100644 --- a/draft-ietf-mmusic-sdp-bundle-negotiation-54.xml +++ b/draft-ietf-mmusic-sdp-bundle-negotiation-54.xml @@ -180,9 +180,35 @@ +
+ + Since the approval of the WebRTC specification documents, the IETF has become aware of an inconsistency + between the document specifying JSEP and the document specifying BUNDLE (RFC 8829 and RFC 8843, respectively). + Rather than delaying publication further to come to a resolution, the documents are being published as they were + originally approved. The IETF intends to restart work on these technologies, and revised versions of these + documents will be published as soon as a resolution becomes available. + + + The specific issue involves the handling of "m=" sections that are designated as bundle-only, as discussed + in RFC 8829, Section 4.1.1. Currently, there is divergence between JSEP and BUNDLE, as well as between these + specifications and existing browser implementations: + + + JSEP prescribes that said "m=" sections should use port zero and add an "a=bundle-only" attribute in + initial offers, but not in answers or subsequent offers. + + + BUNDLE prescribes that these "m=" sections should be marked as described in the previous point, + but in all offers and answers. + + + Most current browsers do not mark any "m=" sections with port zero and instead use the same port for + all bundled "m=" sections; one follows the JSEP behavior. + + + +
- -