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

RE: [Simple] Draft on optimized presence federation



Hi,

This draft addresses an important problem, assuming we want to support
SIMPLE based presence between large domains. I think it is also
important to address the problem with minimum affect to the UAs, as this
draft does. The key question seems to be whether we want to allow a
domain to decide how much it wants to reveal on the policies of its
users' policies to a particular other domain. If we set that as a
requirement, I think building upon the ideas proposed in this draft is
the way to go.   

I have one specific question:

Have you considered whether the ACL format can effectively cope with
"domain" and "exception" logic in common policy? For instance the common
policy RFC has a following example rule:

       <rule id="f3g44r1">
           <conditions>
               <identity>
                   <many domain="example.com">
                       <except id="sip:alice at example.com"/>
                       <except id="sip:bob at example.com"/>
                   </many>
               </identity>
           </conditions>
           <actions/>
           <transformations/>
       </rule>

In this kind of case (assuming no other rules) the presence server would
know that everyone else from example.com would get a certain view, while
alice and bob would be blocked. Is this readily supported in ACL doc by
listing two rules there? (BTW, instead of calling the ACL elements
rules, how about calling them e.g. views to avoid confusion with common
policy terminology?) 

Markus


>-----Original Message-----
>From: ext Jonathan Rosenberg [mailto:jdrosen at cisco.com] 
>Sent: 12 November, 2007 17:10
>To: Simple WG
>Subject: [Simple] Draft on optimized presence federation
>
>I've just submitted an I-D that defines a SIP event framework 
>extension called "view sharing". View sharing optimizes the 
>performance of subscriptions inter-domain and is meant as an 
>answer to the scaling analysis and requirements drafts we've 
>been working on. The basic idea is, if there are ten watchers 
>that are interested in the same presentity and will get the 
>same presence document, have just one subscription rather than ten.
>
>Here is a pointer to the draft:
>http://www.ietf.org/internet-drafts/draft-rosenberg-simple-view
>-sharing-00.txt
>
>-Jonathan R.
>-- 
>Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
>Cisco Fellow                                   Parsippany, NJ 
>07054-2711
>Cisco Systems
>jdrosen at cisco.com                              FAX:   (973) 952-5050
>http://www.jdrosen.net                         PHONE: (973) 952-5000
>http://www.cisco.com
>
>
>_______________________________________________
>Simple mailing list
>Simple at ietf.org
>https://www1.ietf.org/mailman/listinfo/simple
>


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