- From: Lorenzo Miniero <lorenzo@meetecho.com>
- Date: Thu, 11 Apr 2019 18:19:51 +0200
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Hi Harald, why drop SSRC advertisement for rtx for simulcast? While I understand rtx is still there if you use the repaired-rid extension, Chrome was able to do both using different ssrc-groups. I realize SIM was not standard, but it gave the right context, and FID provided the rtx mappings instead. As such, as an interim solution, that sounded like an easier approach. Anyway, the rest looks good to me! Lorenzo On Thu, 11 Apr 2019 12:30:13 +0200 Harald Alvestrand <harald@alvestrand.no> wrote: > I have made a proposal. > > Note: This is strictly a *personal* contribution. Do not attach undue > authority to it. > > > Harald > > > > -------- Forwarded Message -------- > Subject: New Version Notification for > draft-alvestrand-mmusic-simulcast-ssrc-00.txt > Date: Thu, 11 Apr 2019 03:28:17 -0700 > From: internet-drafts@ietf.org > To: Harald Alvestrand <harald@alvestrand.no> > > > > > A new version of I-D, draft-alvestrand-mmusic-simulcast-ssrc-00.txt > has been successfully submitted by Harald Alvestrand and posted to the > IETF repository. > > Name: draft-alvestrand-mmusic-simulcast-ssrc > Revision: 00 > Title: Using SSRC with WebRTC Simulcast > Document date: 2019-04-11 > Group: Individual Submission > Pages: 6 > URL: > https://www.ietf.org/internet-drafts/draft-alvestrand-mmusic-simulcast-ssrc-00.txt > Status: > https://datatracker.ietf.org/doc/draft-alvestrand-mmusic-simulcast-ssrc/ > Htmlized: > https://tools.ietf.org/html/draft-alvestrand-mmusic-simulcast-ssrc-00 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-alvestrand-mmusic-simulcast-ssrc > > > Abstract: > This document describes a convention for sending "a=ssrc" attributes > in SDP together with "a=simulcast" attributes. This allows SFUs that > need SSRC information to have this info easily accessible. > > Given that it is intended as an interim measure, it does not aim for > being published as an RFC. > > > > Please note that it may take a couple of minutes from the time of > submission until the htmlized version and diff are available at > tools.ietf.org. > > The IETF Secretariat > -- I'm getting older but, unlike whisky, I'm not getting any better https://twitter.com/elminiero
Received on Thursday, 11 April 2019 16:20:21 UTC