| Newsgroups |
gmane.ietf.rmt |
| Message-ID |
<[email protected]> |
FLUTE's approach is inherited from ALC - i.e. this needs doing for ALC
and then FLUTE inherits the solution. I would have thought it absolutely
should not be further described in FLUTE (possibly not in ALC either)
according to the RMT building block approach. Is that about right?
Cheers, Rod.
>-----Original Message-----
>From: ext Magnus Westerlund [mailto:[email protected]]
>Sent: 01 December, 2006 15:27
>To: [email protected]
>Subject: [Rmt] congestion control in FLUTE
>
>Hi,
>
>As FLUTE is an application of the RMT building blocs I think
>it needs to specify how the hell you actually apply some
>congestion control on the sessions. In section 4 there is
>discussion about four scenarios of how this may be done. I
>think it will be necessary to flesh out how one actually
>perform A and C using the available tools. That means
>specifying how you actually can apply WEBRC and TFMCC to flute
>and what restrictions that do apply. It might not be necessary
>to define both, however we do need something that works well
>in most deployments where FLUTE is used.
>
>It would also be really good to see someone write up the glue
>that is need to enable implementation of WEBRC. There seem to
>be need for clarification on how to handle the WEBRC channels
>and in addition how one signal this to the receivers using SDP.
>
>I want to get this going as I don't think we will be able to
>proceed to standards track with flute unless we have a solid
>congestion control story.
>
>Cheers
>
>Magnus Westerlund
>
>IETF Transport Area Director & TSVWG Chair
>----------------------------------------------------------------------
>Multimedia Technologies, Ericsson Research EAB/TVA/A
>----------------------------------------------------------------------
>Ericsson AB | Phone +46 8 4048287
>Torshamsgatan 23 | Fax +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: [email protected]
>----------------------------------------------------------------------
>
>_______________________________________________
>Rmt mailing list
>[email protected]
>https://www1.ietf.org/mailman/listinfo/rmt
>