[rfc-dist] RFC 4628 on RTP Payload Format for H.263 Moving RFC 2190 to Historic Status
rfc-editor at rfc-editor.org
Thu Feb 1 10:51:35 PST 2007
A new Request for Comments is now available in online RFC libraries.
Title: RTP Payload Format for H.263
Moving RFC 2190 to Historic Status
Author: R. Even
Date: January 2007
Mailbox: roni.even at polycom.co.il
I-D Tag: draft-ietf-avt-rfc2190-to-historic-06.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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist