RTP (in particular, the DATA PART) is tightly coupled to the application, so that a kernel implementation makes little sense. A number of people have developed libraries that implement RTP and RTCP (SEE listing). The sources to NeVoT, rtpdump, vat, rat and vic also contain RTP and RTCP processing modules which should be usable in other APPLICATIONS with minor modifications. Note also that the specification itself contains NUMEROUS code fragments. (Most of the other applications are using older versions of RTP and thus should not be relied upon for developments.)

The Java Media Framework (JMF), a Java API, also supports RTP and RTCP.

There is no standard API for RTP.

RTP (in particular, the data part) is tightly coupled to the application, so that a kernel implementation makes little sense. A number of people have developed libraries that implement RTP and RTCP (see listing). The sources to NeVoT, rtpdump, vat, rat and vic also contain RTP and RTCP processing modules which should be usable in other applications with minor modifications. Note also that the specification itself contains numerous code fragments. (Most of the other applications are using older versions of RTP and thus should not be relied upon for developments.)

The Java Media Framework (JMF), a Java API, also supports RTP and RTCP.

There is no standard API for RTP.