RTP Payload Format for H.263 Moving RFC 2190 to Historic Status
draft-ietf-avt-rfc2190-to-historic-06

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    avt mailing list <avt@ietf.org>, 
    avt chair <avt-chairs@tools.ietf.org>
Subject: Document Action: 'RTP Payload Format for H.263 using 
         RFC2190 to Historic status' to Informational RFC 

The IESG has approved the following document:

- 'RTP Payload Format for H.263 using RFC2190 to Historic status '
   <draft-ietf-avt-rfc2190-to-historic-07.txt> as an Informational RFC

This document is the product of the Audio/Video Transport Working Group. 

The IESG contact persons are Cullen Jennings and Jon Peterson.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2190-to-historic-07.txt

Ballot Text

Technical Summary

The RTP Payload Format defined in RFC 2190 supports only the 1996 version of
H.263. Implementations supporting the 1998 (or later) versions of H.263 must
useRFC 2429 or its successor. This draft marks RFC 2190 as historic, to reduce
the
confusion about which version of the RTP Payload Format to use in new
implementations.

Working Group Summary

RFC 2190 was deprecated by the working group in 1998, with the publication of
RFC 2429. With the impending publication of 2429bis, there is clear consensus
inthe working group to formally mark RFC 2190 as historic.

Protocol Quality

The request to mark RFC 2190 as historic has been reviewed by Colin Perkins.
There are existing (old) implementations of RFC 2190 - the aim of this draft is
to prevent new implementations of it!


Note to RFC Editor
 
We would recommend holding this publication until we have an RFC number for
rfc2429bis. Please mark RFC 2190 as historic when this is published. 

Please add the following text after the last paragraph in Section 3: 

  This recommendation will come into effect at the publication or as soon as 
  possible after the publication of rfc2429-bis [rfc2429bis].

RFC Editor Note