Magnus Westerlund | 24 Apr 2012 15:17
Picon
Favicon

Re: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-12.txt

Authors,

I have reviewed the latest changes and do wonder if the proposed
formulations really are the correct one.

Full diff:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-avtcore-monarch-12

Section 5.2:
Report blocks that require such correlation need to include the payload
type of the reported media, and must signal details and parameters of
the payload format to which that payload type is bound.

I think my grief with the above sentence is the second half. I don't
find it appropriate that each report block include details and
parameters of the the payload format. I think the approriate level is to
include the payload type and use the functions you anyway have for
associating signalling with media session capture to store the actual
parameter?

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund <at> ericsson.com
----------------------------------------------------------------------

_______________________________________________
Audio/Video Transport Core Maintenance
avt <at> ietf.org
https://www.ietf.org/mailman/listinfo/avt


Gmane