From: Dave Taht <dave.taht@gmail.com>
To: galene@lists.galene.org
Cc: T H Panton <tim@pi.pe>
Subject: [Galene] Re: using up more ports in ipv6 for better congestion control
Date: Sat, 10 Jul 2021 08:19:24 -0700 [thread overview]
Message-ID: <CAA93jw6ctcjpJcQBsgbCTiDiPX7TYp0PVcYW3Y=u=eHp=CaCyw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw58HfxwGTi6dwT+rGRYRrWQmBsaGatCmmNDc+KYPRLG+g@mail.gmail.com>
the thread over here:
https://www.linkedin.com/posts/dtaht_apples-new-facetime-a-sip-perspective-activity-6817609260348911616-p0kv/
On Sat, Jul 10, 2021 at 8:15 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> tim panton wrote me just now on linked in:
>
> "It is still possible. Just set bundle-policy to max-compat and you'll
> get one stream for audio and one for video. Turn off rtcp-mux and
> you'll get 4 ports (voice, video, voice-RTCP, video-RTCP) - But your
> ability to connect will drop significantly (according to Google's
> data) and your connection setup time will increase. Even with port
> muxing congestion control is still possible, it just works
> _differently_ - which arguably it should, because realtime video has
> quite different needs from streaming or file transfer. Happy to have a
> chat about this...."
>
> (so... chatting via email is preferred for me)
>
> I am also under the impression that the congestion control
> notifications in rtcp are essentially obsolete in the rfc, mandating a
> 500ms interval instead of something sane, like a frame?
>
> My other fantasy is to somehow start using udplite for more things.
>
> The context for this of course is my never ending quest to have an IP
> based video and audio streaming system good enough to have a band
> playing with each other across town.
>
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
--
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
Dave Täht CTO, TekLibre, LLC
next prev parent reply other threads:[~2021-07-10 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 15:15 [Galene] " Dave Taht
2021-07-10 15:19 ` Dave Taht [this message]
2021-07-10 16:36 ` [Galene] " T H Panton
2021-07-10 16:48 ` Dave Taht
2021-07-11 11:19 ` Juliusz Chroboczek
2021-07-15 14:17 ` Sean DuBois
2021-07-16 1:36 ` Juliusz Chroboczek
2021-07-16 14:25 ` Sean DuBois
2021-07-15 16:26 ` T H Panton
2021-07-16 1:37 ` Juliusz Chroboczek
2021-07-16 14:46 ` T H Panton
2021-07-16 17:48 ` Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6ctcjpJcQBsgbCTiDiPX7TYp0PVcYW3Y=u=eHp=CaCyw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=galene@lists.galene.org \
--cc=tim@pi.pe \
--subject='[Galene] Re: using up more ports in ipv6 for better congestion control' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox