RFC 2762 on RTP Sampling
RFC Editor <rfc-ed@ISI.EDU> Tue, 08 February 2000 16:51 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01392; Tue, 8 Feb 2000 11:51:01 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id LAA28915 for ietf-123-outbound.10@ietf.org; Tue, 8 Feb 2000 11:45:06 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id LAA28867 for <all-ietf@loki.ietf.org>; Tue, 8 Feb 2000 11:41:32 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00882 for <all-ietf@ietf.org>; Tue, 8 Feb 2000 11:41:31 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id IAA06774; Tue, 8 Feb 2000 08:41:27 -0800 (PST)
Message-Id: <200002081641.IAA06774@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2762 on RTP Sampling
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 08 Feb 2000 08:41:27 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2762 Title: Sampling of the Group Membership in RTP Author(s): J. Rosenberg, H. Schulzrinne Status: Experimental Date: February 2000 Mailbox: jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu Pages: 12 Characters: 25796 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-rtpsample-06.txt URL: ftp://ftp.isi.edu/in-notes/rfc2762.txt In large multicast groups, the size of the group membership table maintained by RTP (Real Time Transport Protocol) participants may become unwieldy, particularly for embedded devices with limited memory and processing power. This document discusses mechanisms for sampling of this group membership table in order to reduce the memory requirements. Several mechanisms are proposed, and the performance of each is considered. This document is a product of the Audio/Video Transport Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2762 on RTP Sampling RFC Editor