Re: [Sipping] Expiration of permissions in consent

[David R Oran <[e-mail]>]

On Nov 23, 2005, at 9:27 AM, Henry Sinnreich wrote:

> I vote to keep REQ 7 so that forgetful users would not be abused.
> This is similar to many IETF mailing lists renewals.
> Soft state has many advantages.
>
True, but in today's usage the mailing list maintainance sends out  
notifications for to remind that the subscription is active. It isn't  
a notification of impending removal that has to be responded to, nor  
a mechanism that allows subscriptions to silently expire.

I agree that soft state has advantages, but exploders have a lot of  
hard state already so adding some form of expiration may make sense.  
On the other hand, it may be useful to build this into the  
application on that is using the consent framework rather than the  
consent operations themselves.

I think the feature is useful, but I'm not sure delaying te consent  
framework in order to satisfy this is the right tradeoff.

Dave.

> Thanks, Henry
>
>
>
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On  
> Behalf
> Of Gonzalo Camarillo
> Sent: Wednesday, November 23, 2005 6:39 AM
> To: sipping
> Cc: Dean Willis
> Subject: [Sipping] Expiration of permissions in consent
>
> 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
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [e-mail] for questions on current sip
> Use [e-mail] for new developments of core SIP
>
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [e-mail] for questions on current sip
> Use [e-mail] for new developments of core SIP

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP