RFC Errata
Found 15 records.
Status: Verified (15)
RFC 5022, "Media Server Control Markup Language (MSCML) and Protocol", September 2007
Source of RFC: INDEPENDENT
Errata ID: 1239
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.1.1.1 says:
Attributes of <audio>: o url - required, no default value: The URL of the content to be retrieved and played. The target may be a local or remote (NFS) "file://" scheme URL or an "http://" or "https://" scheme URL. If the URL is not fully qualified and a "baseurl" attribute was set, the value of the "baseurl" attribute will be prepended to this value to generate the target URL.
It should say:
< see Notes >
Notes:
Again, the RFC should make use of standard terminology
established in the IETF.
STD 66, RFC 3986 should be used here.
The attribute, 'url', should better have been named 'uri'.
Consequently, all subsequent references to an URL w.r.t. this
attribute should be replaced by "URI" or "URI reference", as
appropriate.
Authors comment: This is really an Editorial erratum. If it were to be changed, it should be changed consistently throughout the document.
Errata ID: 1242
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.1.1.1. says:
o rate - optional, default value "0": Specifies the absolute playback rate of the content relative to normal as either a positive percentage (faster) or a negative percentage (slower). Any value that attempts to set the rate above the maximum allowed or below the minimum allowed silently sets the rate to the maximum or minimum. The rate reverts back to its original value when playback of the content URL has been completed.
It should say:
| o rate - optional, default value "0": Specifies the deviation of the | content playback rate from its normal value as either a positive percentage (faster) or a negative percentage (slower). Any value that attempts to set the rate above the maximum allowed or below the minimum allowed silently sets the rate to the maximum or minimum. The rate reverts back to its original value when | playback of the content specified by the URI has been completed.
Notes:
There is perfect confusion between 'absolute' and 'relative",
leaving this specification open to gross misunderstanding.
I hope the proposed replacement text says what had been intended
to say; it also corrects sluggish language and applies STD 66 terms.
Errata ID: 1247
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.5.3, p.41 says:
The recording example (Figure 19) plays a prompt and records it to the destination specified in the "recurl" attribute encoded as MS-GSM in wave format.
It should say:
| The recording example (Figure 19) plays a prompt and records the | response to the destination specified in the "recurl" attribute encoded as MS-GSM in wave format.
Notes:
The RFC text is ambiguous/misleading; what does 'it' refer to ?
I guess that nobody will be interested in recording the prompt.
Therefore, I hope the clarification above says what has been intended.
Errata ID: 1248
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 8, page 48 says:
Managecontent Attributes: o src - required, no default value: Specifies the local source URL of the content. The URL scheme MUST be "file://". o dest - required (see note), no default value: Specifies the destination URL. The URL scheme MUST be "http://". Note: If the selected action is 'delete', this attribute is optional; otherwise it is required.
It should say:
Managecontent Attributes: | o src - required, no default value: Specifies the local source URI | of the content. The URI scheme MUST be "file". o dest - required (see note), no default value: Specifies the | destination URI. The URI scheme MUST be "http". Note: If the selected action is 'delete', this attribute is optional; otherwise it is required.
Notes:
a)
The RFC should follow STD 66, RFC 3986 terminology and syntax.
URI schemes do not allow ':' and '/' -- see Section 3.1 (p.17) of RFC 3986.
b) ... MUST be "http" ...
Why the hack does the RFC explicitely forbid using HTTP security
and the "https" URI scheme ????
(I do not believe the authors expect the use of "Upgrade to TLS"
within HTTP, which is rarely implemented -- although it once was
intended as a generice security layer drop-in mechanism.)
Authors comment: Yes, HTTP is a MUST implement, though not the only option here.
Errata ID: 1234
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 5.5 says:
A client can modify a leg by issuing an INFO on the dialog associated | with the participant leg. For example, Figure 8 mutes a conference leg.
It should say:
A client can modify a leg by issuing an INFO on the dialog associated | with the participant leg. For example, the request in Figure 8 mutes a conference leg.
Notes:
Text below Figure 7 (on page 15) is misleading.
Figure 8 is printed on the paper sheet in my hand
and does not mute anything :-)
Errata ID: 1235
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 5.7, 3rd par says:
| A request for an active talker report is in Figure 9. The active talker report enumerates the current call legs in the mix.
It should say:
| A request for an active talker report is shown in Figure 9. The active talker report enumerates the current call legs in the mix.
Notes:
Improved language.
Errata ID: 1236
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 5.8.2.3 says:
The corresponding MSCML request is as follows. <?xml version="1.0"?> <MediaServerControl version="1.0"> ... Figure 12: Join Agent Request
It should say:
The corresponding MSCML request is as follows. | <?xml version="1.0"?> <MediaServerControl version="1.0"> ... Figure 12: Join Agent Request
Notes:
On page 22, the XML shown in Figure 12 should have been separated
from the preceding text with a blank line.
The same issue recurs in Section 5.8.2.4 below (on the same page),
with respect to Figure 13.
Errata ID: 1240
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.1.1.1. says:
o gain - optional, default value "0": Sets the absolute gain to be applied to the content URL. [...]
It should say:
o gain - optional, default value "0": Sets the absolute gain to be applied to the content specified by the URI. [...]
Notes:
Sluggish language --
can't mute an URI, or apply gain to an URI ! :-)
Note that other errata request the change from URL to URI throughout.
Errata ID: 1241
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.1.1.1 says:
o gaindelta - optional, default value "0": Sets the relative gain to | be applied to the content URL. The value of this attribute is specified in units of dB. The media server MAY silently cap values that exceed the gain limits imposed by the platform. The level reverts back to its original value when playback of the | content URL has been completed.
It should say:
o gaindelta - optional, default value "0": Sets the relative gain to | be applied to the content specified by the URI. The value of this attribute is specified in units of dB. The media server MAY silently cap values that exceed the gain limits imposed by the platform. The level reverts back to its original value when | playback of the content has been completed.
Notes:
Again, sluggish language (and non-use of STD 66 terminology).
Errata ID: 1243
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.1.1.1 p.29 says:
Spoken variables are specified using the <variable> element. This element has the attributes described in the list below. MSCML's | spoken variables are based on those described in Audio Server Protocol [17].
It should say:
Spoken variables are specified using the <variable> element. This element has the attributes described in the list below. MSCML's | spoken variables are based on those described in the Audio Server Protocol [17].
Notes:
Missing article (mid-page 29).
Author comment: Good catch.
Errata ID: 1245
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.4.3 says:
a) ... "immediate" and "infinite." (3 instances) b) ... returnkey is set to #, ...
It should say:
a) ... "immediate" and "infinite". (3 instances) b) ... returnkey is set to "#", ...
Notes:
a) Syntax error; apply 'rational quotation' !
The issue occurs in the 1st, 3rd, and 4th bullet on page 35.
b) Clarification; the single pound character needs to be double-quoted
in the XML anyway, isn't it?
This also will make the text more uniform.
Errata ID: 1246
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 6.5.2, p.40 says:
."
It should say:
".
Notes:
Again, in the second to seventh bullet on page 40,
'rational quotation' should be applied (6 instances).
Errata ID: 1249
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 8, page 49 says:
o name - required (see note), no default value: Specifies the field name for the content in the form when using the 'post' method. This is not to be confused with the "src" or "dest" attributes. | Note: This attribute is required when the "htttpmethod" has the value "post" and is optional otherwise.
It should say:
o name - required (see note), no default value: Specifies the field name for the content in the form when using the 'post' method. This is not to be confused with the "src" or "dest" attributes. | Note: This attribute is required when the "httpmethod" attribute has the value "post" and is optional otherwise.
Notes:
A typo, and sluggishly inprecise use of language.
Errata ID: 1251
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 8.1, last pa says:
." (2 instances)
It should say:
".
Notes:
The last paragraph of Section 8.1 again contains two syntax errors
based non non-pplication of 'rational quoting'.
Errata ID: 1254
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Verifier Name: Nevil Brownlee
Date Verified: 2011-03-28
Section 9.2, Table 5 says:
... it MUST match remote terminal's identifier ...
It should say:
... it MUST match the remote terminal's identifier ...
Notes:
Insert the missing article in the 5th line from the bottom of Figure 5.