Re: AW: [Simple] reachibility information for services in current pre sence data mo del

[Henning Schulzrinne <hgs at cs.columbia.edu>]

Unless there is some significant difference between services, you 
wouldn't publish multiple contact addresses for it. Thus

<tuple>
   ... description ...
   sip:foo at somewhere
   sip:bar at example
   sip:123 at whoknows
</tuple>

makes very little sense - why publish three URIs that the observer has 
no way of distinguishing? If there's no annotation, the user can only 
throw darts and pick one.

With the possible exception of having both a "tel" and SIP URI that 
reach the same device, I see little practical use for your description, 
but maybe I'm misunderstanding your use case.

Boehmer Bernhard Com Berlin wrote:
> Hi Henning,
> my assumption is that a user has a certain service available 
> at different locations (devices, agents, etc.) each identified
> by different contact addresses. The user wants to publish all
> these contact addresses for this service. Together with the contact
> information, however, (s)he also publishes also a bunch of other
> information about this service. Due to the fact that only one contact
> is possible in <tuple>, my current understanding is that the user has to publish
> multiple tuples indicating the different contacts but *duplicating*
> the other service information. This information, therefore, seems to 
> be doubled. I would like to avoid this redundancy somehow.

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