[Sipping] Pushing Policies towards the Sender's Domain

Hi all,

when reading through the documents I came across the following statement 
in <draft-niccolini-sipping-spitstop-00.txt>:

"
   Please note that the described reference scenario does not addresses
   management interfaces to entities involved in SPIT prevention.  A
   first approach to this issue has been made is described in
   [I-D.froment-sipping-spit-authz-policies].
"

it seems that some parts of 
<draft-froment-sipping-spit-authz-policies-02.txt> got misunderstood.

There are some text paragraphs in 
<draft-froment-sipping-spit-authz-policies-02.txt> that envisioned that 
the authorization policies are distributed to other domains, and in 
particular towards the sender's domain. There is obviously the question 
what you would but in these policy documents, when to distribute them 
and whether there are potential privacy problems with that approach.

This is an interesting technical issue BUT I would put it on my priority 
list for work that has to be done in the SPIT prevention space to the 
end of the queue. This lead us actually to create a new document (see 
http://fon.gs/spit-requirements)  that focuses purely on requirements 
for authorization policies that are not distributed between domains.

I wonder what other people think about pushing policies towards the 
sender's domain.

Ciao
Hannes

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP