[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Simple] Inter-domain Requirements for SIMPLE

Orit,

I am still confused on this requirement.

It sounds like what you want is for the watcher to find out if he has permission to subscribe or fetch presence from the presentity, without actually subscribing or fetching? In other words, it would be a request from the watcher to the presentity to ask the presentity to set an authorization policy for the watcher, in absence of any specific subscription. Is that right?

If so, what is the motivating use case here?

THanks,
Jonathan R.

Orit Levin wrote:

This requirement attempts to say:

A potential watcher asks a presentity to grant access to presentity's
presence information, but the watcher (or more precisely, its PS) is not
interested in the presence information being pushed on individual basis
from this point on. In other words, it can be implemented by just adding
the watcher to presentity's ACL. Or in case of groups, adding the
requesting watcher to a specific group.

Orit.

-----Original Message-----
From: Robert Sparks [mailto:rsparks@dynamicsoft.com] Sent: Wednesday, February 25, 2004 8:48 AM
To: Orit Levin
Cc: IETF SIMPLE WG; Avshalom Houri
Subject: Re: [Simple] Inter-domain Requirements for SIMPLE

Orit, Avshalom -

Thanks for submitting this draft. You've captured some
important thoughts around deploying presence systems that
deserve attention. I particularly look forward to the
discussions we'll have around section 7.3 (Grouping of
Watchers for SHARING of Presence Info).

One quick question: I don't understand what you're looking
for with the first requirement of 7.1:

o Presence access: It MUST be possible to request continuous
access to the status of a remote presentity without
"subscribing" to it.

Could you explain this a little more?

RjS

On Mon, 2004-02-23 at 17:33, Orit Levin wrote:

Guys!
We have submitted a requirements document for secure and efficient
transfer of presence information over inter-domain links.
Please, take a look at our thoughts and suggestions:



http://www.ietf.org/internet-drafts/draft-levin-simple-interdomain-reqs-
00.txt


We look forward to your feedbacks on how we can enhance SIMPLE to
support these directions.

Thanks,
Orit.



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


--
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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