IFX Mail Archive: RE: IFX> Legal Requirements on Classic fax

RE: IFX> Legal Requirements on Classic fax

From: Dan Wing (dwing@cisco.com)
Date: Tue Feb 13 2001 - 21:46:09 EST

  • Next message: MAEDA toru: "RE: IFX> Legal Requirements on Classic fax"

    On Tue, 13 Feb 2001 19:29 +0900, MAEDA toru wrote:

    > Jim-san
    >
    > We designed that the IFAX header is similer as G3 header.
    > The IFAX header consists of date, time,mail address of transmitter and page
    > number.
    > One of reason that fax header is send as image form is character font
    > converting to image.
    > The receiver could not print the information form transmitter
    > when Japanese characters are send from the transmitter in the information.

    Hi.

    RFC2047-encoded headers can handle non-ASCII character sets, including
    Japanese. Almost all common mailers, including Eudora, Netscape, pine,
    and many others, are capable of handling RFC2047-encoded headers when both
    sending and receiving messages.

    -d

    > I know that the user may not understand the Japanese characters in the
    > image header.
    >
    > Regards,
    >
    > Toru Maeda
    >
    >
    > At 08:49 01/02/05 -0500, Jim Dahmen wrote:
    > >Maeda-san,
    > >
    > >When sending a T.37 message, isn't the header information of the email the
    > >same as the information sent in the header of the fax message?
    > >I realize that it is not in the body of the message as the fax header, but
    > >the same information is provided, i.e. when it was sent and who it came
    > >from. I know that this information can be faked, but so can the information
    > >from a fax device.
    > >
    > >Just a thought.
    > >
    > >Best regards,
    > >Jim Dahmen
    > >
    > >
    > > > -----Original Message-----
    > > > From: owner-ifx@pwg.org [mailto:owner-ifx@pwg.org]On Behalf
    > > > Of MAEDA toru
    > > > Sent: Monday, February 05, 2001 2:17 AM
    > > > To: Wagner,William; ifx@pwg.org
    > > > Subject: RE: IFX> Legal Requirements on Classic fax
    > > >
    > > >
    > > > Bill-san
    > > >
    > > > Yes, FCC Part68 only mention about Telephone connected fax.
    > > > There was no legal requirement before junk fax has become
    > > > popular in G3 fax.
    > > >
    > > > Can you imagine that ifax users get many printed SPAM mail
    > > > and junk fax
    > > > which cost some cents per page.
    > > > User will ask to stop printing such useless junk fax.
    > > > Sending date/stamping header may prevent junk IFAX.
    > > > So supporting Part68 for ifax is very important not only for
    > > > user but also
    > > > manufacturer.
    > > >
    > > > Some T.37 fax machine supports fax date/stamping header same
    > > > header as of
    > > > Classic fax,
    > > > I am proposing T.37 Terminal Mode which mandates
    > > > date/stamping, in IETF.
    > > >
    > > > Regrads,
    > > >
    > > > Toru Maeda
    > > >
    > > > At 15:20 01/02/04 -0500, Wagner,William wrote:
    > > > >Maeda-san,
    > > > >
    > > > >Many thanks for this input. I think this raises a very
    > > > important question
    > > > >for IPP-FAX. The PART 68 requirement is very specific to
    > > > Telephone facsimile
    > > > >machines, and applicability to Internet facsimile is not
    > > > obvious. Indeed,
    > > > >PART 68 is only applicable to telephone communications and interface.
    > > > >
    > > > >So far as I can see, T.37 has no mention of date/stamping,
    > > > other than a
    > > > >requirement that offramp gateways "Ensure that local legal
    > > > requirements
    > > > >relating to facsimile transmissions are met". This again applies to
    > > > >telephone connections.
    > > > >
    > > > >Have any date/stamping practices been established for T.37
    > > > implementations
    > > > >in anticipation of legal requirements being set?
    > > > >
    > > > >Thank you.
    > > > >
    > > > >Bill Wagner
    > > > >NetSilicon
    > > > >
    > > > >
    > > > >
    > > > >-----Original Message-----
    > > > >From: MAEDA toru [mailto:maeda.toru@canon.co.jp]
    > > > >Sent: Sunday, January 28, 2001 10:03 PM
    > > > >To: ifx@pwg.org
    > > > >Subject: IFX> Legal Requirements on Clasic fax
    > > > >
    > > > >
    > > > >Hi,
    > > > >
    > > > >Attached is the legal requirements on classic fax in FCC68,
    > > > >during the discussion at Maui meeting.
    > > > >
    > > > >Regards,
    > > > >
    > > > >Toru MAEDA
    > > > >CANON Inc.
    > > > >
    > > > >
    > > > >[Code of Federal Regulations]
    > > > >[Title 47, Volume 3, Parts 40 to 69]
    > > > >[Revised as of October 1, 1998]
    > > > > From the U.S. Government Printing Office via GPO Access
    > > > >[CITE: 47CFR68.318]
    > > > >
    > > > >[Page 338]
    > > > >
    > > > > TELECOMMUNICATION
    > > > >
    > > > > CHAPTER I--FEDERAL COMMUNICATIONS COMMISSION--(CONTINUED)
    > > > >
    > > > >PART 68--CONNECTION OF TERMINAL EQUIPMENT TO THE TELEPHONE
    > > > NETWORK--Table
    > > > >of Contents
    > > > >
    > > > > Subpart D--Conditions for Registration
    > > > >
    > > > >Sec. 68.318 Additional limitations.
    > > > > (d) Telephone facsimile machines; Identification of
    > > > the sender of
    > > > >the message. It shall be unlawful for any person within the United
    > > > >States to use a computer or other electronic device to send
    > > > any message
    > > > >via a telephone facsimile machine unless such message
    > > > clearly contains,
    > > > >in a margin at the top or bottom of each transmitted page or on the
    > > > >first page of the transmission, the date and time it is sent and an
    > > > >identification of the business, other entity, or individual
    > > > sending the
    > > > >message and the telephone number of the sending machine or of such
    > > > >business, other entity, or individual. Telephone facsimile machines
    > > > >manufactured on and after December 20, 1992, must clearly mark such
    > > > >identifying information on each transmitted message.
    > > > >
    > > > >
    > > > >--------------------
    > > > >MAEDA TORU
    > > > >MIE Development Div. 2
    > > > >CANON Inc.
    > > > >--------------------
    > > >
    > > > -----------------------------------
    > > > $B%-%d%N%s3t<02q<R(B
    > > > $B1GA|;vL35!(BMIE$B?d?J%;%s%?!<(B
    > > > $B1GA|;vL35!(BMIE$BBh#23+H/It(B
    > > > $BA0ED!!E0(B
    > > > 146-8501$B!!El5~ETBgED6h2<4];R#3!]#3#0!]#2(B
    > > > $BEEOC!!(B03-3757-9738$B!"(BFAX$B!!(B03-3757-8205
    > > > -----------------------------------
    >
    > --------------------
    > MAEDA TORU
    > MIE Development Div. 2
    > CANON Inc.
    > --------------------
    >



    This archive was generated by hypermail 2b29 : Tue Feb 13 2001 - 21:46:26 EST