Yaakov Stein wrote:
According to RFC 2026 historic RFCs are those whose
specification has been superceded by a more recent specification.
RFC 4612 is labeled historic, and defines a MIME type
for T.38 over RTP, a practice that is just now being adopted
and to be encouraged.
Indeed, the RFC discusses limitations of UDPTL,
but it does not suggest deprecating its use.
In any case the subject of the RFC is the RTP mode,
and not UDPTL.
So why the "historic" designation?
From the announcement of IESG approval:
This document was Last Called as Proposed Standard in the past, but
review by the Audio Video Transport Working Group and the
IESG led to concern that the format not become a precedent
for future media types. The specification should be
published and available for registration, and the media-type should
be registered, but only because these are required for a very specific
application within ITU SG 16's T.38's real-time fax support.
This application is described in the document as a "legacy".
The Historic designation does not imply that the legacy
application should not be operative with this specification and
registration to support it, but only that there not be *future*
designs, non-legacies, based on this precedent.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf