Re: [rtcweb] JSEP: RTP demux algorithms

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 04 October 2016 13:43 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADF6129855 for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2016 06:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a9aO-iCEkuil for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2016 06:43:47 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 119FE1288B8 for <rtcweb@ietf.org>; Tue, 4 Oct 2016 06:43:46 -0700 (PDT)
X-AuditID: c1b4fb3a-ab7ff7000000099a-9e-57f3b20f0af9
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by (Symantec Mail Security) with SMTP id 2D.9A.02458.F02B3F75; Tue, 4 Oct 2016 15:43:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0319.002; Tue, 4 Oct 2016 15:43:43 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, Colin Perkins <csp@csperkins.org>
Thread-Topic: [rtcweb] JSEP: RTP demux algorithms
Thread-Index: AQHSDrBduC6LB65/lE2Mthgf5jiIWqB6/zGAgAFa1ACAAAkSAIAAAGcAgApOYwCABLS/gIAAB1yAgAAFnACADLXmgIAAOXmA///SXACAADWZAP//1iwAgAA+rAA=
Date: Tue, 04 Oct 2016 13:43:43 +0000
Message-ID: <D4198B28.1064D%christer.holmberg@ericsson.com>
References: <CAOW+2dtN-tfmnsep8FjOFD2R2uZbUwZxHfDGBwx3N13Ue9Nb2w@mail.gmail.com> <E1B53795-4B14-408B-BFF1-A305EE45AD20@iii.ca> <66CB8C7B-56D1-4AC9-B0F8-4F1689E2CA89@vidyo.com> <E7C35776-C554-47C5-A522-F1C02629041F@iii.ca> <A52D1EFE-6A7D-418F-A77B-176E184EBAB9@vidyo.com> <07afeaa4-06fb-b6a9-b2d7-f944b471fde1@ericsson.com> <949bdcde-b24d-f2d4-e855-91424b2be30a@alvestrand.no> <4837a71e-0e54-29d0-0a96-75f3fdbc7e1b@ericsson.com> <2a67053c-bd75-cc85-eeba-e57f64667ab1@alvestrand.no> <46F5ACCF-8701-41F1-A8A4-85796EFF9B07@csperkins.org> <D41975B4.105C7%christer.holmberg@ericsson.com> <00d7ff8e-e6dc-7231-334f-833af1727cd7@alvestrand.no> <D4197BD1.105FE%christer.holmberg@ericsson.com> <c9a9ae72-804e-33fa-669c-da09dd258e78@alvestrand.no>
In-Reply-To: <c9a9ae72-804e-33fa-669c-da09dd258e78@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1B0B245F5CFFDF408B3D14F95A4EA551@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMIsWRmVeSWpSXmKPExsUyM2K7iq7gps/hBrefylssf3mC0eJYXxeb xdp/7ewOzB5XJlxh9Zh2/z6bx5IlP5kCmKO4bFJSczLLUov07RK4Mt6/289ScE2i4uF0tgbG FokuRg4OCQETiRdvA7oYuTiEBNYzSsy7cJEZwlnEKLH4wyUWkCI2AQuJ7n/aXYycHCICgRK7 VzWyg9jMAuoSdxafA7OFBQwkFrZ9ZQcpFxEwlOjqkwcZIyLQxSjx4/FBZpAaFgEViW/3vzKB 1PAKWEusbeUFCQsJ/GSV2HOlEsTmFHCUWLylhQ3EZhQQk/h+ag0TxCpxiVtP5oPZEgICEkv2 nGeGsEUlXj7+xwpiiwroSXz/Ohsqrijx8dU+RpBVzAKaEut36UOY1hItG7ggJipKTOl+CHY8 r4CgxMmZT1gmMIrPQrJsFkLzLITmWUiaZyFpXsDIuopRtDi1uDg33chIL7UoM7m4OD9PLy+1 ZBMjMOoObvlttYPx4HPHQ4wCHIxKPLwJKZ/ChVgTy4orcw8xSnAwK4nwZm/4HC7Em5JYWZVa lB9fVJqTWnyIUZqDRUmc12zl/XAhgfTEktTs1NSC1CKYLBMHp1QD48x3M/6qOmzgV+kQEvmb Mi3nfunS+Vej2AxDNl394cmx6i1TrMuMN/6+Har79WZJL7npxSGhNufm5FXs4tNm3EnccU53 9osfBi0Ttj/VYr5m/v277dTAtI+a+T1mn9l+vQuvd3vUrmR+L153/Q1emzWz0kuXvi3T/C6x RnBNX5DBbaVvG9/826DEUpyRaKjFXFScCAC2cVratgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/qeq9en0tn7fRHf7-36qPBXMP2GE>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP: RTP demux algorithms
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Oct 2016 13:43:49 -0000

Hi,

>>>>I still question why the low-level RTP demuxing shall be described in
>>>> JSEP, instead of e.g., BUNDLE.
>>>>
>>>> Keep in mind that all BUNDLE implementations may not implement JSEP,
>>>> but I
>>>> still think we want the RTP demuxing to be done in the same way?
>>>
>>> Does BUNDLE say how to handle RID?
>> 
>> No. Cullen wanted more text, though, but I am not sure whether that
>> covered RID.
>> 
>>> Seriously, please get BUNDLE out the door and don't tangle it in any
>>> more new stuff.
>> 
>> If that was meant to me, I will pretend I didn¹t see itŠ
>
>It's actually a grave concern of mine - more addressed to the chairs of
>the relevant WGs than to anyone else.
>
>Any open document is a magnet for new functionality, and any new
>functionality delays the document's publication.
>
>The bundle document, with its associated changes in registration
>procedures for SDP attributes (the mux category), needs to be seen as
>stable. RFC publication is the best way to make it so.
>
>Datatracker says we've been working on this document since 2011. It's
>now at version -32, and was in state "Minor updates needed to address
>WGLC comments" in May.
>
>If we can segregate new requests for functionality into other documents,
>I think that is a win.

It’s not the addition of new functionality that has caused the delay.
Whenever we’ve decided to add some new functionality, the process has been
rather fast and smooth - thanks to everyone who have provided text and
input.

What is causing the delay is the never-ending requests for editorial
changes (many of which are not done using a simple search/replace - they
often require wider re-writing/structuring). Whenever person X has
provided comments, and I’ve updated the document, person Y wants something
else. It would have been much easier if person Y would have given his/her
comments when person X did, and then we could have discussed and tried to
find something that both X and Y are happy with.

Note that I AM very thankful that people DO review the document (we need
more of that), and most of the comments are really good, but by using the
current “process” we’ll never be ready. Anyway, I think that discussion
belongs to MMUSIC.

Regards,

Christer