[Simple] draft-ietf-simple-prescaps-ext-10 comment

["Eric Tremblay" <eric.m.tremblay at gmail.com>]

Hi Mikko & Krisztian,

In section 3.2.14:
I wonder if representing winfo support in the <event-packages> element
as a single <winfo> element makes sense. Just putting <winfo> under a
<supported> element does not mean that an application supports
watcher-info for all events enumerated there.

I think that winfo should somehow apply to an other event. Without an
existing grammar to represent recursive template support (or
limitations of such support), I would suggest representing a single
level of support and then applications could assume that if
presence.winfo is supported, then presence.winfo.winfo should also be
supported. A bug already exists to track this issue:
http://bugs.sipit.net/show_bug.cgi?id=711

I suggest two options:

1) Allowing an optional <winfo> element under the other event types
(<conference>, <dialog>, <kpml>, <message-summary>, <poc-settings>,
<presence>, <reg>, <refer>, <Siemens-RTP-Stats>, <spirits-INDPs>,
<spirits-user-prof>) to indicate that winfo is supported for that
specific event type.

2) Allowing an optional "template" attribute to the event types which
could contain a comma separated list of templates supported for this
event type. <conference template="winfo,foo">

How do we then represent the fact that a device only supports
conference.winfo but not conference? Maybe an additional attribute
could do the trick...

Best Regards,

EricT
_______________________________________________
Simple mailing list
Simple at ietf.org
https://www.ietf.org/mailman/listinfo/simple