1. draft-johnston-sipping-rtcp-summary-01.txt RTCP Summary Report Delivery to SIP Third Parties draft-johnston-sipping-rtcp-summary-01.txt Alan Johnston – alan.johnston @ mci.com Alan Clark – alan @ telchemy.com

2. draft-johnston-sipping-rtcp-summary-01.txt Rationale Provide VoIP session quality metrics to SIP third parties RTCP XR provides endpoint-to-endpoint exchange of information Service providers/ network managers would like fault/performance management info associated with calls (e.g. in CDRs) H.323 and H.248 are being extended with “QoS reporting” based on RTCP XR metrics, desirable to use a common approach for all signaling protocols

3. draft-johnston-sipping-rtcp-summary-01.txt IP Network IP Network Applications Proxy“Proxy” Proxy Provide call quality/ service quality feedback to the “service provider” Call control protocols maintain association between endpoint generated call quality metrics and endpoint identification NAT Domain

4. draft-johnston-sipping-rtcp-summary-01.txt Draft-02.. updates/issues 01 draft described –RTCP forking –transport of metrics in SIP header or message body –SIP Events package (recommended approach) 02 draft adds proposed format for Metrics –Binary field (-RTCP XR payload) [32 bytes always] –Comma separated ASCII encoded hex [up to 85 bytes] –Comma separated ASCII [up to 91 bytes] –Proposes Comma separated ASCII hex

5. draft-johnston-sipping-rtcp-summary-01.txt Draft-02.. issues SIP Events package best choice? Preferred format for metrics? Include both local and remote metrics (if remote available via RTCP XR)?