RFC 4571 on Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport
rfc-editor@rfc-editor.org Wed, 19 July 2006 18:33 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Grq-0000wB-24; Wed, 19 Jul 2006 14:33:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GNx-0000HE-MS; Wed, 19 Jul 2006 14:03:01 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3GNw-0002rw-3w; Wed, 19 Jul 2006 14:03:00 -0400
Received: from nit.isi.edu ([128.9.160.116]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G3GNK-0007ln-MU; Wed, 19 Jul 2006 14:02:24 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k6JI2J85029331; Wed, 19 Jul 2006 11:02:19 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k6JI2JSE029330; Wed, 19 Jul 2006 11:02:19 -0700
Date: Wed, 19 Jul 2006 11:02:19 -0700
Message-Id: <200607191802.k6JI2JSE029330@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -17.6 (-----------------)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4571 on Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4571
Title: Framing Real-time Transport Protocol (RTP)
and RTP Control Protocol (RTCP) Packets
over Connection-Oriented Transport
Author: J. Lazzaro
Status: Standards Track
Date: July 2006
Mailbox: lazzaro@cs.berkeley.edu
Pages: 9
Characters: 18751
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avt-rtp-framing-contrans-06.txt
URL: http://www.rfc-editor.org/rfc/rfc4571.txt
This memo defines a method for framing Real-time Transport
Protocol (RTP) and RTP Control Protocol (RTCP) packets onto
connection-oriented transport (such as TCP). The memo also defines
how session descriptions may specify RTP streams that use the framing
method. [STANDARDS TRACK]
This document is a product of the Audio/Video Transport
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. 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.
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
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce