RE: [Sipping] Expiration of permissions in consent
"Henry Sinnreich" <henry@pulver.com> Wed, 23 November 2005 14:27 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eevat-0004ra-Ou; Wed, 23 Nov 2005 09:27:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eevar-0004rV-Th for sipping@megatron.ietf.org; Wed, 23 Nov 2005 09:27:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08028 for <sipping@ietf.org>; Wed, 23 Nov 2005 09:26:50 -0500 (EST)
Message-Id: <200511231426.JAA08028@ietf.org>
Received: from mail.pulver.com ([192.246.69.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eevtj-0004ag-4t for sipping@ietf.org; Wed, 23 Nov 2005 09:47:00 -0500
Received: (qmail 13484 invoked by uid 510); 23 Nov 2005 09:52:07 -0500
Received: from henry@pulver.com by mail.pulver.com by uid 508 with qmail-scanner-1.22-st-qms (clamdscan: 0.72. spamassassin: 2.63. Clear:RC:1(24.1.142.34):. Processed in 0.950492 secs); 23 Nov 2005 14:52:07 -0000
X-Antivirus-MYDOMAIN-Mail-From: henry@pulver.com via mail.pulver.com
X-Antivirus-MYDOMAIN: 1.22-st-qms (Clear:RC:1(24.1.142.34):. Processed in 0.950492 secs Process 13479)
Received: from c-24-1-142-34.hsd1.tx.comcast.net (HELO 1AB764895C324D3) (henry@pulver.com@24.1.142.34) by 192.246.69.184 with SMTP; Wed, 23 Nov 2005 14:52:06 +0000
From: Henry Sinnreich <henry@pulver.com>
To: 'Gonzalo Camarillo' <Gonzalo.Camarillo@ericsson.com>, 'sipping' <sipping@ietf.org>
Subject: RE: [Sipping] Expiration of permissions in consent
Date: Wed, 23 Nov 2005 08:27:20 -0600
Organization: pulver.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-reply-to: <438462DF.7060906@ericsson.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-index: AcXwO3zzZlYkNbRmTMeQ/7qm70wbbgAAeVsg
X-Antivirus-MYDOMAIN-Message-ID: <113275752683513479@mail.pulver.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: 'Dean Willis' <dean.willis@softarmor.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: henry@pulver.com
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
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. Thanks, Henry -----Original Message----- From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] 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 sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org 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 sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] Expiration of permissions in consent Gonzalo Camarillo
- RE: [Sipping] Expiration of permissions in consent Henry Sinnreich
- Re: [Sipping] Expiration of permissions in consent David R Oran
- Re: [Sipping] Expiration of permissions in consent Gonzalo Camarillo
- [Sipping] Re: Expiration of permissions in consent Jonathan Rosenberg
- Re: [Sipping] Expiration of permissions in consent Dean Willis
- Re: [Sipping] Expiration of permissions in consent Miguel Garcia