Hi,
the current presence data model discusses nicely reachability
information. Maximum openess concerning the definition of
a service is maintained. However, in the actual definition
of the <tuple> - being the legacy of pidf - reachability information
is restricted to one entry, the <contact> element. Thus, within
one <tuple> element the possibility that a service may be reachable
via different, e.g., addresses cannot be reflected. The only way I
see currently is to send two <tuple> elements with basically the same
information but the <contact>/reachability information.
From my perspective this introduces quite some redundancy in the presence
doc (a point which is especially relevant for mobile networks) and
is furthermore asymmetric to possibility to introduce several device ids
into one <tuple> element (the latter, however, not being made explicit
by the XML schema).
So, my question is: Have you once considered to add more than one piece
of reachability information and you have rejected this possibility or
do you share the view that this means should be introduced?
Regards Bernhard
___________________________
Dr. Bernhard Böhmer
Systems Engineering
Siemens AG Communications,
Mobile Networks AS BD C
Siemensdamm 50, Berlin
Fon: +49-30-386-22756
Mobile: +49-178-7700119
_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple