[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [AVT] I-D ACTION:draft-ietf-avt-tfrc-profile-05.txt
Internet-Drafts at ietf.org writes:
> Title : RTP Profile for TCP Friendly Rate Control
> Author(s) : L. Gharai
> Filename : draft-ietf-avt-tfrc-profile-05.txt
> Pages : 14
> Date : 2005-10-25
>
>This memo specifies a profile called "RTP/AVPCC" for the use of the
> real-time transport protocol (RTP) and its associated control
> protocol, RTCP, with the TCP Friendly Rate Control (TFRC). TFRC is
Is it just me, or are we facing an explosion of pain over the
number of profiles being adopted? Every time we create a new profile, we
need to create N more because most of these options are orthogonal.
Will we now need AVPCCF, SAVPCC and SAVPCCF to be defined??? Not
to mention other possibilities... And this will now mean that to initiate
a call will require navigating the waters of 8 possible semi-compatible
profiles.... And we don't have a way to properly and quickly handle this -
let alone in a single UDP packet (yes, I know TCP/TLS is preferred - but
it's also not widely deployed in a lot of commercial networks), or let
alone in a reliably compatible fashion.
ARGH.
--
Randell Jesup, Worldgate (developers of the Ojo videophone), ex-Amiga OS team
rjesup at wgate.com
_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt