[AVTCORE] comments on draft-ietf-avtcore-monarch-05

["Charles Eckel (eckelcu)" <[e-mail]>]

I read the draft and have the following comments:

Section 2 and 3 contain some definitions. Should we add definitions
there for additional terms, including interval metric, cumulative
metric, and sampled metric. There has been some debate on the
definitions of these on xrblock alias, and it would be good to have a
consistent definition of these terms.

Section 3 reads, " The Metric Block exposes real time Application
Quality information". Section 2 defined transport level, application
level, and end system metrics. As such, the use of "application quality
information" seems too specific and limiting to me.

Section 5.2 read, There may be situation where more than one media
transport protocols are used by one application to interconnect to the
same session in the gateway.  For example, one RTCP XR Packet is sent to
the participating endpoints using non- RTP-based media transport (e.g.,
using SIP) in a VOIP session, one crucial factor lies in how to handle
their different identities that are corresponding to different media
transport."
Are we really expecting RTCP XR packets to be used outside of an RTP
session? Or are we trying to say there may be multiple RTP sessions for
a given VoIP session, and there is a need to be able to correlate the
RTCP XR packets from each of these RTP sessions with each other?

Nits:

Section 4:
- change " may have different monitoring requirements, design large
block ..." to " may have different monitoring requirements. Designing
large block ..."
- change " it is hardly to provide" to " it is hard to provide"
- change " block types For example" to " block types.  For example"
- change " consecutive metric interval" to " consecutive metric
intervals"

Thanks,
Charles