From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Date: Thu, 22 Nov 2012 14:59:42 +0100
Thread-Topic: [MMUSIC] T.38 (Re: M-line philosophy (Re: Wisdom sought:
 Prioritization of codecs))
Thread-Index: Ac3Itsv14bj2MiQoQIivv6tR4UFhowAAN0Ng
Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9623DF0C4376@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com>
References: <50AE2838.9000807@ericsson.com> <50AE2B02.2020900@ericsson.com>
In-Reply-To: <50AE2B02.2020900@ericsson.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MMUSIC] T.38 (Re: M-line philosophy (Re: Wisdom sought:
 Prioritization of codecs))
Precedence: list

Looks like that your are describing T.37 FoIP behaviour, whereas Adam did p=
oint on T.38 FoIP.

WebRTC should firstly agree
a) whether fax is part of this conversational realtime multimedia service a=
t all,
and if,
b) which transport mode via IP.

To a): support of F.185 (Internet fax) Yes/No
To b):=20
	b.1) T.37 FoIP store-and-forward already sufficient Yes/No
	b.2) T.38 FoIP realtime required Yes/No ((perhaps T.38 over RTP/UDP or UDP=
TL/UDP))
	b.3) or any alternative to T.38 FoIP realtime Yes/No

NOTE: T.38 would specify the behaviour of the=20
1) PSTN gateway (as "T.38 gateway", which is always a PSTN-to-IP gateway) a=
nd
2) Browser (as "T.38 IAD" (Internet aware fax device))
in below illustration.

-Albrecht

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of=
 Stefan Hakansson LK
Sent: Donnerstag, 22. November 2012 14:39
To: mmusic@ietf.org
Subject: Re: [MMUSIC] T.38 (Re: M-line philosophy (Re: Wisdom sought: Prior=
itization of codecs))

On 11/20/2012 15:56, Adam Roach wrote:
>
>
>    +---------+   +------------+   +---------+
>    | Web App |---| SIP Server |---|         |
>    +---------+   +------------+   |         | +-------------+
>         |                         | PSTN GW |--| Fax Machine |
>    +---------+      media         |         | +-------------+
>    | Browser |--------------------|         |
>    +---------+                    +---------+

For cases when one client is not a proper fax machine, is not the usual=20
thing that is done that the facsimile is converted to/from TIFF, JPEG,=20
PDF or similar somewhere between that client and the fax machine? (And=20
often sent as a mail attachment)

If so, all tools are already available (e.g. File API if you want to=20
store/access on the local file system, XHR or WebSockets - or even the=20
rtcweb data channel for transport) to build a client that can handle=20
fax. (I am probably missing something)

Stefan

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic