RE: [Simple] notes from the SIMPLE components adhoc at IETF53

On 06 April 2002 00:11, Paul Kyzivat wrote:
> Callerprefs provide a number of dimensions on which to classify a 
> contact (tuple). These could be mapped directly to status values. Or 
> they could be mapped to some new elements within a tuple. They are a 
> bit more complex than the what is currently defined by 
> urn:ietf:params:cpim-presence:status-type:basic. There are a number of

> preference parameter types (class, duplex, feature, language, media, 
> mobility, methods, priority), and each in turn has an enumerated set 
> of possible values. (There is also a "description" parameter, but it 
> probably should be mapped to <note>, and a q-value that is already 
> represented as the priority attribute of <contact>.)

A new draft describing IMPP PIDF has been posted and should show up
shortly. It includes changes from recent IMPP discussions but still
leaves a few issues outstanding.

One question I have with reference to the text above is regarding the
priority attribute of <contact>. In the current draft, the priority is
defined in the range 0 to 255. The description above suggests mapping a
q-value to the priority. What range does this have? Do you feel the
priority as currently defined is appropriate or are there any
alternative suggestions?

Best regards,

Adrian.




  [reminder: [email protected] for non-technical discussions, please]