Alan,
I think it would certainly be beneficial to prevent any kind of resistance to acceptance at the SG16 meeting. I think it is beneficial for the experts to have time to see this and comment prior to the SG16 meeting.
Paul
----- Original Message ----- From: "Alan Clark" alan@telchemy.com To: "'Paul E. Jones'" paulej@packetizer.com; ITU-SG16@echo.jf.INTEL.COM Sent: Wednesday, March 05, 2003 9:47 AM Subject: RE: [H460.9] - Update on status of RTCP Reporting Extensions
Paul
The proposal is to use the VoIP Metrics described in Section 4.7 of the
RTCP
Reporting Extensions (attached to yesterday's email).
The primary change since the previous version that was aired at the last SG16 meeting was the inclusion of residual echo - many problems in VoIP networks are caused by incorrect signal levels or high echo levels and
hence
it is important to report these parameters. Fortunately many line echo cancellors already have the necessary data available and hence the RTCP Reporting code simply extracts these from the DSP.
I would be happy to put some draft text together and circulate it. This would essentially comprise the set of metrics contained in the -03 draft
put
into the same format as those already described in the pre-published
H.460.9
Regards
Alan Clark Telchemy
-----Original Message----- From: Paul E. Jones [mailto:paulej@packetizer.com] Sent: Tuesday, March 04, 2003 8:14 PM To: alan@TELCHEMY.COM; ITU-SG16@echo.jf.INTEL.COM Subject: Re: [H460.9] - Update on status of RTCP Reporting Extensions
Alan,
In order to see this included in H.460.9, I think you should draft what changes you'd like to see in H.460.9 and float it around to experts on
this
list. I would personally prefer to add this as an Annex to the current pre-published H.460.9, though I'm open to discussion on how we can include this.
At any rate, I think we need to have some discussion on this before the
May
meeting. I don't think we can approve something if that is the first time we've seen it.
Paul
----- Original Message ----- From: "Alan Clark" alan@TELCHEMY.COM To: ITU-SG16@echo.jf.INTEL.COM Sent: Tuesday, March 04, 2003 3:46 PM Subject: [H460.9] - Update on status of RTCP Reporting Extensions
The IETF AVT RTCP Reporting Extensions draft is now at release 03
(attached)
and is being proposed for "last call" at the IETF meeting in mid-March.
I
hope that the document is reaching a level of stability that will permit
it
to be considered for inclusion in H.460.9
Regards
Alan Clark Telchemy
____________________________________________________________________________
Alan,
I fully agree with Bob's reply below. In my view H.460.9 is now
sufficiently
open to be used for transporting also advanced statistical data, even if
the
initial choice reflects the content of today's RTCP reports.
The information content of QoS reports is only one part of the standard. Another - maybe the major - part is the mechanism for conveying these reports from endpoints to gatekeepers and between gatekeepers. And this
part
does not change if improved QoS statistics become available.
It was the unanimous opinion of the experts at the SG16 meeting that
H.460.9
will be used for extended QoS reports as soon as the relevant work in
IETF
has finished. How this is best done will be decided when the RFC is available. Any input from your side is certainly welcome.
Regards, Ernst Horvath Siemens AG
For help on this mail list, send "HELP ITU-SG16" in a message to listserv@lists.intel.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@lists.intel.com