Protocol Action: Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 23 May 2002 20:27 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25912; Thu, 23 May 2002 16:27:02 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA10546 for ietf-123-outbound.10@ietf.org; Thu, 23 May 2002 16:15:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id QAA10483 for <all-ietf@loki.ietf.org>; Thu, 23 May 2002 16:09:16 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24966; Thu, 23 May 2002 16:08:57 -0400 (EDT)
Message-Id: <200205232008.QAA24966@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@isi.edu>
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration to Proposed Standard
Date: Thu, 23 May 2002 16:08:57 -0400
Sender: scoya@cnri.reston.va.us


The IESG has approved the Internet-Draft 'Real-time Facsimile (T.38) -
image/t38 MIME Sub-type Registration' <draft-parsons-itu-t38-reg-00.txt>
as a Proposed Standard.  This has been reviewed in the IETF but is not 
the product of an IETF Working Group.

The IESG contact persons are Ned Freed and Patrik Faltstrom.

Technical Summary

   This document describes the registration of the MIME sub-type 
   image/t38. The encoding is defined by [T.38] and is intended
   for use as an SDP media descriptor. 
     
 Working Group Summary

   This document is an individual submission; it is not the product of
   a working group.

   Protocol Quality

   This specification was reviewed for the IESG by Ned Freed.



Note to RFC Editor:

Please change the [T.38] citation in the abstract to "ITU Recommendation T.38".

Please INSERT the following text immediately after Section 5:


   6.	Security Considerations 

	   Security considerations for this media type are discussed in the 
	   MIME type registration that appears in section 5.

   7.