RE: [imss] MIB doctor review for T11-FC-SP-ZONING-MIB

"Bert Wijnen - IETF" <bertietf@bwijnen.net> Fri, 04 January 2008 18:49 UTC

Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JArbX-0004M9-TE; Fri, 04 Jan 2008 13:49:15 -0500
Received: from imss by megatron.ietf.org with local (Exim 4.43) id 1JArbX-0004M4-2T for imss-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 13:49:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JArbW-0004Lv-Ou for imss@ietf.org; Fri, 04 Jan 2008 13:49:14 -0500
Received: from relay.versatel.net ([62.250.3.110]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JArbU-0001O2-Ej for imss@ietf.org; Fri, 04 Jan 2008 13:49:14 -0500
Received: (qmail 35081 invoked from network); 4 Jan 2008 18:49:11 -0000
Received: from unknown (HELO bwMedion) (87.215.199.34) by relay.versatel.net with SMTP; 4 Jan 2008 18:49:11 -0000
From: "Bert Wijnen - IETF" <bertietf@bwijnen.net>
To: "Keith McCloghrie" <kzm@cisco.com>
Subject: RE: [imss] MIB doctor review for T11-FC-SP-ZONING-MIB
Date: Fri, 4 Jan 2008 19:49:24 +0100
Message-ID: <NIEJLKBACMDODCGLGOCNEELGEEAA.bertietf@bwijnen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <200801041800.KAA04384@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: imss@ietf.org, Black_David <Black_David@emc.com>, Dan Romascanu <dromasca@avaya.com>
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
Errors-To: imss-bounces@ietf.org

Yes, now we are in agreement

Bert Wijnen

> -----Oorspronkelijk bericht-----
> Van: Keith McCloghrie [mailto:kzm@cisco.com]
> Verzonden: vrijdag 4 januari 2008 19:00
> Aan: Bert Wijnen - IETF
> CC: Keith McCloghrie; imss@ietf.org; Black_David; Dan Romascanu
> Onderwerp: Re: [imss] MIB doctor review for T11-FC-SP-ZONING-MIB
>
>
> Extracting the one issue out of your response:
>
> > > >    t11FcSpZoneSetHashStatus OBJECT-TYPE
> > > >        SYNTAX       INTEGER {
> > > >                      calculate(1),
> > > >                      correct(2),
> > > >                      stale(3)
> > > >                     }
> > > >
> > > >    That SYNTAX a number of times in the set of MIB modules.
> > > >    Candidate for a TC?
> > >
> > > Done.
> > >
> > > > - FOr that same object, I wonder how a re-calculate can be done
> > > >   for a permanent row, since the storage type states:
> > > >
> > > >            If an instance of this object has the value
> > > >            'permanent(4)', the Zone Set database for the given
> > > >            fabric on the given switch is not required to be
> > > >            writeable."
> > >
> > > Assuming that I've correctly understood your question, I'll add:
> > > a sentence in the DESCRIPTION of t11FcSpZoneSetHashStatus to say:
> > >
> > >     If and when the corresponding instance of
> > >     t11ZsServerDatabaseStorageType (defined in RFC 4936) has the value
> > >     'permanent(4)', then if any the instance of an object in
> if any row
> >
> > "if any the instance" ??  do you mean "if any instance"
> > "in if any row" ?? maybe remove the last "if" ??
>
> Sorry for the confusion, let me try again:
>
>      If and when the corresponding instance of
>      t11ZsServerDatabaseStorageType (defined in RFC 4936) has the value
>      'permanent(4)', then if write access is supported to any instance of
>      a read-write object in any row of any table governed by the
>      'permanent' value of t11ZsServerDatabaseStorageType, then write
>      acces to the corresponding instance of this object must also be
>      supported.
>
> > >     of any table governed by t11ZsServerDatabaseStorageType has an
> > >     object that is writable, then so too must be the corresponding
> > >     instance of this object.
> > >
> > > OK?
> >
> > Not sure I underatand, so you say this one only needs to be writable
> > if any other wrietable object is writable?
> > I am confused?
>
> Doubtful -- it's probably that I've interpreted your comment wrongly.
> Here's the conclusion that I "jumped" to:
>
>   RFC 2579 says (for StorageType):
>
>             Every usage of this textual convention is required to
>             specify the columnar objects which a permanent(4) row must
>             at a minimum allow to be writable."
>
>   but t11ZsServerDatabaseStorageType is aleady defined in RFC 4936 and
>   we aren't modifying RFC 4936, and so you want the specification of
>   "must at a minimum allow to be writable" to be updated in the
>   DESCRIPTION of t11FcSpZoneSetHashStatus.
>
>   Now, one instance of t11ZsServerDatabaseStorageType covers all the
>   associated rows of many tables, including rows in this new table
>   which AUGMENTS t11ZsServerEntry.  If t11ZsServerDatabaseStorageType
>   is 'permanent', then some of the instances in the identified set of
>   rows might be writeable -- if any are, then the Hash value is likely
>   to change when such modifying such instances, and so the
>   corresponding instance of t11FcSpZoneSetHashStatus needs to be
>   writable.  In contrast, if none of the instances of objects in the
>   identified set of rows are writable, then that instance of
>   t11FcSpZoneSetHashStatus doesn't need to be writable either.
>
> Is that what you meant ??  If so, did I capture it in my proposed
> addition to t11FcSpZoneSetHashStatus ?
>
> Keith.
>



_______________________________________________
imss mailing list
imss@ietf.org
https://www1.ietf.org/mailman/listinfo/imss