rfc-3362

Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration

G. Parsons
date2002-09 streamLegacy statusPROPOSED STANDARD pages5 canonicalhttps://www.rfc-editor.org/rfc/rfc3362 doi10.17487/RFC3362
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.

Extracted elements (6)

design-rationale §3

ITU-T T.38 allows use of either TCP or UDP depending on the service environment, reflecting the need to accommodate different network reliability and latency trade-offs for real-time facsimile over IP.

realtime, voip, tcp, udp

interoperability-note §3

ITU-T T.38 (04/02) aggregates the original T.38 (06/98) and all subsequent amendments including T.38D-00. The SIP procedures described reference RFC 2543 but can also be applied to the revised SIP specification RFC 3261.

realtime, voip, sip

interoperability-note §4

The image/t38 MIME subtype is intended solely for use as an SDP parameter in SIP call setup for T.38. Use by email applications is not defined and is not guaranteed to interoperate with a T.38 stream.

realtime, voip, sip, email

protocol-element §3.1

The image/t38 media type is used as an SDP media descriptor in SIP call setup for T.38 real-time facsimile, as described in ITU-T Rec. T.38 Annex D. It indicates a T.38 media stream within SDP.

realtime, voip, sip

registry §4

Registers the MIME media type image/t38 with IANA. The subtype has no required or optional parameters, uses binary encoding, and is intended for use as an SDP media descriptor for T.38 real-time facsimile streams.

registry, realtime, voip, sip

security-consideration §5

The image/t38 content denotes a facsimile bit stream that may or may not be encrypted. No mandatory encryption is specified; security is left to the enclosing transport or application layer.

security, realtime, voip