Re: Operation permissions on Read-Only objects in a table

"Randy Presuhn" <randy_presuhn@mindspring.com> Tue, 24 June 2008 20:28 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81A143A6806; Tue, 24 Jun 2008 13:28:07 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 525D73A67F7 for <ietf@core3.amsl.com>; Tue, 24 Jun 2008 13:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level:
X-Spam-Status: No, score=-1.856 tagged_above=-999 required=5 tests=[AWL=0.743, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZRe9rj4H7Pc0 for <ietf@core3.amsl.com>; Tue, 24 Jun 2008 13:28:05 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 8EF393A6800 for <ietf@ietf.org>; Tue, 24 Jun 2008 13:28:05 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=E/IG7Kv5l6FZg8wMLAGM6G81p1mhn380dafA9Ml+Got9p6FRkc9UNQAMYLSZFIXG; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [69.3.144.108] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1KBF7U-0008U2-9H for ietf@ietf.org; Tue, 24 Jun 2008 16:28:04 -0400
Message-ID: <007501c8d638$fe171f60$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <021c01c8d5e0$a38a9ca0$1edda8c0@dlh.st.com>
Subject: Re: Operation permissions on Read-Only objects in a table
Date: Tue, 24 Jun 2008 13:29:23 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a63b7957ab9b23b3d365e6d989f538ec709e93e8e1dbfab4350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.3.144.108
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi -

> From: "Aditya JAIN" <aditya.jain@st.com>
> To: <ietf@ietf.org>
> Sent: Tuesday, June 24, 2008 2:56 AM
> Subject: Operation permissions on Read-Only objects in a table
...
> Suppose we have a table in which some objects are read-only, and at least
> one columnar object which has MAX- ACCESS = read-create. Does this imply
> that we cannot delete that instance row by setting status to "destroy", if
> we have created one?
...

No.

See the DESCRIPTION of RowStatus in RFC 2579.  Successfully setting a
RowStatus object to "destroy" deletes all the corresponding instances
in a row, regardless of their  MAX-ACCESS.

Randy

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf