[Sipping] Re: Expiration of permissions in consent

I think this requirement was more appropriate before we had fully 
thought through roles here. In the framework now, we are seeking to put 
minimal capabilities in the relay in the "other network", and leaving 
more complicated permissions in the servers in a user's own network. 
Supporting of time-limited permissions means that the server needs to 
worry about refreshes, making it have to do more work.

So, my vote is to remove.

-Jonathan R.

Gonzalo Camarillo wrote:

> Folks,
> 
> there is a last open issue in the consent requirements draft:
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-consent-reqs-01.txt
> 
> The open issue has to do with requirement number 7:
> 
>    REQ 7: It shall be possible for the users to specify that permissions
>       are time limited, and must be refreshed after expiration.
> 
> The idea is that the relays storing consent state for a particular user 
> do not need to be in the same administrative domain as the user. 
> Therefore, the state information to be stored should be as little as 
> possible. That's why we have removed allowed operations from the 
> permission documents.
> 
> Now, storing expiration information requires a little more logic in the 
> relay, but, on the other hand, having permissions that expire could be a 
> useful feature in some scenarios.
> 
> The open issue is: do we keep or remove REQ 7?
> 
> Note that when you subscribe to an email mailing list, you do not 
> typically set any expiration time for your subscription. So, I lean 
> towards removing REQ 7 but do not have a strong opinion.
> 
> Opinions?
> 
> Thanks,
> 
> Gonzalo
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
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