[IPFIX] IPFIX-based identification of RTP traffic with support of RTP-specific information elements?
"Schwarz, Albrecht (Albrecht)" <[email protected]>
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <786615F3A85DF44AA2A76164A71FE1AC02257B@FR711WXCHMBA03.zeu.alcatel-lucent.com> |
Hi Benoit, et al.,
just a quick question for clarification, would expect that this topic was already discussed by the IPFIX community in the past:
The IPFIX registry only lists the RTP SN (RFC 3550) element:
http://www.iana.org/assignments/ipfix/ipfix.xml
=> rtpSequenceNumber
I'm wondering about support of more RTP-specific elements, which would be e.g. required for more fine-granular identification of RTP/RTCP (sub-flows)?
Such as support of
a) RTP:
- RTP PT (payload type)| RTCP PT (packet type)
- RTP SSRC
- RTP CSCR(s)
b) RTCP basic reports:
- RTCP SDES CNAME
- etc
c) RTCP extension reports (RFC 3611, XRBLOCK):
- RTCP XR BT
- etc
Looks odd that the IANA registry just provides the RTP SN, because the SSRC or/and CNAME might be much more interesting for traffic identification purposes. Hm?
Regards,
Albrecht
PS
I've noticed the " draft-scholz-ipfix-rtp-audio-quality" proposal.
Prime purpose is (in my understanding) the export of LOCAL measurements, e.g. according RTCP XR BT=7 or other RTP application-level performance metric types according XRBLOCK.
However, if such measurements would be REMOTELY generated AND reported along the IP media path using RTCP XR reports (see RFC 6792), then the IPFIX entity could identify and export such measurements ... if there would by IPFIX information elements available ("which is basically feasible ...") ... i.e. another category in above list.
__________________________________________________
Dr. Albrecht Schwarz
Alcatel-Lucent
[email protected]
_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix