2009/4/14 Iñaki Baz Castillo i...@aliax.net:
El Martes 14 Abril 2009, Paul Kyzivat escribió:
I think you are missing that there can be multiple publishers of
presence *about* Alice that are themselves *not* Alice. So:
1) they can't assert that the publish is from Alice, because it isn't
2)
I think there are multiple issues here:
1) what the sender places in the To and R-URI of the PUBLISH
2) Whether the (proxy) server that services the AoR for a
user should be presence-aware and be able to route PUBLISH
requests for presence to the presence server for the AoR
3) What the
2009/4/16 Paul Kyzivat pkyzi...@cisco.com:
If you expect the originator to insert the address of the presence server in
the
R-URI, then it must know that. How would it? That would be yet one more
thing that needs to be configured. The point of an AoR is that it is the
Address of Record for
Hi, RFC 3903 (PUBLISH method) states that the target AoR for a PUBLISH request
is the Request URI.
I don't understand it. Theorically, a UA sends a PUBLISH to a presence server,
and when the presence server receives the PUBLISH it should inspect the From
instead of the RURI (this is what makes
I think you are missing that there can be multiple publishers of
presence *about* Alice that are themselves *not* Alice. So:
1) they can't assert that the publish is from Alice, because it isn't
2) they can't address Alice's presence server because they may not
know it. They just know
El Martes 14 Abril 2009, Paul Kyzivat escribió:
I think you are missing that there can be multiple publishers of
presence *about* Alice that are themselves *not* Alice. So:
1) they can't assert that the publish is from Alice, because it isn't
2) they can't address Alice's presence server
