Re: [xrblock] I-D Action:draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt

["Schwarz, Albrecht (Albrecht)" <[e-mail]>]

Two comments Rachel:
1) Well, that's not a general observation, rather a specific use case, given by a condition of limited transport capacity.
Leading to two type of IP access networks ("because if there's a bottleneck, then in the network access"), one type with strict limitations on the available RTCP transport capacity for measurement reports, and one type without strict limitations.

As a side note: the measurement point may be also located on network level, e.g. in a gateway, without your condition of limited transport.

2) Could you provide some guidance concerning expected transport capacity? I.e., what's your estimated ratio between the RTP media traffic and associated RTCP XR measurement traffic?
I know, it's dependent on the number of metric types etc, but I've think you should provide some quantitative figures, especially concerning your expected bandwidth savings ("single, large compound packet vs multiple ..."). 

Thanks,
Albrecht
 

> -----Original Message-----
> From: Rachel Huang(yihong) [mailto:[e-mail]] 
> Sent: Donnerstag, 13. Oktober 2011 16:51
> To: Schwarz, Albrecht (Albrecht); Colin Perkins; Qin Wu
> Cc: [e-mail]
> Subject: 答复: [xrblock] I-D 
> Action:draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt
> 
> The intention that we use the measurement identity is to 
> reduce the duplicated fields in every metric XR blocks, to 
> save bandwidth when we're monitoring. It will benefit those 
> systems whose resources are not rich, for example, systems 
> with low-bitrate links. While in those systems, the RTCP XR 
> packets may not be able to compound together, which has been 
> described in [RFC5506]. And in this case, these RTCP XR 
> blocks may have to be sent with measurement indentity block 
> one by one, and I don't think it can achieve the original intention. 
> So I agree with Colin. my opinion is that we don't need to 
> involve important fields (like durations) which are closely 
> connected with metric XR blocks.
> 
> ______________________________________
> 发件人: [e-mail] [[e-mail]] 代表 
> Schwarz, Albrecht (Albrecht) [[e-mail]]
> 发送时间: 2011年10月13日 19:12
> 到: Colin Perkins; Qin Wu
> Cc: [e-mail]
> 主题: Re: [xrblock]       I-D     
> Action:draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt
> 
> My opinion:
> 
> When we would use the measurement identity SDES item, 
> measurement information XR block, together with an associated 
> set of a number of metric XR blocks, - e.g. in performance 
> monitoring and reporting architecture as a network overlay -, 
> then the measurement duration (cumulative & interval) would 
> be normally common characteristics across all metrics.
> 
> Don't see the use case for metric-individual measurement 
> duration settings.
> 
> Thus, could be kept in the measurement information XR block 
> in my opinion.
> 
> My .03 €,
> Albrecht
> 
> 
> 
> > -----Original Message-----
> > From: [e-mail]
> > [mailto:[e-mail]] On Behalf Of Colin Perkins
> > Sent: Donnerstag, 13. Oktober 2011 12:17
> > To: Qin Wu
> > Cc: [e-mail]
> > Subject: Re: [xrblock] I-D
> > Action:draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt
> >
> > Qin,
> >
> > Thanks - this addresses most of my comments on the previous version.
> >
> > I'm still somewhat unconvinced that we need a separate report to 
> > convey measurement duration, rather than including it in 
> each report 
> > block. It can avoid duplication, I agree, but at the cost 
> of potential 
> > ambiguity if the measurement duration block is not sent. My 
> preference 
> > is to accept the potential duplication, to avoid the failure 
> > condition, but it would be interesting to hear other opinions.
> >
> > Colin
> >
> >
> >
> > On 13 Oct 2011, at 09:28, Qin Wu wrote:
> > > Here is version 01.
> > >
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-meas-id
> > > entity-01.txt This revision adds  the XR Block format to convey 
> > > additional measurement informtation. We are still using
> > SDES item format to carry APSI. This was brought up by Colin.
> > >
> > > These additional measurement information is still useful becos
> > > draft-ietf-avt-rtcp-xr-burst-gap-discard-02 and
> > > draft-ietf-avt-rtcp-xr-burst-gap-loss-02
> > > depends on this information to calculate the whole number
> > of packets expected.
> > >
> > > For diff:
> > >
> > 
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-xrblock-rtcp-xr-meas-ide
> > > ntity-01.txt
> > >
> > > Regards!
> > > -Qin
> > > ----- Original Message -----
> > > From: <[e-mail]>
> > > To: <[e-mail]>
> > > Cc: <[e-mail]>
> > > Sent: Thursday, October 13, 2011 11:15 AM
> > > Subject: [xrblock] I-D
> > > Action:draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt
> > >
> > >
> > >> A New Internet-Draft is available from the on-line
> > Internet-Drafts directories. This draft is a work item of 
> the Metric 
> > Blocks for use with RTCP&#39;s Extended Report Framework 
> Working Group 
> > of the IETF.
> > >>
> > >> Title           : Measurement Identity and information
> > Reporting using SDES item and XR Block
> > >> Author(s)       : Geoff Hunt
> > >>                         Alan Clark
> > >>                         Qin Wu
> > >> Filename        : draft-ietf-xrblock-rtcp-xr-meas-identity-01.txt
> > >> Pages           : 13
> > >> Date            : 2011-10-12
> > >>
> > >>  This document defines a RTCP SDES item and a RTCP XR
> > Block carrying
> > >> parameters which identify a measurement, to which one or
> > more other
> > >> RTCP XR Report Blocks may refer.
> > >>
> > >>
> > >> A URL for this Internet-Draft is:
> > >>
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-xrblock-rtcp-xr-meas-i
> > >> dentity-01.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-xrblock-rtcp-xr-meas-id
> > >> entity-01.txt _______________________________________________
> > >> xrblock mailing list
> > >> [e-mail]
> > >> https://www.ietf.org/mailman/listinfo/xrblock
> > > _______________________________________________
> > > xrblock mailing list
> > > [e-mail]
> > > https://www.ietf.org/mailman/listinfo/xrblock
> >
> >
> >
> > --
> > Colin Perkins
> > http://csperkins.org/
> >
> >
> >
> > _______________________________________________
> > xrblock mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/xrblock
> >
> _______________________________________________
> xrblock mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/xrblock