From owner-freebsd-net Wed May 3 9: 4:33 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 8A2B537BA27 for ; Wed, 3 May 2000 09:04:30 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA78212; Wed, 3 May 2000 12:01:47 -0400 (EDT) (envelope-from wollman) Date: Wed, 3 May 2000 12:01:47 -0400 (EDT) From: Garrett Wollman Message-Id: <200005031601.MAA78212@khavrinen.lcs.mit.edu> To: Yonny Cardenas Cc: freebsd-net@FreeBSD.ORG Subject: RTP and BSD Kernel In-Reply-To: <20000502202655.2834.qmail@web1604.mail.yahoo.com> References: <20000502202655.2834.qmail@web1604.mail.yahoo.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I think that is desirable a RTP implementation in kernel available > for several applications or for better performance. The general sense I have had from the developers of this technology is that you absolutely do *not* want it in the kernel. The reason is that each individual application will have its own, unique requirements for the RTP data stream, and that the RTP implementation therefore needs to be tightly integrated into the application. By contrast, RTP itself places minimal requirements upon the lower layers. OTOH, what *would* potentially be useful would be an implementation of RTP/UDP/IP header compression. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message