RFC 4628 on RTP Payload Format for H.263 Moving RFC 2190 to Historic Status
rfc-editor@rfc-editor.org Thu, 01 February 2007 18:51 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCh25-000304-Mz; Thu, 01 Feb 2007 13:51:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCh23-0002zv-O5; Thu, 01 Feb 2007 13:51:39 -0500
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCh21-000416-2h; Thu, 01 Feb 2007 13:51:39 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l11IpZRU014252; Thu, 1 Feb 2007 10:51:35 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l11IpZKj014251; Thu, 1 Feb 2007 10:51:35 -0800
Date: Thu, 01 Feb 2007 10:51:35 -0800
Message-Id: <200702011851.l11IpZKj014251@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4628 on RTP Payload Format for H.263 Moving RFC 2190 to Historic Status
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 4628
Title: RTP Payload Format for H.263
Moving RFC 2190 to Historic Status
Author: R. Even
Status: Informational
Date: January 2007
Mailbox: roni.even@polycom.co.il
Pages: 5
Characters: 8084
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avt-rfc2190-to-historic-06.txt
URL: http://www.rfc-editor.org/rfc/rfc4628.txt
The first RFC that describes RTP payload format for
ITU Telecommunication Standardization Sector (ITU-T) recommendation
H.263 is RFC 2190. This specification discusses why to move RFC 2190
to historic status. This memo provides information for the Internet community.
This document is a product of the Audio/Video Transport
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce