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

[Qin Wu <[e-mail]>]

Hi, Magnus:
----- Original Message ----- 
From: "Magnus Westerlund" <[e-mail]>
To: <[e-mail]>
Sent: Wednesday, May 30, 2012 10:28 PM
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-monarch-14.txt


WG,

My individual review of the changes are the following.

1. I think section 3 would really benefit from a figure of the possible
locations of RTP monitors. I think it should focus on the location
rather than the full flow of the collected information. Thus become
simpler than the removed figure.

[Qin]: I thought the figure 1 has already been incoporated into setion 3 and replaced by the description in the section 3.
Based on your comment, I can propose to have the following figure

                            +------------|
         ------------------>|            |<------------------
         |                  | Management |                  |
         |                  |   System   <-----             |
         |                  |            |    |             |
         |                  +------^-----+    |             |
         |                         |          |             |
         |                         |          |             |
         |                 +---------------+  |             |
         |                 |               |  |             |
         |                 | Third Party   |  |             |
         |                 | RTP Monitor   |  |             |
         |                 |               |  |             |
         |                 +---------------+  |             |
         |                                    |             |
 +-------|-------+         +Intermediate --+  |    +--------|------+
 |RTP Sender     |         | RTP System    |  |    |RTP Receiver   |
 |               |         |               |---    |               |
 | +-----------+ |         | +-----------+ |       | +-----------+ |
 | |RTP Monitor| |  RTP    | |RTP Monitor| | RTP   | |RTP Monitor| |
 | +-----------+ | Stream  | +-----------+ |Stream | +-----------+ |
 |               |-------->|               |------>|               |
 |               |         |               |       |               |
 +---------------+         +---------------+       +---------------+
Is this figure what you are looking for?

2. I also wonder if we shouldn't really remove the word architecture
from this document and instead have the title be "Guidelines for the RTP
Monitoring Framework"

[Qin]: Are you proposing to replace the word "architecture" with "framework"?

3. In some sense I wished we could keep the old figure 1 somewhere in
the document. But I guess it would require even more discussion around
the management system.

[Qin]: Management system may not have RTP functionality. Therefore shouldn't it be
beyond scope of the RTP monitoring architecture? In the current draft, we have briefly 
discussed interaction between RTP monitor and management system with the following
description:
"
The RTP monitor also exposes real time Application QoS/QoE metric
   information in the appropriate report block format (e.g.,RTCP XR or
   other non-RTP means) to the management system. 
"

Cheers

Magnus

On 2012-05-30 15:49, Magnus Westerlund wrote:
> WG, Colin and Albrecht,
> 
> Please check if you think the changes in this version are appropriate.
> 
> Cheers
> 
> Magnus
> 
> On 2012-05-29 04:25, [e-mail] wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF.
>>
>> Title           : Monitoring Architecture for RTP
>> Author(s)       : Qin Wu
>>                           Geoff Hunt
>>                           Philip Arden
>> Filename        : draft-ietf-avtcore-monarch-14.txt
>> Pages           : 27
>> Date            : 2012-05-28
>>
>>    This memo proposes an architecture for extending RTP Control Protocol
>>    (RTCP) with a new RTCP Extended Reports (XR) (RFC3611) block type to
>>    report new metrics regarding media transmission or reception quality,
>>    following RTCP guidelines established in RFC5968.  This memo suggests
>>    that a new block should contain a single metric or a small number of
>>    metrics relevant to a single parameter of interest or concern, rather
>>    than containing a number of metrics which attempt to provide full
>>    coverage of all those parameters of concern to a specific
>>    application.  Applications may then "mix and match" to create a set
>>    of blocks which covers their set of concerns.  Where possible, a
>>    specific block should be designed to be re-usable across more than
>>    one application, for example, for all of voice, streaming audio and
>>    video.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-14.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-avtcore-monarch-14.txt
>>
>> The IETF datatracker page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-avtcore-monarch/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  [phone]
Färögatan 6                | Mobile [phone]
SE-164 80 Stockholm, Sweden| mailto: [e-mail]
----------------------------------------------------------------------

_______________________________________________
Audio/Video Transport Core Maintenance
[e-mail]
https://www.ietf.org/mailman/listinfo/avt