RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 3965, "A Simple Mode of Facsimile Using Internet Mail", December 2004

Source of RFC: fax (app)

Errata ID: 711
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2005-01-04
Held for Document Update by: Alexey Melnikov

 

a) Change the first sentence of section 2.1.3, on page 4, from:

  "An offramp gateway that operate as an MTA serving multiple users
   SHOULD use SMTP;" ...

to:

| "An offramp gateway that operates as an MTA serving multiple users
   SHOULD use SMTP;" ...

b) Change the first sentence of section 2.2.4, on page 4, from:

  "A single multi-page document SHOULD be sent as a single multi- page
   TIFF file, even though recipients MUST process multipart/mixed
   containing multiple TIFF files."

to:

| "A single multi-page document SHOULD be sent as a single multi-page
   TIFF file, even though recipients MUST process multipart/mixed
   containing multiple TIFF files."

c) Change section 5.1. on page 6 from:

  "This specification is based on use of existing Internet mail.  To
   maintain interoperability with Internet mail, any security to be
   provided should be part of the of the Internet security
   infrastructure, rather than a new mechanism or some other mechanism
   outside of the Internet infrastructure."

to:

| "This specification is based on the use of existing Internet mail.
   To maintain interoperability with Internet mail, any security to be
|  provided should be part of the Internet security infrastructure,
   rather than a new mechanism or some other mechanism outside of the
   Internet infrastructure."

d) Change the final sentence of section 5.2, on page 6, from:

                 ... "This section reviews relevant concerns about
   Internet mail for IFax environments, as well as considering the
   potential problems which can result of integrating the existing G3Fax
   service with Internet mail."

to:
                 ... "This section reviews relevant concerns about
   Internet mail for IFax environments, as well as considering the
|  potential problems which can result from integrating the existing
   G3Fax service with Internet mail."

e) Change the first paragraph of section 5.2.1, on page 6, from:

   "The actual sender of the message might not be the same as that
   specified in the Sender or From fields of the message content headers
   or the MAIL FROM address from the SMTP envelope."

to:

   "The actual sender of the message might not be the same as that
   specified in the Sender or From fields of the message content headers
|  or the MAIL FROM address in the SMTP envelope."

f) Change the second-to-last paragraph of section 5.2.2, on page 7,
from:

  "Originator authentication entails the use of weak or strong
   mechanisms, such as cleartext keywords or encryption-based
   data-signing, respectively, to determine and validate the identify
   of the sender and assess permissions accordingly."

to:

  "Originator authentication entails the use of weak or strong
   mechanisms, such as cleartext keywords or encryption-based
|  data-signing, respectively, to determine and validate the identity
   of the sender and assess permissions accordingly."

g) Change the first sentence of the last paragraph of section 5.2.3,
on page 8, from:

  "Typically authorization needs to be associated to specific senders
   and specific messages, in order to prevent a "replay" attack which
   causes and earlier authorization to enable a later dial-out by a
   different (and unauthorized) sender." ...

to:

| "Typically authorization needs to be associated with specific senders
   and specific messages, in order to prevent a "replay" attack which
|  causes an earlier authorization to enable a later dial-out by a
   different (and unauthorized) sender." ...

It should say:

[see above]

Notes:

from pending

Report New Errata