rfc.dk

Cited in: RFC 4351

13 RFCs mentioned in the text of RFC 4351 (Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream)

RFCTitleStatusDate
791Internet ProtocolJ. PostelInternet StandardSeptember 1981
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
2198RTP Payload for Redundant Audio DataC. Perkins, I. Kouvelas, O. Hodson, V. Hardman, M. Handley, J.C. Bolot, A. Vega-Garcia, S. Fosse-ParisisProposed StandardSeptember 1997
2327SDP: Session Description ProtocolM. Handley, V. Jacobson · obsoleted by RFC 4566Proposed StandardApril 1998
2733An RTP Payload Format for Generic Forward Error CorrectionJ. Rosenberg, H. Schulzrinne · obsoleted by RFC 5109Proposed StandardDecember 1999
2833RTP Payload for DTMF Digits, Telephony Tones and Telephony SignalsH. Schulzrinne, S. Petrack · obsoleted by RFC 4733, RFC 4734Proposed StandardMay 2000
3264An Offer/Answer Model with Session Description Protocol (SDP)J. Rosenberg, H. SchulzrinneProposed StandardJuly 2002
3550RTP: A Transport Protocol for Real-Time ApplicationsH. Schulzrinne, S. Casner, R. Frederick, V. JacobsonInternet StandardJuly 2003
3551RTP Profile for Audio and Video Conferences with Minimal ControlH. Schulzrinne, S. CasnerInternet StandardJuly 2003
3555MIME Type Registration of RTP Payload FormatsS. Casner, P. Hoschka · obsoleted by RFC 4855, RFC 4856Proposed StandardJuly 2003
3629UTF-8, a transformation format of ISO 10646F. YergeauInternet StandardNovember 2003
3714IAB Concerns Regarding Congestion Control for Voice Traffic in the InternetS. Floyd, Ed., J. Kempf, Ed.InformationalMarch 2004
4103RTP Payload for Text ConversationG. Hellstrom, P. JonesProposed StandardJune 2005