RFC 2886 (rfc2886) - Page 2 of 21
Megaco Errata
Alternative Format: Original Text Document
RFC 2886 Megaco Errata August 2000
Section: 4 "Abbreviations"
----------
Editorial: delete unused abbreviation BRI.
Editorial: add explanations for GSM and IVR.
Section: 6.2.2 "TerminationIDs"
----------
Issue: Not clear what wildcard union responses look like.
Resolution: Add the following text:
"ie. Given termination Ta with properties p1=a, p2=b, and
termination Tb with properties p2=c, p3=d a UNION
response would be T* p1=a, p2=b,c, p3=d."
Section: 6.2.4 "Termination Properties and descriptors"
----------
Issue: Says that property values set in Null context are remembered
and reinstated when termination returns to Null. Contradicts latest
text in 7.2.3.
Resolution: Rewrite the first paragraph from the third sentence
onward, to read: "Most properties have default values, which are
explicitly defined in this standard or in a package (see Section 12)
or set by provisioning. If not provisioned otherwise, all
descriptors except for TerminationState and LocalControl default to
empty/"no value" when a termination is first created or is returned
to the null context. The default contents of the two exceptions are
described in sections 7.1.5 and 7.1.7."
Issue: DigitMap entry in table makes explicit reference to DTMF
tones, but is also intended to apply to other in-band signalling
systems.
Resolution: Change existing text to new one as follows: "Defines
patterns against which sequences of a specified set of events are to
be matched so they can be reported as a group rather than singly."
Section: 6.2.5 "Root Termination"
----------
Issue: Root can have statistics as well as properties and events.
Resolution: add "statistics" to the fourth sentence of the first
paragraph, listing what is valid for Root. Add "statistics" to what
AuditValue can return for Root.
Taylor Standards Track