FW: RFC 2083 on PNG: Portable Network Graphics

Dan Kohn (dan@teledesic.com)
Thu, 16 Jan 1997 12:32:12 -0800

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------ =_NextPart_000_01BC03A9.61DA8B00
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Is anybody working on a multiple graphic versions (i.e., supporting
animation) of PNG? It seems like nobody will drop GIF and adopt PNG
until it can offer the same functionality of animated GIFs.

- dan

>From: RFC Editor[SMTP:rfc-ed@isi.edu]
>Sent: Thursday, January 16, 1997 11:04 AM
>To: The recipient's address is unknown.
>Cc: rfc-ed@isi.edu
>Subject: RFC 2083 on PNG: Portable Network Graphics
>A new Request for Comments is now available in online RFC libraries.
> RFC 2083:
> Title: PNG (Portable Network Graphics) Specification
> Version 1.0
> Author: T. Boutell, et. al.
> Date: January 1997
> Mailbox: boutell@boutell.com
> Pages: 102
> Characters: 242520
> Updates/Obsoletes: None
> URL: ftp://ds.internic.net/rfc/rfc2083.txt
>This document describes PNG (Portable Network Graphics), an
>extensible file format for the lossless, portable, well-compressed
>storage of raster images. This specification defines the Internet
>Media Type image/png.
>This memo provides information for the Internet community. This memo
>does not specify an Internet standard of any kind. Distribution of
>this memo is unlimited.
>IESG Note: The IESG takes no position on the validity of any
>Intellectual Property Rights statements contained in this document.
>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@CNRI.RESTON.VA.US. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@ISI.EDU with the message body
>help: ways_to_get_rfcs. For example:
> To: rfc-info@ISI.EDU
> 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 admin@DS.INTERNIC.NET. 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@ISI.EDU. Please consult RFC 1543, Instructions to RFC
>Authors, for further information.
>Joyce K. Reynolds and Mary Kennedy
>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.

------ =_NextPart_000_01BC03A9.61DA8B00
Content-Type: Message/External-body; name="ATT00527.txt"
Content-Transfer-Encoding: base64


------ =_NextPart_000_01BC03A9.61DA8B00
Content-Type: Message/External-body; name="rfc2083.txt.url"
Content-Transfer-Encoding: base64


------ =_NextPart_000_01BC03A9.61DA8B00--