Hi Dale, ext [EMAIL PROTECTED] wrote: > From: Aki Niemi <[EMAIL PROTECTED]> > > - There is a single authoritative notifier agent responsible for any > single resource. > > - A resource is identified using a SIP URI. > > - A subscriber subscribes to a resource using the SIP URI. > > Often a subscriber will send the SUBSCRIBE to a URI which is not the > request-URI of the SUBSCRIBE when it reaches the notifier agent. This > happens due to normal SIP request routing, but the routing can also > change with time.
Correct, but are you saying there might be more than one agent with a different idea on the entity-tags of entities pertaining to a certain resource? In other words, that the resource has multiple agents that may have a different view of the resource state? I believe this is disallowed per RFC3265 already. > - Each entity has an assigned entity-tag. > > Each entity has a succession of versions. Each version of each entity > has an assigned entity-tag. Yes. > - There is a one-to-many relationship between an entity and its versions > (different etag values, of which only one is current). > > - An entity-tag must be unique across all versions of all entities from > a resource. > > Does this rule out hash-based entity-tags, which are only > probabalistically unique? No, I think this MUST statement should probably be followed with an implementation note that talks about what's reasonably unique in this context. Cheers, Aki _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
