RFC 2448 on AT&T's Error Resilient

RFC Editor <rfc-ed@ISI.EDU> Mon, 16 November 1998 22:55 UTC

Message-Id: <199811162238.OAA11305@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2448 on AT&T's Error Resilient
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 16 Nov 1998 14:38:12 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2448:

        Title:	    AT&T's Error Resilient Video Transmission
		    Technique
	Author(s):  M. Civanlar, G. Cash, B. Haskell
	Status:     Informational
	Date:       November 1998
        Mailbox:    civanlar@research.att.com, glenn@research.att.com,
		    bgh@research.att.com
	Pages:      7
        Characters: 14655
        Updates/Obsoletes/See Also: None
        I-D Tag:    draft-civanlar-hplp-01.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2448.txt


This document describes a set of techniques for packet loss resilient
transmission of compressed video bitstreams based on reliable delivery
of their vital information-carrying segments. The described techniques
can be used over packet networks without packet prioritization. These
techniques are related to AT&T/Lucent patents [1, 2].

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.echo 
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 Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2448.txt"><ftp://ftp.isi.edu/in-notes/rfc2448.txt>

RFC 2448 on AT&T's Error Resilient RFC Editor