IVR Control Package for Media Control Channel Framework Scott McGlashan, Tim Melanchuk, Chris Boulton draft-ietf-mediactrl-ivr-control-package-00

1
IVR Control Package for Media Control Channel
Framework Scott McGlashan, Tim Melanchuk, Chris
Boulton draft-ietf-mediactrl-ivr-control-package
-00

• IETF 72
• Dublin, Ireland

2
Next version -01

• Address issues identified in -00 Editors Notes
• Address RAI Expert Review comments (thanks to Ben
  Campbell)
• Fix some other nits ..
• Missing defaults in the schema
• Collect and record defaults
• IANA naming e.g. H.263 -gt H263
• Editorial typos, etc
• Then ready for WGLC

3
Issues in -00 Version 1/2

• IVR-200. Would this description benefit from a
  state machine diagram? (Section 4.2)
• Perhaps. Any volunteers skilled in ASCII art?
  Otherwise, no.
• IVR-201. If the conference mixer package supports
  video layout regions, then we need a mechanism to
  specify that the dialog is to be started on a
  specific region of the conference.
  (ltdialogstartgt)
• Update ltstreamgt with ltregiongt child element (as
  defined in Mixer package)

4
Issues in -00 Version 2/2

• IVR-202. What do 'gen' and 'ndn' format mean for
  digits? Terms defined in MSCML (ltvariablegt)
• gen is general number string. ndn is North
  American Dialed Number. Remove ndn.
• IVR-203. Do we need to define additional
  information? specific (rate, speed, etc) or
  generic using ltparamsgt? (ltcodecgt)
• Not unless someone asks for it. Recommend use of
  ltparamsgt.

5
RAI Issues - Substantive

• The security considerations section is very
  light. Do you really believe there are no
  security considerations here beyond those of
  RFC3023? I'm not saying that I know of any
  specific issues, but an almost empty security
  considerations section raises a red flag in my
  head.
• Add link to Framework security. Other security
  issues? Resource usage?

6
RAI Issues - Specific

• Introduction You make ASR explicitly out of
  scope. Is there an effort for extending this to
  support ASR? I note that fully half of the IVR
  applications I interact with these days support
  some degree of ASR.
• Spec says ASR functionality may be addressed
  by other dialog types used with this package,
  extension to this package or other packages.
  Doing this is not a (current) WG goal.
• Chairs Candidate to add to our milestones?

7
RAI Issues - Specific

• 4.2.1, "src" attribute What URI schemes make
  sense here? It probably doesn't need a list of
  specific schemes, but some general guidance would
  help. "mailto" probably does not make sense. Is
  there an error code for "unknown URI scheme"?
• Suggestions for general guidance without being
  specific welcome! Add unsupported URI scheme
  error code.

8
RAI Issues - Specific

• 4.2.5.2, dtmf and timestamp attributes Am I
  correct in assuming that dtmf can hold a string
  of digits? If so, what does the timestamp
  indicate? First digit? Last digit?
• Good catch. Clarify timestamp as last DTMF in
  sequence.

9
RAI Issues - Specific

• 4.3.1 "The behavior is not defined if both
  ltcollectgt and ltrecordgt are specified. Does that
  imply a 2119 normative statement?
• Are we clear on what should happen?
• Will re-word