RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 6 records.

Status: Held for Document Update (6)

RFC 5347, "Media Gateway Control Protocol Fax Package", October 2008

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 1600

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Held for Document Update by: Robert Sparks

Section 2.1.1,pg.6/7 says:

a)  last paragraph on page 6:

   The Call Agent instructs the gateway to perform the media change by
   sending it a ModifyConnection command with "image/t38" listed as the
   encoding method in the LocalConnectionOptions (receipt of a
   ModifyConnection command without LocalConnectionOptions but with a
|  RemoteConnectionDescriptor containing an "m=" line with the MIME type
   "image/t38" would achieve the same).  [...]

b)  second paragraph on page 7:

                     [...].  The T.38 fax procedure continues when an
   acceptable RemoteConnectionDescriptor is received.  An acceptable
   RemoteConnectionDescriptor contains an "m=" line with the "image/t38"
|  MIME type (using the normal SDP syntax) and a supported transport
   protcol (UDPTL or TCP).  [...]

It should say:

a)
   The Call Agent instructs the gateway to perform the media change by
   sending it a ModifyConnection command with "image/t38" listed as the
   encoding method in the LocalConnectionOptions (receipt of a
   ModifyConnection command without LocalConnectionOptions but with a
|  RemoteConnectionDescriptor containing an "m=" line with the media
   type "image/t38" would achieve the same).  [...]

b)

                     [...].  The T.38 fax procedure continues when an
   acceptable RemoteConnectionDescriptor is received.  An acceptable
   RemoteConnectionDescriptor contains an "m=" line with the "image/t38"
|  media type (using the normal SDP syntax) and a supported transport
   protcol (UDPTL or TCP).  [...]

Notes:

Rationale:

BCP 13, RFC 4288, has re-enforced the terminology from
RFC 2045 ff. The 'IM' in "MIME" stands for 'Internet Mail'.
As pointed out in RFC 4288, it makes no sense to remain stuck
with the colloquial abuse of language, talking about "MIME types",
in particular when Media Types are used outside the scope of
Internet Mail; the MGCP context is one specific example of
such a scenario. Hence, the RFC should use the terminology
established in the IETF, as explained in RFC 4288.

Errata ID: 1601

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Held for Document Update by: Robert Sparks

Section 2.1.4, pg.9 says:

<< near the top of page 9 >>:

|     * the relevant MIME media type, e.g., "image/t38", is included in
        the "m=" line in the RemoteConnectionDescriptor, or

|     * the relevant MIME media type is included as a capability (see
        [RFC3407]) in the RemoteConnectionDescriptor.

It should say:

|     * the relevant media type, e.g., "image/t38", is included in the
        "m=" line in the RemoteConnectionDescriptor, or

|     * the relevant media type is included as a capability (see
        [RFC3407]) in the RemoteConnectionDescriptor.

Notes:

Rationale: See Errata for Section 2.1.1, Eid=1600.

Errata ID: 1603

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Held for Document Update by: Robert Sparks

Section 3.2, pg.33 says:

<< in step 14 >>:

   The Call Agent then instructs the terminating gateway to use the
|  "image/t38" MIME type instead:
|

It should say:

   The Call Agent then instructs the terminating gateway to use the
|  "image/t38" media type instead:

Notes:

Rationale:
See Errata Note for same issue for Section 2.1.1, Eid=1600.

Errata ID: 1605

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Held for Document Update by: Robert Sparks

Section 3.3, pg.43 says:

a)   << Steps 15, 16 >>

|  The originating endpoint detects V.21 fax preamble.  Even though the
   endpoint is already using "image/t38" for media, it generates a
   "t38(start)" event and notifies the Call Agent.

b)   << Step 23 >>

   The originating endpoint also generates a "t38(stop)" event, which is
   notified to the Call Agent:

|     NTFY 3502 ds/ds1-1/1@gw-o.example.net MGCP 1.0 O: t38(stop) X: 2


It should say:

a)

|  The originating endpoint detects the V.21 fax preamble.  Even though
   the endpoint is already using "image/t38" for media, it generates a
   "t38(start)" event and notifies the Call Agent.

b)

   The originating endpoint also generates a "t38(stop)" event, which is
   notified to the Call Agent:

|     NTFY 3502 ds/ds1-1/1@gw-o.example.net MGCP 1.0
|     O: t38(stop)
|     X: 2

Notes:

Rationale:

a) Missing definite article.

b) Confusing formating, inconsistent with all other message examples.

Errata ID: 1602

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Held for Document Update by: Robert Sparks

Section 3.2, pg.29 says:

<< last line of first paragraph >>:

   Furthermore, the originating fax machine is generating CNG tone.

It should say:

   Furthermore, the originating fax machine is generating a CNG tone.
                                                         ^^^

Notes:

Rationale: Missing indefinite article.

Errata ID: 1604

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2008-11-17
Held for Document Update by: Robert Sparks
Date Held: 2010-12-17

Section 3.3, pg.37 says:

<<  last line of first paragraph >>:

   Once again, the originating fax does not generate CNG tone.

It should say:

   Once again, the originating fax does not generate a CNG tone.
                                                    ^^^

Notes:

Rationale: Missing indefiniet article; it should be used
consistently.

--- From the RAI reviewer
Recommended status: (incorrect) Rejected

Thinking about this some more (and in contradiction to my report on
erratum 1602 on this RFC), the intention of the text is to use "CNG
tone" as a mass noun, and so it does not take an indefinite article.

I believe that use of such phrases as "CNG tone" as a mass noun is
more common in British English than American English. This RFC
appears to follow the British convention, with the sole exception of
the first line of "Steps 9-12" on page 33 of section 3.2, which I now
consider to be an error.
======================================================================

Report New Errata



Search RFCs
Advanced Search
×