RE: RAQMON Last Call
"Fardid, Reza" <[email protected]> Wed, 15 Feb 2006 14:24:09 -0800
| Newsgroups | gmane.ietf.rmonmib |
|---|---|
| Message-ID | <DE218759AAF51B45B534A59F5166425402638FF7@ZANEVS03.cc-ntd1.covad.com> |
Andy, A rough estimate for signaling would be < 1% of all packets for an average duration (3-min) G.711 VoIP call and lower for G.729. Quantification of the error requires making application-specific assumptions. Qualitatively, it will not be possible to differentiate between signaling impairments caused by network packet loss versus other possible factors, such as softswtich failover. Regards, Reza Fardid -----Original Message----- From: Andy Bierman [mailto:[email protected]] Sent: Wednesday, February 15, 2006 1:13 PM To: Fardid, Reza Cc: [email protected] Subject: Re: [RMONMIB] RAQMON Last Call Fardid, Reza wrote: > > > > From a Service Provider point of view, it is important to a) measure > and differentiate signaling and media QoS metrics of delay and packet > loss, and b) report their measurements separately. This > differentiation may gain more significance, when one SP does not have > administrative and measurement control over the end-to-end path(s) > traversed by signaling and media packets, prompting the IPPM WG to > undertake work to define Spatial Composition of Metrics. Even though > the RAQMON MIB differentiates between signaling and application delay, > it does not clearly do so for packet loss. > What is the percentage of signaling to data packets we are talking about here? Please try to quantify the error that counting packet loss in this manner will introduce. I do not believe there is WG consensus to change the RAQMON Basic Report contents at this time. There is a mechanism within RAQMON for defining additional reports and additional report elements. IMO, we should gain implementation experience with the Basic Report we have now, and refine it over time, based on deployment experience and feedback. > > > Regards, > > Reza Fardid > > Covad Communications > > > Andy