From imss-bounces@ietf.org Mon Sep 04 03:25:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GK8pB-0007ID-O5; Mon, 04 Sep 2006 03:24:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GK8pA-0007DU-Fs
	for imss@ietf.org; Mon, 04 Sep 2006 03:24:52 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GK8p8-0003ev-5J
	for imss@ietf.org; Mon, 04 Sep 2006 03:24:52 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k847OgSJ022958
	for <imss@ietf.org>; Mon, 4 Sep 2006 02:24:43 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK8B8P>; Mon, 4 Sep 2006 09:24:41 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550A9D3D3B@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: imss@ietf.org
Subject: RE: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
	vr, and Zone Svr MIBs
Date: Mon, 4 Sep 2006 09:24:41 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
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

Here are the SMICng results:

  C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-CONFIG-SERVER-MIB.inc
  W: f(T11-FC-FABRIC-CONFIG-SERVER-MIB.mi2), (716,15) Row 
  "t11FcsPortListEntry" does not have a consistent indexing scheme
  - index items from current table must come after index items from
  other tables

  *** 0 errors and 1 warning in parsing

  C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-LOCK-MIB.inc
  Successful parsing

  C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
  E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between sequence items

  *** 1 error and 0 warnings in parsing

  C:\bwijnen\smicng\work>smicng T11-FC-ZONE-SERVER-MIB.inc
  W: f(T11-FC-ZONE-SERVER-MIB.mi2), (959,15) Row "t11ZsSetZoneEntry"
  does not have a consistent indexing scheme - cannot specify an index
  item from additional "base row" t11ZsSetEntry, since can have only one
  "base row" which is t11ZsZoneEntry

  *** 0 errors and 1 warning in parsing

The two warnings for inconistent indexing are possibly OK if what we did
is indeed intended.

The missing comma should be fixed. It is in this table:
T11FcRscnStatsEntry ::= SEQUENCE {
    t11FcRscnInScrs                    Counter32,
    t11FcRscnInRscns                   Counter32,
    t11FcRscnOutRscns                  Counter32,
    t11FcRscnInSwRscns                 Counter32,
    t11FcRscnOutSwRscns                Counter32,
    t11FcRscnScrRejects                Counter32,
    t11FcRscnRscnRejects               Counter32,
    t11FcRscnSwRscnRejects             Counter32
    t11FcRscnInUnspecifiedRscns        Counter32,
    t11FcRscnOutUnspecifiedRscns       Counter32,
    t11FcRscnInChangedAttribRscns      Counter32,
    t11FcRscnOutChangedAttribRscns     Counter32,
    t11FcRscnInChangedServiceRscns     Counter32,
    t11FcRscnOutChangedServiceRscns    Counter32,
    t11FcRscnInChangedSwitchRscns      Counter32,
    t11FcRscnOutChangedSwitchRscns     Counter32,
    t11FcRscnInRemovedRscns            Counter32,
    t11FcRscnOutRemovedRscns           Counter32
}

Bert

> -----Original Message-----
> From: Black_David@emc.com [mailto:Black_David@emc.com]
> Sent: Saturday, August 26, 2006 02:26
> To: imss@ietf.org
> Cc: dromasca@avaya.com; Black_David@emc.com
> Subject: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config
> Svr, and Zone Svr MIBs
> 
> 
> This is to announce an imss WG Last Call on the following
> three MIB drafts:
> 
>      Fibre Channel Registered State Change Notification (RSCN) MIB
>                    draft-ietf-imss-fc-rscn-mib-00.txt
> 
>              Fibre-Channel Fabric Configuration Server MIB
>                    draft-ietf-imss-fc-fcs-mib-00.txt
> 
>                      Fibre-Channel Zone Server MIB
>                     draft-ietf-imss-fc-zs-mib-00.txt
>  
> This WG Last Call will run through 12 midnight Eastern Time on
> Sunday, September 17, 2006 (your WG chair hopes to deal with
> Last Call results during the week of September 18th).
> 
> Technical comments *must* be sent to the imss mailing list.
> Editorial comments may be sent directly to the draft editor
> (but please cc: me) - all three drafts have the same editor:
> 
> 		Keith McCloghrie [kzm@cisco.com]
> 
> Thanks,
> --David (imss WG chair)
> ----------------------------------------------------
> David L. Black, Senior Technologist
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> black_david@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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



From imss-bounces@ietf.org Mon Sep 04 05:48:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKB4L-00076g-IS; Mon, 04 Sep 2006 05:48:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKB4K-00076V-E1
	for imss@ietf.org; Mon, 04 Sep 2006 05:48:40 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKB4I-0007ss-63
	for imss@ietf.org; Mon, 04 Sep 2006 05:48:40 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k849mWwU029796
	for <imss@ietf.org>; Mon, 4 Sep 2006 04:48:33 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK81ZQ>; Mon, 4 Sep 2006 11:48:32 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA9650E@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: imss@ietf.org
Subject: RE: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
	vr, and Zone Svr MIBs
Date: Mon, 4 Sep 2006 11:48:31 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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

SMIlint tells me the following:

  C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-ZONE-SERVER-MIB
  ./T11-FC-ZONE-SERVER-MIB:117: [5] {type-without-format} warning:
   type `T11ZsZoneMemberType' has no format specification

It is just a warning. Yet we may want to add a DISPLAY-HINT.

  C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-RSCN-MIB

  C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-FABRIC-LOCK-MIB

  C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-FABRIC-CONFIG-SERVER-MIB
  ./T11-FC-FABRIC-CONFIG-SERVER-MIB:706: [5] {index-element-not-accessible}
  warning: exactly one index element of row `t11FcsPortListEntry' 
  must be accessible

I think this is fine. It is telling us that an INDEX object is accesible
(normally it should not be accessible), but it explains us why this is OK.

  ./T11-FC-FABRIC-CONFIG-SERVER-MIB:75: [5] {type-without-format} warning:
  type `T11ListIndex' has no format specification
  ./T11-FC-FABRIC-CONFIG-SERVER-MIB:85: [5] {type-without-format} warning:
  type `T11ListIndexPointer' has no format specification

It is just two warnings. Yet we may want to add a DISPLAY-HINT.

Bert

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



From imss-bounces@ietf.org Mon Sep 04 05:48:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKB4L-00076u-KQ; Mon, 04 Sep 2006 05:48:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKB4K-00076a-IU
	for imss@ietf.org; Mon, 04 Sep 2006 05:48:40 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKB4I-0007sr-63
	for imss@ietf.org; Mon, 04 Sep 2006 05:48:40 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k849mWKg029794
	for <imss@ietf.org>; Mon, 4 Sep 2006 04:48:33 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK81Z3>; Mon, 4 Sep 2006 11:48:32 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA9650F@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: imss@ietf.org
Subject: RE: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
	vr, and Zone Svr MIBs
Date: Mon, 4 Sep 2006 11:48:31 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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

SMIC strict checking reveals the following:

  C:\bwijnen\smicng\work>smicstrict

  C:\bwijnen\smicng\work>smicng T11-FC-ZONE-SERVER-MIB.inc
  W: f(T11-FC-ZONE-SERVER-MIB.mi2), (959,15) Row "t11ZsSetZoneEntry"
  does not have a consistent indexing scheme - cannot specify an
  index item from additional "base row" t11ZsSetEntry, since can
  have only one "base row" which is t11ZsZoneEntry

Keith, what is your comments on this one?

  W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2254,20) Variable "ifIndex"
  in notification "t11ZsMergeFailureNotify" is an index for a table
  W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2269,20) Variable "ifIndex" in
  notification "t11ZsMergeSuccessNotify" is an index for a table

I do not see the above two as fatal flaws. We could pass ifAlias,
or some other columnar-object of the ifTable I guess. That would make
the warning go away, and we would be sending extra information in
the notification.

  C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
  E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between sequence
  items

Just add the comma (as stated earlier).

  C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-LOCK-MIB.inc

is OK

  C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-CONFIG-SERVER-MIB.inc
  W: f(T11-FC-FABRIC-CONFIG-SERVER-MIB.mi2), (716,15) Row
  "t11FcsPortListEntry" does not have a consistent indexing scheme
  - index items from current table must come after index items from
  other tables

Keith, can you comment?

Bert

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



From imss-bounces@ietf.org Mon Sep 04 05:48:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKB4O-00077p-NB; Mon, 04 Sep 2006 05:48:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKB4O-00077k-CR
	for imss@ietf.org; Mon, 04 Sep 2006 05:48:44 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKB4I-0007sq-63
	for imss@ietf.org; Mon, 04 Sep 2006 05:48:44 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k849mWUI029795
	for <imss@ietf.org>; Mon, 4 Sep 2006 04:48:33 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK81ZP>; Mon, 4 Sep 2006 11:48:32 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96510@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: imss@ietf.org
Date: Mon, 4 Sep 2006 11:48:32 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Subject: [imss] WG last call: draft-ietf-imss-fc-rscn-mib-00.txt
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

None of the below are fatal issues in my view (except for the
missing comma, but that is easy to fix).

Some comments/questions:

- I see various objects like this one:

  t11FcRscnIlsRejectNotifyEnable OBJECT-TYPE
    SYNTAX       TruthValue
    MAX-ACCESS   read-write
    STATUS       current
    DESCRIPTION
           "This object specifies if a t11FcRscnIlsRejectReqNotify
           notification should be generated when this switch
           rejects an SW_RSCN on this fabric.

           Values written to this object should be retained
           over agent reboots."
    DEFVAL { false }
    ::= { t11FcRscnNotifyControlEntry 1 }

  Do we all think that "should be retained over agent reboots" is
  good (and deterministic) enough? It is a lowercase should, and so 
  any implementation that does not keep this over a reboot seems
  still compliant. In other words, I have no deterministic way
  at an NMS to figure out if this is persistent or not.

- I also see a number of times a REFERENCE aka:

    REFERENCE
           "ANSI INCITS xxx-200n, Fibre Channel - Link Services
           (FC-LS), Rev 1.2, June 2005, tables 38 & 43.

  which I supposed is referenced by:

   [FC-LS]
     "Fibre Channel - Link Services (FC-LS)", ANSI INCITS xxx-200n, Rev
     1.2, http://www.t11.org/t11/stat.nsf/upnum/1620-d, June 2005.

  do we habve any idea when the   xxx-200n can be filled out?
  it seems to me that this is a normative reference, no? 
  so we need a stable doc to look at I think.

- W.r.t. the notifications, I wonder if we (ever) run a risk that
  an agent would send so many a to cuase congestion.
  We do not seem to have a mechanism to control the amount of
  notifications that can be sent/generated per second/minute/xx
  Do we need one? If not, should we add some text to the DESCRIPTION
  clauses of the NOTIFICATIOn-TYPE definitions to explain why an
  agent would never generate more than x per second/minute/xxx?

- A real nit:
  In the security considerations section:
    Even if the network itself is secure (for example by using IPSec),
  s/IPSec/IPsec/.
  A while ago, this text was also in error in the security template
  on the ops.ietf.org website. That has been fixed now as well.

- Can the content of t11FcRscnRejectedRequestString have any specific 
  sensitive of secret content? If so, then maybe we should elaborate
  on that a bit in the security considerations. If not, then fine.

- For completenes, here is a SMICng error that I reported ealier

   C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
   E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between 
   sequence items> 
   *** 1 error and 0 warnings in parsing

  The missing comma should be fixed. It is in this table:
  T11FcRscnStatsEntry ::= SEQUENCE {
     t11FcRscnInScrs                    Counter32,
     t11FcRscnInRscns                   Counter32,
     t11FcRscnOutRscns                  Counter32,
     t11FcRscnInSwRscns                 Counter32,
     t11FcRscnOutSwRscns                Counter32,
     t11FcRscnScrRejects                Counter32,
     t11FcRscnRscnRejects               Counter32,
     t11FcRscnSwRscnRejects             Counter32
     t11FcRscnInUnspecifiedRscns        Counter32,
     t11FcRscnOutUnspecifiedRscns       Counter32,
     t11FcRscnInChangedAttribRscns      Counter32,
     t11FcRscnOutChangedAttribRscns     Counter32,
     t11FcRscnInChangedServiceRscns     Counter32,
     t11FcRscnOutChangedServiceRscns    Counter32,
     t11FcRscnInChangedSwitchRscns      Counter32,
     t11FcRscnOutChangedSwitchRscns     Counter32,
     t11FcRscnInRemovedRscns            Counter32,
     t11FcRscnOutRemovedRscns           Counter32
  }
 
Bert

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



From imss-bounces@ietf.org Mon Sep 04 06:13:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKBSf-0007ui-C2; Mon, 04 Sep 2006 06:13:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKBSd-0007uU-QM
	for imss@ietf.org; Mon, 04 Sep 2006 06:13:47 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GKBSc-0003M5-BK
	for imss@ietf.org; Mon, 04 Sep 2006 06:13:47 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 04 Sep 2006 03:13:46 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k84ADjal031292; Mon, 4 Sep 2006 03:13:45 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k84ADjYp008853;
	Mon, 4 Sep 2006 03:13:45 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id DAA06575;
	Mon, 4 Sep 2006 03:12:41 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609041012.DAA06575@cisco.com>
Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
To: bwijnen@lucent.com
Date: Mon, 4 Sep 2006 03:12:41 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 04, 2006 09:24:41 AM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=4706; t=1157364825; x=1158228825;
	c=relaxed/simple; s=sjdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20imss=20WG=20Last=20Call=3A=20Fibre=20Channel=20RSCN,
	=20 Fabric=20Config=20S;
	X=v=3Dcisco.com=3B=20h=3DlaAriIoH+ywm80asOo8mxlBfKuo=3D;
	b=J+LmgyMsoEAvMujJaFED5zSh9oo2RCrpAq7Rd2PodEMuKCx7exW4/7mGM+L8xuTySxFx3zU/
	jvSnSKgTX3X4dledWcEjT57MghRDfOf4ZBGHaoV7thEETij9EItgZkvR;
Authentication-Results: sj-dkim-1.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: imss@ietf.org
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

Hi Bert,

I've fixed the missing comma in my source file (but I'll defer submitting
an updated I-D until after all the Last Call comments are in).  The
INDEX issues are both situations where smilint doesn't find anything
wrong -- in both cases, the semantics of the INDEX clause are as
intended, and (I expect) the SMICng warning would go away if a new
auxiliary object were defined with identical semantics, rather than
re-using an object which is an auxiliary object in another table.  So,
they would (I think) be easy to fix if that's what you prefer.

Thanks,
Keith.
 
> Here are the SMICng results:
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-CONFIG-SERVER-MIB.inc
>   W: f(T11-FC-FABRIC-CONFIG-SERVER-MIB.mi2), (716,15) Row 
>   "t11FcsPortListEntry" does not have a consistent indexing scheme
>   - index items from current table must come after index items from
>   other tables
> 
>   *** 0 errors and 1 warning in parsing
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-LOCK-MIB.inc
>   Successful parsing
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
>   E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between sequence items
> 
>   *** 1 error and 0 warnings in parsing
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-ZONE-SERVER-MIB.inc
>   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (959,15) Row "t11ZsSetZoneEntry"
>   does not have a consistent indexing scheme - cannot specify an index
>   item from additional "base row" t11ZsSetEntry, since can have only one
>   "base row" which is t11ZsZoneEntry
> 
>   *** 0 errors and 1 warning in parsing
> 
> The two warnings for inconistent indexing are possibly OK if what we did
> is indeed intended.
> 
> The missing comma should be fixed. It is in this table:
> T11FcRscnStatsEntry ::= SEQUENCE {
>     t11FcRscnInScrs                    Counter32,
>     t11FcRscnInRscns                   Counter32,
>     t11FcRscnOutRscns                  Counter32,
>     t11FcRscnInSwRscns                 Counter32,
>     t11FcRscnOutSwRscns                Counter32,
>     t11FcRscnScrRejects                Counter32,
>     t11FcRscnRscnRejects               Counter32,
>     t11FcRscnSwRscnRejects             Counter32
>     t11FcRscnInUnspecifiedRscns        Counter32,
>     t11FcRscnOutUnspecifiedRscns       Counter32,
>     t11FcRscnInChangedAttribRscns      Counter32,
>     t11FcRscnOutChangedAttribRscns     Counter32,
>     t11FcRscnInChangedServiceRscns     Counter32,
>     t11FcRscnOutChangedServiceRscns    Counter32,
>     t11FcRscnInChangedSwitchRscns      Counter32,
>     t11FcRscnOutChangedSwitchRscns     Counter32,
>     t11FcRscnInRemovedRscns            Counter32,
>     t11FcRscnOutRemovedRscns           Counter32
> }
> 
> Bert
> 
> > -----Original Message-----
> > From: Black_David@emc.com [mailto:Black_David@emc.com]
> > Sent: Saturday, August 26, 2006 02:26
> > To: imss@ietf.org
> > Cc: dromasca@avaya.com; Black_David@emc.com
> > Subject: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config
> > Svr, and Zone Svr MIBs
> > 
> > 
> > This is to announce an imss WG Last Call on the following
> > three MIB drafts:
> > 
> >      Fibre Channel Registered State Change Notification (RSCN) MIB
> >                    draft-ietf-imss-fc-rscn-mib-00.txt
> > 
> >              Fibre-Channel Fabric Configuration Server MIB
> >                    draft-ietf-imss-fc-fcs-mib-00.txt
> > 
> >                      Fibre-Channel Zone Server MIB
> >                     draft-ietf-imss-fc-zs-mib-00.txt
> >  
> > This WG Last Call will run through 12 midnight Eastern Time on
> > Sunday, September 17, 2006 (your WG chair hopes to deal with
> > Last Call results during the week of September 18th).
> > 
> > Technical comments *must* be sent to the imss mailing list.
> > Editorial comments may be sent directly to the draft editor
> > (but please cc: me) - all three drafts have the same editor:
> > 
> > 		Keith McCloghrie [kzm@cisco.com]
> > 
> > Thanks,
> > --David (imss WG chair)
> > ----------------------------------------------------
> > David L. Black, Senior Technologist
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > black_david@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> > 
> > _______________________________________________
> > imss mailing list
> > imss@ietf.org
> > https://www1.ietf.org/mailman/listinfo/imss
> > 
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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



From imss-bounces@ietf.org Mon Sep 04 06:53:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKC5F-0003KJ-8j; Mon, 04 Sep 2006 06:53:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKC5D-0003Jm-SO
	for imss@ietf.org; Mon, 04 Sep 2006 06:53:39 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GKC5C-0003xk-HN
	for imss@ietf.org; Mon, 04 Sep 2006 06:53:39 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 04 Sep 2006 03:53:38 -0700
X-IronPort-AV: i="4.08,208,1154934000"; 
	d="scan'208"; a="442334778:sNHT31903142"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k84ArbEA028755; Mon, 4 Sep 2006 03:53:37 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k84ArbQV028954;
	Mon, 4 Sep 2006 03:53:37 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id DAA09039;
	Mon, 4 Sep 2006 03:52:33 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609041052.DAA09039@cisco.com>
Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
To: bwijnen@lucent.com
Date: Mon, 4 Sep 2006 03:52:33 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 04, 2006 11:48:31 AM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=2516; t=1157367217; x=1158231217;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20imss=20WG=20Last=20Call=3A=20Fibre=20Channel=20RSCN,
	=20 Fabric=20Config=20S;
	X=v=3Dcisco.com=3B=20h=3DlaAriIoH+ywm80asOo8mxlBfKuo=3D;
	b=q96pRAzUVvQhIxgXF4m9dPUB/hD7H9EGFfuMG6/qIttTYKR5LXYt/W7Z5DW+zS0qffT3gCsr
	ezKmh/3U3i/oJTTbUuG7f0Aq38UB40JVtB3YieIB6koJJ7s9DBgbnNVA;
Authentication-Results: sj-dkim-3.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: imss@ietf.org
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

See my earlier response for most of the issues.

The one new issue is the use of ifIndex in a notification's OBJECTS
clause.  This is another case where SMIC is providing an individual's
personal interpretation of the SMI, rather than being based on what
the SMI actually says, which is (from section 8.1 of RFC 2578):
								An
   object type specified in this clause must not have an MAX-ACCESS
   clause of "not-accessible".

whereas ifIndex has always had a MAX-ACCESS clause of "read-only".  

Note also the linkUp and linkDown notiifcations also have ifIndex in
their OBJECTS clause.  My experience is that customers prefer the use
of auxiliary objects in notifications, and so, in places where the SMI
allows it, I define them so intentionally.

Keith.


> SMIC strict checking reveals the following:
> 
>   C:\bwijnen\smicng\work>smicstrict
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-ZONE-SERVER-MIB.inc
>   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (959,15) Row "t11ZsSetZoneEntry"
>   does not have a consistent indexing scheme - cannot specify an
>   index item from additional "base row" t11ZsSetEntry, since can
>   have only one "base row" which is t11ZsZoneEntry
> 
> Keith, what is your comments on this one?
>
>   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2254,20) Variable "ifIndex"
>   in notification "t11ZsMergeFailureNotify" is an index for a table
>   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2269,20) Variable "ifIndex" in
>   notification "t11ZsMergeSuccessNotify" is an index for a table
> 
> I do not see the above two as fatal flaws. We could pass ifAlias,
> or some other columnar-object of the ifTable I guess. That would make
> the warning go away, and we would be sending extra information in
> the notification.
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
>   E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between sequence
>   items
> 
> Just add the comma (as stated earlier).
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-LOCK-MIB.inc
> 
> is OK
> 
>   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-CONFIG-SERVER-MIB.inc
>   W: f(T11-FC-FABRIC-CONFIG-SERVER-MIB.mi2), (716,15) Row
>   "t11FcsPortListEntry" does not have a consistent indexing scheme
>   - index items from current table must come after index items from
>   other tables
> 
> Keith, can you comment?
> 
> Bert
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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



From imss-bounces@ietf.org Mon Sep 04 06:58:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKC9x-0007No-TT; Mon, 04 Sep 2006 06:58:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKC9w-0007Nb-GQ
	for imss@ietf.org; Mon, 04 Sep 2006 06:58:32 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKC9v-0004z5-4d
	for imss@ietf.org; Mon, 04 Sep 2006 06:58:32 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k84AwRQq022107;
	Mon, 4 Sep 2006 05:58:27 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK8GGJ>; Mon, 4 Sep 2006 12:58:26 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA9654C@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>
Subject: RE: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
Date: Mon, 4 Sep 2006 12:58:26 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: imss@ietf.org
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

Inline

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Monday, September 04, 2006 12:13
> To: bwijnen@lucent.com
> Cc: imss@ietf.org
> Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, 
> Fabric Config
> S
> 
> 
> Hi Bert,
> 
> I've fixed the missing comma in my source file (but I'll defer submitting
> an updated I-D until after all the Last Call comments are in).

Yep, understood.
And I am doing more review. the initial message was just SMICng results.

> The
> INDEX issues are both situations where smilint doesn't find anything
> wrong -- in both cases, the semantics of the INDEX clause are as
> intended, and (I expect) the SMICng warning would go away if a new
> auxiliary object were defined with identical semantics, rather than
> re-using an object which is an auxiliary object in another table.  So,
> they would (I think) be easy to fix if that's what you prefer.
> 

AS long as we know that this is how we want to do the INDEXing and
understand why the SMICng warns us, then I am fine. No need to "fix"
if for me. Others may think different, if so, they better speak up.

Bert
> Thanks,
> Keith.
>  
> > Here are the SMICng results:
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-CONFIG-SERVER-MIB.inc
> >   W: f(T11-FC-FABRIC-CONFIG-SERVER-MIB.mi2), (716,15) Row 
> >   "t11FcsPortListEntry" does not have a consistent indexing scheme
> >   - index items from current table must come after index items from
> >   other tables
> > 
> >   *** 0 errors and 1 warning in parsing
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-LOCK-MIB.inc
> >   Successful parsing
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
> >   E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between 
> sequence items
> > 
> >   *** 1 error and 0 warnings in parsing
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-ZONE-SERVER-MIB.inc
> >   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (959,15) Row "t11ZsSetZoneEntry"
> >   does not have a consistent indexing scheme - cannot 
> specify an index
> >   item from additional "base row" t11ZsSetEntry, since can 
> have only one
> >   "base row" which is t11ZsZoneEntry
> > 
> >   *** 0 errors and 1 warning in parsing
> > 
> > The two warnings for inconistent indexing are possibly OK 
> if what we did
> > is indeed intended.
> > 
> > The missing comma should be fixed. It is in this table:
> > T11FcRscnStatsEntry ::= SEQUENCE {
> >     t11FcRscnInScrs                    Counter32,
> >     t11FcRscnInRscns                   Counter32,
> >     t11FcRscnOutRscns                  Counter32,
> >     t11FcRscnInSwRscns                 Counter32,
> >     t11FcRscnOutSwRscns                Counter32,
> >     t11FcRscnScrRejects                Counter32,
> >     t11FcRscnRscnRejects               Counter32,
> >     t11FcRscnSwRscnRejects             Counter32
> >     t11FcRscnInUnspecifiedRscns        Counter32,
> >     t11FcRscnOutUnspecifiedRscns       Counter32,
> >     t11FcRscnInChangedAttribRscns      Counter32,
> >     t11FcRscnOutChangedAttribRscns     Counter32,
> >     t11FcRscnInChangedServiceRscns     Counter32,
> >     t11FcRscnOutChangedServiceRscns    Counter32,
> >     t11FcRscnInChangedSwitchRscns      Counter32,
> >     t11FcRscnOutChangedSwitchRscns     Counter32,
> >     t11FcRscnInRemovedRscns            Counter32,
> >     t11FcRscnOutRemovedRscns           Counter32
> > }
> > 
> > Bert
> > 
> > > -----Original Message-----
> > > From: Black_David@emc.com [mailto:Black_David@emc.com]
> > > Sent: Saturday, August 26, 2006 02:26
> > > To: imss@ietf.org
> > > Cc: dromasca@avaya.com; Black_David@emc.com
> > > Subject: [imss] imss WG Last Call: Fibre Channel RSCN, 
> Fabric Config
> > > Svr, and Zone Svr MIBs
> > > 
> > > 
> > > This is to announce an imss WG Last Call on the following
> > > three MIB drafts:
> > > 
> > >      Fibre Channel Registered State Change Notification (RSCN) MIB
> > >                    draft-ietf-imss-fc-rscn-mib-00.txt
> > > 
> > >              Fibre-Channel Fabric Configuration Server MIB
> > >                    draft-ietf-imss-fc-fcs-mib-00.txt
> > > 
> > >                      Fibre-Channel Zone Server MIB
> > >                     draft-ietf-imss-fc-zs-mib-00.txt
> > >  
> > > This WG Last Call will run through 12 midnight Eastern Time on
> > > Sunday, September 17, 2006 (your WG chair hopes to deal with
> > > Last Call results during the week of September 18th).
> > > 
> > > Technical comments *must* be sent to the imss mailing list.
> > > Editorial comments may be sent directly to the draft editor
> > > (but please cc: me) - all three drafts have the same editor:
> > > 
> > > 		Keith McCloghrie [kzm@cisco.com]
> > > 
> > > Thanks,
> > > --David (imss WG chair)
> > > ----------------------------------------------------
> > > David L. Black, Senior Technologist
> > > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > > black_david@emc.com        Mobile: +1 (978) 394-7754
> > > ----------------------------------------------------
> > > 
> > > _______________________________________________
> > > imss mailing list
> > > imss@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/imss
> > > 
> > 
> > _______________________________________________
> > imss mailing list
> > imss@ietf.org
> > https://www1.ietf.org/mailman/listinfo/imss
> > 
> 

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



From imss-bounces@ietf.org Mon Sep 04 06:58:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKC9z-0007O0-0z; Mon, 04 Sep 2006 06:58:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKC9x-0007Nj-M5
	for imss@ietf.org; Mon, 04 Sep 2006 06:58:33 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKC9w-0004z9-Ae
	for imss@ietf.org; Mon, 04 Sep 2006 06:58:33 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 04 Sep 2006 03:58:30 -0700
X-IronPort-AV: i="4.08,208,1154934000"; 
	d="scan'208"; a="317393123:sNHT30818880"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k84AwTe3027933; Mon, 4 Sep 2006 03:58:29 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k84AwTw7000362;
	Mon, 4 Sep 2006 03:58:29 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id DAA10982;
	Mon, 4 Sep 2006 03:57:25 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609041057.DAA10982@cisco.com>
Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
To: bwijnen@lucent.com
Date: Mon, 4 Sep 2006 03:57:25 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 04, 2006 11:48:31 AM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1497; t=1157367509; x=1158231509;
	c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20imss=20WG=20Last=20Call=3A=20Fibre=20Channel=20RSCN,
	=20 Fabric=20Config=20S;
	X=v=3Dcisco.com=3B=20h=3DlaAriIoH+ywm80asOo8mxlBfKuo=3D;
	b=niL6DxkFDe3e7JW3KgoNJqsKjOxQ5Ly8Oo2+WjCXUt525CS7zyNoJTsYvxcNlDCSLbNPEQ4i
	nBHwur0sKfxTzQcozvqXn0UsgKRvGWd+qSwXRAhUss4LPBV8GJuHf//9;
Authentication-Results: sj-dkim-6.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: imss@ietf.org
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

RFC 2579 says:

   The DISPLAY-HINT clause, which need not be present, gives a hint ...

but I can add them if that is your wish.
 
Keith.


> SMIlint tells me the following:
> 
>   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-ZONE-SERVER-MIB
>   ./T11-FC-ZONE-SERVER-MIB:117: [5] {type-without-format} warning:
>    type `T11ZsZoneMemberType' has no format specification
> 
> It is just a warning. Yet we may want to add a DISPLAY-HINT.
> 
>   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-RSCN-MIB
> 
>   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-FABRIC-LOCK-MIB
> 
>   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-FABRIC-CONFIG-SERVER-MIB
>   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:706: [5] {index-element-not-accessible}
>   warning: exactly one index element of row `t11FcsPortListEntry' 
>   must be accessible
> 
> I think this is fine. It is telling us that an INDEX object is accesible
> (normally it should not be accessible), but it explains us why this is OK.
> 
>   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:75: [5] {type-without-format} warning:
>   type `T11ListIndex' has no format specification
>   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:85: [5] {type-without-format} warning:
>   type `T11ListIndexPointer' has no format specification
> 
> It is just two warnings. Yet we may want to add a DISPLAY-HINT.
> 
> Bert
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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



From imss-bounces@ietf.org Mon Sep 04 07:00:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKCC2-0007yf-HT; Mon, 04 Sep 2006 07:00:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKCC1-0007w2-Vs
	for imss@ietf.org; Mon, 04 Sep 2006 07:00:41 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKCC0-0005Hb-8N
	for imss@ietf.org; Mon, 04 Sep 2006 07:00:41 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k84B0coP024231;
	Mon, 4 Sep 2006 06:00:39 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK8GHT>; Mon, 4 Sep 2006 13:00:37 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA9654E@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>
Subject: RE: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
Date: Mon, 4 Sep 2006 13:00:37 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: imss@ietf.org
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

And I can live with your choice Keith.
So if no-one else speaks up, then you can keep it as is.

Bert

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Monday, September 04, 2006 12:53
> To: bwijnen@lucent.com
> Cc: imss@ietf.org
> Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, 
> Fabric Config
> S
> 
> 
> See my earlier response for most of the issues.
> 
> The one new issue is the use of ifIndex in a notification's OBJECTS
> clause.  This is another case where SMIC is providing an individual's
> personal interpretation of the SMI, rather than being based on what
> the SMI actually says, which is (from section 8.1 of RFC 2578):
> 								An
>    object type specified in this clause must not have an MAX-ACCESS
>    clause of "not-accessible".
> 
> whereas ifIndex has always had a MAX-ACCESS clause of "read-only".  
> 
> Note also the linkUp and linkDown notiifcations also have ifIndex in
> their OBJECTS clause.  My experience is that customers prefer the use
> of auxiliary objects in notifications, and so, in places where the SMI
> allows it, I define them so intentionally.
> 
> Keith.
> 
> 
> > SMIC strict checking reveals the following:
> > 
> >   C:\bwijnen\smicng\work>smicstrict
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-ZONE-SERVER-MIB.inc
> >   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (959,15) Row "t11ZsSetZoneEntry"
> >   does not have a consistent indexing scheme - cannot specify an
> >   index item from additional "base row" t11ZsSetEntry, since can
> >   have only one "base row" which is t11ZsZoneEntry
> > 
> > Keith, what is your comments on this one?
> >
> >   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2254,20) Variable "ifIndex"
> >   in notification "t11ZsMergeFailureNotify" is an index for a table
> >   W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2269,20) Variable "ifIndex" in
> >   notification "t11ZsMergeSuccessNotify" is an index for a table
> > 
> > I do not see the above two as fatal flaws. We could pass ifAlias,
> > or some other columnar-object of the ifTable I guess. That 
> would make
> > the warning go away, and we would be sending extra information in
> > the notification.
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
> >   E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between sequence
> >   items
> > 
> > Just add the comma (as stated earlier).
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-LOCK-MIB.inc
> > 
> > is OK
> > 
> >   C:\bwijnen\smicng\work>smicng T11-FC-FABRIC-CONFIG-SERVER-MIB.inc
> >   W: f(T11-FC-FABRIC-CONFIG-SERVER-MIB.mi2), (716,15) Row
> >   "t11FcsPortListEntry" does not have a consistent indexing scheme
> >   - index items from current table must come after index items from
> >   other tables
> > 
> > Keith, can you comment?
> > 
> > Bert
> > 
> > _______________________________________________
> > imss mailing list
> > imss@ietf.org
> > https://www1.ietf.org/mailman/listinfo/imss
> > 
> 

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



From imss-bounces@ietf.org Mon Sep 04 07:02:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKCDl-000096-El; Mon, 04 Sep 2006 07:02:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKCDk-00004w-2N
	for imss@ietf.org; Mon, 04 Sep 2006 07:02:28 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKCDi-0005XQ-OJ
	for imss@ietf.org; Mon, 04 Sep 2006 07:02:28 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k84B2O31026190;
	Mon, 4 Sep 2006 06:02:25 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK8GJM>; Mon, 4 Sep 2006 13:02:23 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96551@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>
Subject: RE: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
Date: Mon, 4 Sep 2006 13:02:24 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: imss@ietf.org
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

As I said "it is just a warning".
I think it would not hurt to add a DISPLAY-HINT.
But if that is the only reason to respin the draft, 
then I can also live with not adding it.

Bert

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Monday, September 04, 2006 12:57
> To: bwijnen@lucent.com
> Cc: imss@ietf.org
> Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, 
> Fabric Config
> S
> 
> 
> RFC 2579 says:
> 
>    The DISPLAY-HINT clause, which need not be present, gives 
> a hint ...
> 
> but I can add them if that is your wish.
>  
> Keith.
> 
> 
> > SMIlint tells me the following:
> > 
> >   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-ZONE-SERVER-MIB
> >   ./T11-FC-ZONE-SERVER-MIB:117: [5] {type-without-format} warning:
> >    type `T11ZsZoneMemberType' has no format specification
> > 
> > It is just a warning. Yet we may want to add a DISPLAY-HINT.
> > 
> >   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-RSCN-MIB
> > 
> >   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-FABRIC-LOCK-MIB
> > 
> >   C:\smi\mibs\work>smilint -m -s -l 6 
> ./T11-FC-FABRIC-CONFIG-SERVER-MIB
> >   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:706: [5] 
> {index-element-not-accessible}
> >   warning: exactly one index element of row `t11FcsPortListEntry' 
> >   must be accessible
> > 
> > I think this is fine. It is telling us that an INDEX object 
> is accesible
> > (normally it should not be accessible), but it explains us 
> why this is OK.
> > 
> >   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:75: [5] 
> {type-without-format} warning:
> >   type `T11ListIndex' has no format specification
> >   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:85: [5] 
> {type-without-format} warning:
> >   type `T11ListIndexPointer' has no format specification
> > 
> > It is just two warnings. Yet we may want to add a DISPLAY-HINT.
> > 
> > Bert
> > 
> > _______________________________________________
> > imss mailing list
> > imss@ietf.org
> > https://www1.ietf.org/mailman/listinfo/imss
> > 
> 

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



From imss-bounces@ietf.org Mon Sep 04 07:55:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKD2o-0005LC-NO; Mon, 04 Sep 2006 07:55:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKD2o-0005Hs-66
	for imss@ietf.org; Mon, 04 Sep 2006 07:55:14 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKD2j-0005GM-Jd
	for imss@ietf.org; Mon, 04 Sep 2006 07:55:14 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 04 Sep 2006 04:55:09 -0700
X-IronPort-AV: i="4.08,208,1154934000"; 
	d="scan'208"; a="317400831:sNHT34456200"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k84Bt8Dt004198; Mon, 4 Sep 2006 04:55:08 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k84Bt86W014959;
	Mon, 4 Sep 2006 04:55:08 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id EAA18648;
	Mon, 4 Sep 2006 04:54:04 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609041154.EAA18648@cisco.com>
Subject: Re: [imss] WG last call: draft-ietf-imss-fc-rscn-mib-00.txt
To: bwijnen@lucent.com
Date: Mon, 4 Sep 2006 04:54:04 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 04, 2006 11:48:32 AM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=5631; t=1157370908; x=1158234908;
	c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20WG=20last=20call=3A=20draft-ietf-imss-fc-rscn-mib-00.tx
	t; X=v=3Dcisco.com=3B=20h=3Df0WAuFGdwYTdyET0uT2QG1/mTqc=3D;
	b=h2VqP7JEi0chd6cIwaWpkUFVEFBBerWOF7/L0EFQvjLuZNiP+vHj+AJa+8UPgzMOVsb7CX9Z
	KBUt25XRVMpYE9KSCfFKHtOtjHrok/lLAVct9CcA29HGRUyCkGaNTHCD;
Authentication-Results: sj-dkim-5.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: imss@ietf.org
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

> None of the below are fatal issues in my view (except for the
> missing comma, but that is easy to fix).
> 
> Some comments/questions:
> 
> - I see various objects like this one:
> 
>   t11FcRscnIlsRejectNotifyEnable OBJECT-TYPE
>     SYNTAX       TruthValue
>     MAX-ACCESS   read-write
>     STATUS       current
>     DESCRIPTION
>            "This object specifies if a t11FcRscnIlsRejectReqNotify
>            notification should be generated when this switch
>            rejects an SW_RSCN on this fabric.
> 
>            Values written to this object should be retained
>            over agent reboots."
>     DEFVAL { false }
>     ::= { t11FcRscnNotifyControlEntry 1 }
> 
>   Do we all think that "should be retained over agent reboots" is
>   good (and deterministic) enough? It is a lowercase should, and so 
>   any implementation that does not keep this over a reboot seems
>   still compliant. In other words, I have no deterministic way
>   at an NMS to figure out if this is persistent or not.
 
Some systems store this type of information in an ASCII-formatted
"configuration file" which they keep in non-volatile memory, but also
have the capability for the file to be reloaded at boot time.  One of
the reasons why such configuration files have typically (until recently)
been formatted in ASCII is so that they can be edited by an administrator
to change the parameters prior to the device dowloading it (but
presumably, the same can now be done with XML-formatted files and
XML-based editors.)  In such a situation, you are correct that there is
no deterministic way for the agent to tell an NMS whether the parameter
was persistent.

> - I also see a number of times a REFERENCE aka:
> 
>     REFERENCE
>            "ANSI INCITS xxx-200n, Fibre Channel - Link Services
>            (FC-LS), Rev 1.2, June 2005, tables 38 & 43.
> 
>   which I supposed is referenced by:
> 
>    [FC-LS]
>      "Fibre Channel - Link Services (FC-LS)", ANSI INCITS xxx-200n, Rev
>      1.2, http://www.t11.org/t11/stat.nsf/upnum/1620-d, June 2005.
> 
>   do we habve any idea when the   xxx-200n can be filled out?
>   it seems to me that this is a normative reference, no? 
>   so we need a stable doc to look at I think.
 
I'll let Claudio and David speak to this.

> - W.r.t. the notifications, I wonder if we (ever) run a risk that
>   an agent would send so many a to cuase congestion.
>   We do not seem to have a mechanism to control the amount of
>   notifications that can be sent/generated per second/minute/xx
>   Do we need one? If not, should we add some text to the DESCRIPTION
>   clauses of the NOTIFICATIOn-TYPE definitions to explain why an
>   agent would never generate more than x per second/minute/xxx?
 
It is hard to quantify them as "x per second/minute/xxx" but at most,
they would have a similar frequency to linkUp/linkDown.  Nevertheless,
one mechanism was added to reduce the number of notifications in a
specific situation; in particular, the t11ZsFabricIndex object was
defined with the additional value of 4096, such that it could be
included in this t11ZsMergeFailureNotify as described in the
notification's DESCRIPTION:

           If multiple Virtual Fabrics are configured on an
           interface, and all have a Zone merge failure
           at the same time, then just one notification is
           generated and t11ZsFabricIndex has the value 4096."

> - A real nit:
>   In the security considerations section:
>     Even if the network itself is secure (for example by using IPSec),
>   s/IPSec/IPsec/.
>   A while ago, this text was also in error in the security template
>   on the ops.ietf.org website. That has been fixed now as well.
 
Now fixed in the source of all three drafts.

> - Can the content of t11FcRscnRejectedRequestString have any specific 
>   sensitive of secret content? If so, then maybe we should elaborate
>   on that a bit in the security considerations. If not, then fine.
 
It's a list of port numbers of affected ports and/or an error code, and
in some cases the name and state of such ports.  So, no, I don't think
it has any specific secret content.

> - For completenes, here is a SMICng error that I reported ealier
> 
>    C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
>    E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between 
>    sequence items> 
>    *** 1 error and 0 warnings in parsing
> 
>   The missing comma should be fixed. It is in this table:
>   T11FcRscnStatsEntry ::= SEQUENCE {
>      t11FcRscnInScrs                    Counter32,
>      t11FcRscnInRscns                   Counter32,
>      t11FcRscnOutRscns                  Counter32,
>      t11FcRscnInSwRscns                 Counter32,
>      t11FcRscnOutSwRscns                Counter32,
>      t11FcRscnScrRejects                Counter32,
>      t11FcRscnRscnRejects               Counter32,
>      t11FcRscnSwRscnRejects             Counter32
>      t11FcRscnInUnspecifiedRscns        Counter32,
>      t11FcRscnOutUnspecifiedRscns       Counter32,
>      t11FcRscnInChangedAttribRscns      Counter32,
>      t11FcRscnOutChangedAttribRscns     Counter32,
>      t11FcRscnInChangedServiceRscns     Counter32,
>      t11FcRscnOutChangedServiceRscns    Counter32,
>      t11FcRscnInChangedSwitchRscns      Counter32,
>      t11FcRscnOutChangedSwitchRscns     Counter32,
>      t11FcRscnInRemovedRscns            Counter32,
>      t11FcRscnOutRemovedRscns           Counter32
>   }
  
Right.  I've fixed this in my source.

Thanks,
Keith.

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



From imss-bounces@ietf.org Mon Sep 04 08:02:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKD9K-0002qS-KB; Mon, 04 Sep 2006 08:01:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKD9J-0002qM-Kf
	for imss@ietf.org; Mon, 04 Sep 2006 08:01:57 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKD9H-0005y8-97
	for imss@ietf.org; Mon, 04 Sep 2006 08:01:57 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-4.cisco.com with ESMTP; 04 Sep 2006 05:01:55 -0700
X-IronPort-AV: i="4.08,208,1154934000"; 
	d="scan'208"; a="1851837666:sNHT31709388"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-8.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k84C1sFt002253; Mon, 4 Sep 2006 05:01:54 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k84C1sw7015968;
	Mon, 4 Sep 2006 05:01:54 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id FAA19202;
	Mon, 4 Sep 2006 05:00:50 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609041200.FAA19202@cisco.com>
Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S
To: bwijnen@lucent.com
Date: Mon, 4 Sep 2006 05:00:50 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 04, 2006 01:02:24 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=2276; t=1157371314; x=1158235314;
	c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20imss=20WG=20Last=20Call=3A=20Fibre=20Channel=20RSCN,
	=20 Fabric=20Config=20S;
	X=v=3Dcisco.com=3B=20h=3DlaAriIoH+ywm80asOo8mxlBfKuo=3D;
	b=rVZtYrcDWbQzQwyBFRkng+fmIjUAiVmGsymskeOgrZ+9uxeahbSfl551VRfD+f927Beae2Au
	Hocz8pGwhyFPiisE7U4xoK/5eixsLrVjczTlZc50nw6L+Zyzcide1M8t;
Authentication-Results: sj-dkim-8.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: imss@ietf.org, Keith McCloghrie <kzm@cisco.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

Each one has to be re-spun, because they all have to have "IPSec"
changed to "IPsec" in the standard boilerplate :-).

Keith.
 
> As I said "it is just a warning".
> I think it would not hurt to add a DISPLAY-HINT.
> But if that is the only reason to respin the draft, 
> then I can also live with not adding it.
> 
> Bert
> 
> > -----Original Message-----
> > From: Keith McCloghrie [mailto:kzm@cisco.com]
> > Sent: Monday, September 04, 2006 12:57
> > To: bwijnen@lucent.com
> > Cc: imss@ietf.org
> > Subject: Re: [imss] imss WG Last Call: Fibre Channel RSCN, 
> > Fabric Config
> > S
> > 
> > 
> > RFC 2579 says:
> > 
> >    The DISPLAY-HINT clause, which need not be present, gives 
> > a hint ...
> > 
> > but I can add them if that is your wish.
> >  
> > Keith.
> > 
> > 
> > > SMIlint tells me the following:
> > > 
> > >   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-ZONE-SERVER-MIB
> > >   ./T11-FC-ZONE-SERVER-MIB:117: [5] {type-without-format} warning:
> > >    type `T11ZsZoneMemberType' has no format specification
> > > 
> > > It is just a warning. Yet we may want to add a DISPLAY-HINT.
> > > 
> > >   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-RSCN-MIB
> > > 
> > >   C:\smi\mibs\work>smilint -m -s -l 6 ./T11-FC-FABRIC-LOCK-MIB
> > > 
> > >   C:\smi\mibs\work>smilint -m -s -l 6 
> > ./T11-FC-FABRIC-CONFIG-SERVER-MIB
> > >   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:706: [5] 
> > {index-element-not-accessible}
> > >   warning: exactly one index element of row `t11FcsPortListEntry' 
> > >   must be accessible
> > > 
> > > I think this is fine. It is telling us that an INDEX object 
> > is accesible
> > > (normally it should not be accessible), but it explains us 
> > why this is OK.
> > > 
> > >   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:75: [5] 
> > {type-without-format} warning:
> > >   type `T11ListIndex' has no format specification
> > >   ./T11-FC-FABRIC-CONFIG-SERVER-MIB:85: [5] 
> > {type-without-format} warning:
> > >   type `T11ListIndexPointer' has no format specification
> > > 
> > > It is just two warnings. Yet we may want to add a DISPLAY-HINT.
> > > 
> > > Bert
> > > 
> > > _______________________________________________
> > > imss mailing list
> > > imss@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/imss
> > > 
> > 
> 

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



From imss-bounces@ietf.org Mon Sep 04 08:27:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKDY1-0003pe-1g; Mon, 04 Sep 2006 08:27:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKDXz-0003p9-Ly
	for imss@ietf.org; Mon, 04 Sep 2006 08:27:27 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKDXy-0001Yj-96
	for imss@ietf.org; Mon, 04 Sep 2006 08:27:27 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k84CRK8m005233;
	Mon, 4 Sep 2006 07:27:20 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK8HWN>; Mon, 4 Sep 2006 14:27:19 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA965A7@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>
Subject: RE: [imss] WG last call: draft-ietf-imss-fc-rscn-mib-00.txt
Date: Mon, 4 Sep 2006 14:27:19 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: imss@ietf.org
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

Inline

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Monday, September 04, 2006 13:54
> To: bwijnen@lucent.com
> Cc: imss@ietf.org
> Subject: Re: [imss] WG last call: draft-ietf-imss-fc-rscn-mib-00.txt
> 
> 
> > None of the below are fatal issues in my view (except for the
> > missing comma, but that is easy to fix).
> > 
> > Some comments/questions:
> > 
> > - I see various objects like this one:
> > 
> >   t11FcRscnIlsRejectNotifyEnable OBJECT-TYPE
> >     SYNTAX       TruthValue
> >     MAX-ACCESS   read-write
> >     STATUS       current
> >     DESCRIPTION
> >            "This object specifies if a t11FcRscnIlsRejectReqNotify
> >            notification should be generated when this switch
> >            rejects an SW_RSCN on this fabric.
> > 
> >            Values written to this object should be retained
> >            over agent reboots."
> >     DEFVAL { false }
> >     ::= { t11FcRscnNotifyControlEntry 1 }
> > 
> >   Do we all think that "should be retained over agent reboots" is
> >   good (and deterministic) enough? It is a lowercase should, and so 
> >   any implementation that does not keep this over a reboot seems
> >   still compliant. In other words, I have no deterministic way
> >   at an NMS to figure out if this is persistent or not.
>  
> Some systems store this type of information in an ASCII-formatted
> "configuration file" which they keep in non-volatile memory, but also
> have the capability for the file to be reloaded at boot time.  One of
> the reasons why such configuration files have typically (until recently)
> been formatted in ASCII is so that they can be edited by an administrator
> to change the parameters prior to the device dowloading it (but
> presumably, the same can now be done with XML-formatted files and
> XML-based editors.)  In such a situation, you are correct that there is
> no deterministic way for the agent to tell an NMS whether the 
> parameter was persistent.
> 

Mmm.. I had not even considered that. That is, that the "persistent info"
can manually (or possibly by some other means, like CLI, NETCONF,
what have you) be changed. I guess such is always the case, in that
if we declare (in a MIB module) that data MUST be persistent/nonVolatile,
that some admin can come in and whipe out (or change) the file 
(or nonVolatile memory) that contains the "persistent data" 
and it is gone. This is true for all MIB modules we have defined, 
even for those that have a StorageType object inclued in a row.

What I had in mind was, that an implementation can decide to NOT save any
data (that has been changed via an SNMP-SET) in non-volatile memory. 
The desription clause does leave that open to any implementer.

I know this same sort of discussion has happened in other WGs.
And I would rather see a "must" than a "should" in the text.
But I am not gonna loose sleep if you keep it as is.

> > - I also see a number of times a REFERENCE aka:
> > 
> >     REFERENCE
> >            "ANSI INCITS xxx-200n, Fibre Channel - Link Services
> >            (FC-LS), Rev 1.2, June 2005, tables 38 & 43.
> > 
> >   which I supposed is referenced by:
> > 
> >    [FC-LS]
> >      "Fibre Channel - Link Services (FC-LS)", ANSI INCITS 
> xxx-200n, Rev
> >      1.2, http://www.t11.org/t11/stat.nsf/upnum/1620-d, June 2005.
> > 
> >   do we habve any idea when the   xxx-200n can be filled out?
> >   it seems to me that this is a normative reference, no? 
> >   so we need a stable doc to look at I think.
>  
> I'll let Claudio and David speak to this.
> 

Would be good

> > - W.r.t. the notifications, I wonder if we (ever) run a risk that
> >   an agent would send so many a to cuase congestion.
> >   We do not seem to have a mechanism to control the amount of
> >   notifications that can be sent/generated per second/minute/xx
> >   Do we need one? If not, should we add some text to the DESCRIPTION
> >   clauses of the NOTIFICATIOn-TYPE definitions to explain why an
> >   agent would never generate more than x per second/minute/xxx?
>  
> It is hard to quantify them as "x per second/minute/xxx" but at most,
> they would have a similar frequency to linkUp/linkDown.  Nevertheless,
> one mechanism was added to reduce the number of notifications in a
> specific situation; in particular, the t11ZsFabricIndex object was
> defined with the additional value of 4096, such that it could be
> included in this t11ZsMergeFailureNotify as described in the
> notification's DESCRIPTION:
> 
>            If multiple Virtual Fabrics are configured on an
>            interface, and all have a Zone merge failure
>            at the same time, then just one notification is
>            generated and t11ZsFabricIndex has the value 4096."
> 

But if they have it all say a few milliseconds apart, then several
hundred could get generated in 1 second?

The Transport ADs always worry about these aspects of notifications,
so to defuse any concern (valid in my view) they may have, I suggest
we think of some words to address those concerns.

> > - A real nit:
> >   In the security considerations section:
> >     Even if the network itself is secure (for example by using IPSec),
> >   s/IPSec/IPsec/.
> >   A while ago, this text was also in error in the security template
> >   on the ops.ietf.org website. That has been fixed now as well.
>  
> Now fixed in the source of all three drafts.
> 

thanks ;-)

> > - Can the content of t11FcRscnRejectedRequestString have any specific 
> >   sensitive of secret content? If so, then maybe we should elaborate
> >   on that a bit in the security considerations. If not, then fine.
>  
> It's a list of port numbers of affected ports and/or an error code, and
> in some cases the name and state of such ports.  So, no, I don't think
> it has any specific secret content.
> 

OK. Might be good to state so in the DESCRIPTION clause of the object?
So that it is easier to see what sort of info is in there?
Up to you. I am happy to know that there is no special security concern.

> > - For completenes, here is a SMICng error that I reported ealier
> > 
> >    C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
> >    E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between 
> >    sequence items> 
> >    *** 1 error and 0 warnings in parsing
> > 
> >   The missing comma should be fixed. It is in this table:
> >   T11FcRscnStatsEntry ::= SEQUENCE {
> >      t11FcRscnInScrs                    Counter32,
> >      t11FcRscnInRscns                   Counter32,
> >      t11FcRscnOutRscns                  Counter32,
> >      t11FcRscnInSwRscns                 Counter32,
> >      t11FcRscnOutSwRscns                Counter32,
> >      t11FcRscnScrRejects                Counter32,
> >      t11FcRscnRscnRejects               Counter32,
> >      t11FcRscnSwRscnRejects             Counter32
> >      t11FcRscnInUnspecifiedRscns        Counter32,
> >      t11FcRscnOutUnspecifiedRscns       Counter32,
> >      t11FcRscnInChangedAttribRscns      Counter32,
> >      t11FcRscnOutChangedAttribRscns     Counter32,
> >      t11FcRscnInChangedServiceRscns     Counter32,
> >      t11FcRscnOutChangedServiceRscns    Counter32,
> >      t11FcRscnInChangedSwitchRscns      Counter32,
> >      t11FcRscnOutChangedSwitchRscns     Counter32,
> >      t11FcRscnInRemovedRscns            Counter32,
> >      t11FcRscnOutRemovedRscns           Counter32
> >   }
>   
> Right.  I've fixed this in my source.
> 
Ack

Bert
> Thanks,
> Keith.
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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



From imss-bounces@ietf.org Mon Sep 04 12:24:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKHEm-0007gy-RU; Mon, 04 Sep 2006 12:23:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKHEl-0007gs-HD
	for imss@ietf.org; Mon, 04 Sep 2006 12:23:51 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKHEh-00051u-RF
	for imss@ietf.org; Mon, 04 Sep 2006 12:23:51 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k84GNgPn018226
	for <imss@ietf.org>; Mon, 4 Sep 2006 11:23:43 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK8M3G>; Mon, 4 Sep 2006 18:23:41 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96625@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: imss@ietf.org
Date: Mon, 4 Sep 2006 18:23:41 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 439b8e44c906b144bce6744ebb966e60
Subject: [imss] WG Last Call: draft-ietf-imss-fc-fcs-mib-00.txt
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


Comments/questions:

- In the MODULE-IDENTITY, I see:

    REVISION  "200608140000Z"
    DESCRIPTION
            "Initial version of this MIB module."
    ::= { mib-2 nnn }                     -- to be determined later
  
  I think I would make that:

    REVISION  "200608140000Z"
    DESCRIPTION
            "Initial version of this MIB module, published as RFC yyyy."
    -- RFC-Editor, replace yyyy with actual RFC number & remove this note
    ::= { mib-2 nnn }  -- to be assigned by IANA.
    -- RFC Editor: replace nnn with IANA-assigned number & remove this note

- To avoid later comments, I would also add this to the DESCRIPTION
  clause of the MODULE-IDENTITY itself:

           Copyright (C) The Internet Society (2006).  This version of
           this MIB module is part of RFC yyyy;  see the RFC itself for
           full legal notices."

   -- RFC Editor: replace yyyy with actual RFC number & remove this note

- I wonder if we would not better rename these TCs (for naming consistency):

     FcIeType, FcPortState, FcPortTxType
 
  and name them instead as follows:

     T11FcIeType, T11FcPortState, T11FcPortTxType

  Or are these 3 TCs extending the set of FcXxxx TCs in RFC4044?
  If so, the I'd suggest to add at least a small SMI comment to state that,
  so that it is clear why the names are as chosen.

- For consistency, but also for betetr info in the DESCRIPTION clause,
  I would consider to change:

  FcPortTxType ::= TEXTUAL-CONVENTION
    STATUS  current
    DESCRIPTION
            "The technology of the port transceiver:

                unknown        - unknown (includes the 'null' type)
                other          - some other technology
                shortwave850nm - Short wave laser - SN (850 nm)
                longwave1550nm - Long wave laser - LL (1550 nm)
                longwave1310nm - Long wave laser cost
                                 reduced - LC (1310 nm)
                electrical     - Electrical - EL."

  into:

  FcPortTxType ::= TEXTUAL-CONVENTION
    STATUS  current
    DESCRIPTION
            "The technology of the port transceiver:

                unknown(1)        - unknown (includes the 'null' type)
                other(2)          - some other technology
                shortwave850nm(3) - Short wave laser - SN (850 nm)
                longwave1550nm(4) - Long wave laser - LL (1550 nm)
                longwave1310nm(5) - Long wave laser cost
                                    reduced - LC (1310 nm)
                electrical(6)     - Electrical - EL."

- I am a bit surprised by:

  T11ListIndexPointer ::= TEXTUAL-CONVENTION
    STATUS  current
    DESCRIPTION
            "Objects with this syntax point to a list of elements
            contained in a table, by holding the same value as the
            object with syntax T11ListIndex defined in the table's
            INDEX clause, or, zero to indicate an empty list.
            The definition of an object with this syntax must
            identify the table(s) into which it points."
    SYNTAX  Unsigned32 -- the default range of (0..4294967295)

  First, I would make it:  SYNTAX Unsigned32 (0..4294967295)
  instead of putting that in a SMI comment field.

  Second, I think we normally would use a name of 

    T11ListIndexOrZero ::= TEXTUAL-CONVENTION

  To complement the T11ListIndex TC, which does not include the zaero.

  Third, we also normally do not prescribe what a value of zero means,
  but we normally say something aka (this is from InetrfaceIndexOrZero):

            "This textual convention is an extension of the
            InterfaceIndex convention.  The latter defines a greater
            than zero value used to identify an interface or interface
            sub-layer in the managed system.  This extension permits the
            additional value of zero.  the value zero is object-specific
            and must therefore be defined as part of the description of
            any object which uses this syntax.  Examples of the usage of
            zero might include situations where interface was unknown,
            or when none or all interfaces need to be referenced."

  We in fact have quite a few of these XxxSomeIndex and XxxSomeIndexOrZero
  TCs, which all (i believe) follow/use that same concept. I would strongly
  suggest that we do so here as well.

  Mmmm... I see that for some other TCs in the FC/IMSS/IPS space you do
  not follow the InterfaceIndex/InetrfaceInexOrZero so closely either.
  Oh well... Up to you and the WG. I personally like the InterfaceIndeOrZero
  approach better. 

- I see REFERENCE clauses aka:

    REFERENCE
            "ANSI INCITS xxx-200x, Fibre Channel - Generic Services 5,
            FC-GS-5 T11/Project 1677-D/Rev 8, Table 124."

  which relates to this reference (I guess):

   [FC-GS-5]
     "Fibre Channel - Generic Services - 5 (FC-GS-5)", ANSI INCITS
     xxx-200x, T11/Project 1677-D/Rev 8.00
     http://www.t11.org/t11/stat.nsf/upnum/1677-d, September 2004.


  Do we know when we will get a stable reference?
  It is normative, so we may have to say something about that.

  I guess Keith already stated that David or Claudio should answer this 
  question.

- For t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh,
  is the value in these objects included in teh range? My read would
  say they are. But we may want to make that clear by stating it?

- For t11FcsFabricDiscoveryStart, how long does discovery take?
  The reason I ask, is that if it may take a while, that we might
  want to consider a value like "discoveryInProgress(3) ??
  Just thinking aloud, I can also live with what we have in there now.

- t11FcsFabricDiscoveryTable
  I guess that this table gets created/instantiated by the agent everytime
  it starts. There are no default values for the two objects 
  t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh.
  So how is the behavioud if I issue a DiscoveryStart when these objects
  have not been SET yet? Should we define DEFVALs?

- Given the DESCRIPTION clause of t11FcsFabricDiscoveryStart, I 
  suggest to add  DEFVAL { noOp }

- I suppose that SETTING t11FcsDiscoveryStatus to one of
                     inProgress(1),
                     completed(2),
  would have no effect? I.e. it would be ignored?
  Whatever the intended behaviour is to be, we probably do best to
  be specific as to what we want an agent to do.

  I personally kind of like to add something to the MODULE-COMPLIANCE<
  which states that the WRITE-SYNTAX is  localOnly(3) and that
  the SYNTAX is all 3 values. I think that expresses that only the
  one value that makes sense can be SET/written.

  I personally might do a similar thing for t11FcsFabricDiscoveryStart,
  but that one at least explains what to do if I set the value to
  something that does not trigger an action.

- t11FcsDiscoveryStatus has no persistency (or so is my reading of
  the DESCRIPTION clause) and will be set to localOnly upon a restart?
  If so, it might be usefull to add a sentence about that, just to be
  explicit and clear.

- For objects t11FcsIeName and t11FcsIeDomainId, I wonder if a zero
  (i.e. zero length OCTET STRING) are really valid. If not, then we
  should add a SIZE and RANGE restriction.

- This definition seems strange:

  t11FcsIeFabricName  OBJECT-TYPE
    SYNTAX       FcNameIdOrZero
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The Fabric_Name (WWN) of this Interconnect Element.
            When the Fabric_Name is unknown, this object contains
            the all-zeros value: x'00 00 00 00 00 00 00 00'."
    REFERENCE
            "ANSI INCITS xxx-200x, Fibre Channel - Generic Services 5,
            FC-GS-5 T11/Project 1677-D/Rev 8, section 6.2.3.2.5."
    DEFVAL { '0000000000000000'h }
    ::= { t11FcsIeEntry 5 }

  Because the SYNTAX used is a TC from RFC4044), that states:

   FcNameIdOrZero ::= TEXTUAL-CONVENTION
     STATUS current
     DESCRIPTION
             "The World Wide Name (WWN) associated with a Fibre Channel
             (FC) entity.  WWNs were initially defined as 64-bits in
             length.  The latest definition (for future use) is 128-bits
             long.  The zero-length string value is used in
             circumstances in which the WWN is unassigned/unknown."
    SYNTAX  OCTET STRING (SIZE(0 | 8 | 16))

  And so I would have expected that the t11FcsIeFabricName object would
  have been defined as:

  t11FcsIeFabricName  OBJECT-TYPE
    SYNTAX       FcNameIdOrZero
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The Fabric_Name (WWN) of this Interconnect Element."
    REFERENCE
            "ANSI INCITS xxx-200x, Fibre Channel - Generic Services 5,
            FC-GS-5 T11/Project 1677-D/Rev 8, section 6.2.3.2.5."
    DEFVAL { "" }
    ::= { t11FcsIeEntry 5 }

  I do see in sect "6.2.3.2.5 Interconnect Element Fabric Name" of
  http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf
    This standard does not define how this attribute is registered with
    the Fabric Configuration Server. The null value for the Interconnect
    Element Fabric Name attribute is 00 00 00 00 00 00 00 00h.

  So is the use of FcNameIdOrZero the proper syntax here??


- This is a real nit:
  t11FcsIeLogicalName  OBJECT-TYPE
    SYNTAX       OCTET STRING (SIZE (0..255))
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The logical name of this Interconnect Element.
            When the logical name is unknown, this object contains
            the zero-length string."

  I would use a SYNTAX as follows:
    SYNTAX       OCTET STRING (SIZE (0 | 1..255))
  To indicate that zero has a special meaning.
  Ignore my ranting if you think this is nonsense.

- I see this:

  t11FcsIeMgmtAddrListIndex  OBJECT-TYPE
    SYNTAX       T11ListIndexPointer
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The management address list for this Interconnect Element.
            This object points to an entry in the
            t11FcsMgmtAddrListTable."

  Reading the DESCRIPTIOn clause, I wonder why one would not use a 
  RowPointer. The fact is that the pointer does not point to "an entry"
  in the t11FcsMgmtAddrListTable, but to a SET of such entries.
  So I guess the DESCRIPTION clause could be clarified.

  This is true for more (may be all) cases where this TC T11ListIndexPointer
  is used.

- I see:
 
  t11FcsIeInfoList  OBJECT-TYPE
    SYNTAX       OCTET STRING (SIZE (0..252))
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The information list for this Interconnect Element.
            This object contains the following substrings in order:
            vendor name, model name/number and release code/level,
            followed by zero or more substrings of vendor-specific
            information. Each substring is terminated with a byte
            containing a null value (x'00')."

  And that reads as if it is ASCII information to be (potentially) 
  consumed by human beings.  So in that case, the IETF wants it to
  be an internationalized string.  Comment?

- I see:

  t11FcsMgmtAddr  OBJECT-TYPE
    SYNTAX       SnmpAdminString
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The management address of this entry.
            The format of this object may be based on the
            format of the Uniform Resource Locator (URL).
            For example, for SNMP, see RFC 4088."

  So it syas "the format MAY be based on..." (my emphasis on MAY).
  So, does that mean it may also be based on something else?
  How do I determine what the actual format is?

- SMICng gave a warning about the indexing of

  t11FcsPortListEntry  OBJECT-TYPE
    SYNTAX       T11FcsPortListEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION
            "An entry which identifies that the port which has the
            port name, t11FcsPortName, is in a particular list of
            ports, which is known to a switch (identified by
            fcmInstanceIndex and fcmSwitchIndex)."
    INDEX   { fcmInstanceIndex,  fcmSwitchIndex,
              t11FcsPortListIndex, t11FcsPortName }
    ::= { t11FcsPortListTable 1 }

  I read Keiths explanation, which seemed fine. But now that I am
  reviewing the MIB module in details and try to understand things,
  now I am no so sure this is goodness.

  So, that t11FcsPortname is a value (embedded in the index) that
  should help me find more detailed info, right?
  So how do I find that info? I tyhink I need to go to the
  t11FcsPortTable, which is indexed by:

    INDEX   { fcmInstanceIndex, fcmSwitchIndex,
              t11FcsFabricIndex, t11FcsPortName }

  So assuming that the index values for fcmInstanceIndex, fcmSwitchIndex,
  are the same in both tables, I can see that I can pick up 3 index
  values from the list of t11FcsPortsList in the t11FcsPortsListTable.
  But I am missing the 3rd index of the t11FcsPortnameTable, namely
  t11FcsFabricIndex. So how am I going to wuickly pick that up?
  Or how exactly are the tables connected/linked?

  Maybe I need to study it deeper... but I'd prefer an explanation of
  the people who created these tables with the current indexing schemes.

- for
 
  t11FcsPortName  OBJECT-TYPE
    SYNTAX       FcNameIdOrZero
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION
            "The Port_Name (WWN) of the port for which this row
            contains information."

  I wonder if a zero value (zero length OCTET STRING) is really valid?
  If not, then we may need to limit it with a SIZE paramter aka
    SYNTAX       FcNameIdOrZero SIZE (8 | 16)

  But,  I do see that in sect "6.2.3.3.1 Port Name" of document
  http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf, it says:

      The null value for the Port Name attribute is
      00 00 00 00 00 00 00 00h.

  So... is the SYNTAX of FcNameIdOrZero appropriate here? 
  In any event, the name SIZE seems to be fixed at 8 octets for the
  PortName, so at least one would then define the syntax as:

    SYNTAX       FcNameIdOrZero (SIZE (8))

- For:

  t11FcsPortModuleType  OBJECT-TYPE
    SYNTAX       Unsigned32 (0..255)
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION
            "The port module type of this port."
    REFERENCE
            "ANSI INCITS xxx-200x, Fibre Channel - Generic Services 5,
            FC-GS-5 T11/Project 1677-D/Rev 8, section 6.2.3.3.4."

  It seems better to create a TC that ENUMerates the valid values?

- For:

  t11FcsPortSpeedCapab  OBJECT-TYPE
    SYNTAX       OCTET STRING (SIZE (2))

  It seems that the references document and section say that it is a BITS
  construct ??

- Same for t11FcsPortOperSpeed

- For:

  t11FcsPlatformName  OBJECT-TYPE
    SYNTAX       OCTET STRING (SIZE (0..255))

  It seems to me that the SYNTAX better be:

    SYNTAX       OCTET STRING (SIZE (0 | 3..256))

  because http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf
  section 6.2.3.4.2 tells me:

    The Platform Name attribute may be registered using the
    protocol described in 6.2.2.3. The null value for the
    Platform Name attribute is a zero-length Platform Name.

  So maybe that is how we can get a length of zero. But I am
  not even sure about that. It is also possible that the
  first byte would be valued at zero. Is the format octet 
  included in this case? Not clear from the PDF file for me.

  If I understand the PDF file correctly, then (it speaks about
  reserved to be of length 254-m) then there are 2 octets (1 for
  length, one for format) plus 254 for the actual name. So that
  would be a max size of 256 in my view.

- Several objects in the t11FcsPlatformTable
  (like t11FcsPlatformVendorId, t11FcsPlatformProductId , etc)
  suggest (based on teh SYNTAX of SnmpAdminString) that the value
  can be an internationalized human readable string.
  But the table 121 in the PDF file, section 6.2.3.4.5 seems to
  tell me that they are all ASCII. So what is it?
  I know that IETF is not happy with using DisplayString, but if
  that is what the underlying technology (outside IETF) uses, then
  we should at least not suggest that it is different.
  I could accept that we say "we want to be prepared for UTF-8 
  strings, but for now it is ASCII as per DC-GS-5)". But it 
  might be good to then explicitly state so in the DESCRIPTION
  clauses of these objects.

  At the other hand, the objects are all read-only, and so even
  if they only present ASCII data (in UTF-8 that is exactly the
  same), then it woul still be fine.

  I also wonder if the length for t11FcsPlatformVendorId,
  t11FcsPlatformProductId can actually be zero, because table
  121 says that these are REQUIRED fields.

- For:

  t11FcsPlatformFC4Types  OBJECT-TYPE
    SYNTAX       OCTET STRING (SIZE (0 | 32))

  should be 
    SYNTAX       OCTET STRING (SIZE (0 | 20))

  that is what I read in table 121 of
  http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf


- Object t11FcsNodeName. Is it supposed to represent this:

  6.2.3.4.6 Platform Node Name
     The format of the Platform Node Name attribute, as used by
     the Fabric Configuration Server, shall be identical to the
     Name_Identifier format defined in FC-FS. Zero or more
     Platform Node Name attributes may be associated with a 
     Platform object. Node Names are registered to associate
     a Platform with the Nodes.
     This attribute may be registered using the protocol described
     in 6.2.2.3. The null value for the platform Node Name
     attribute is 00 00 00 00 00 00 00 00h

  That last description of 8 hex zeroes for a null value seems
  to conflict with the underlying 

    SYNTAX       FcNameIdOrZero

  that you are using in the MIB.

- W.r.t.
 
  t11FcsNotifyControlTable OBJECT-TYPE
    SYNTAX       SEQUENCE OF T11FcsNotifyControlEntry
    MAX-ACCESS   not-accessible
    STATUS       current
    DESCRIPTION
            "A table of control information for notifications
            generated due to Fabric Configuration Server events.

            Values written to objects in this table should be
            persistent/retained over agent reboots."

  I have the same questions/concerns about the "should be persistent"
  as I had for the RSCN MIB module. 
  So we can probably resolve this one in the same way (or leave it
  if everyone thinks that I worry too much).

- It might be good to rename the notifications (for example)

    t11FcsReqRejectNotify NOTIFICATION-TYPE

  from xxxxNotify to xxxxNotification.
  But I agree that this is really nitpicking. 
  For consistency with (most) other MOB modules and notifications
  I think my argument makes sense though.

- For the notifications (and the control there-of), it again seems
  that the Transport Area may want us to say somehting about the
  max number of nitifications to be expected per second/minute/xxx
  or to provide a control varianle that a NMS can SET.


Bert

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



From imss-bounces@ietf.org Tue Sep 05 18:05:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKj2V-00040F-3Y; Tue, 05 Sep 2006 18:05:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKj2T-00040A-Ka
	for imss@ietf.org; Tue, 05 Sep 2006 18:05:01 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GKj2O-00076N-CZ
	for imss@ietf.org; Tue, 05 Sep 2006 18:05:01 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 05 Sep 2006 15:04:56 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k85M4twF013487; Tue, 5 Sep 2006 15:04:55 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k85M4tYp009685;
	Tue, 5 Sep 2006 15:04:55 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id PAA28152;
	Tue, 5 Sep 2006 15:03:51 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609052203.PAA28152@cisco.com>
Subject: Re: [imss] WG Last Call: draft-ietf-imss-fc-fcs-mib-00.txt
To: bwijnen@lucent.com
Date: Tue, 5 Sep 2006 15:03:51 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 04, 2006 06:23:41 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=31381; t=1157493895; x=1158357895;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20WG=20Last=20Call=3A=20draft-ietf-imss-fc-fcs-mib-00.txt;
	X=v=3Dcisco.com=3B=20h=3DApB5qo9OnOCGozri+ssfql3/aA4=3D;
	b=dVggQUC90mWRDJ6uFJ9hk6jfiYTRhycyQbVvB9q+cbAlqqhG0Ycg2A/8oN7VJ4dCxfdsyuzg
	8LoBEVh8KIG40iJhrbhKNj8tAYj3P/MffHKlc3meKWPVZ0YE7uVXAhN6;
Authentication-Results: sj-dkim-4.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8403cbbf1773e27474a13192645c46f
Cc: imss@ietf.org
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

Bert,

Thanks for the comments.  My responses are below.

Keith.
-----------------

> - In the MODULE-IDENTITY, I see:
> 
>     REVISION  "200608140000Z"
>     DESCRIPTION
>             "Initial version of this MIB module."
>     ::= { mib-2 nnn }                     -- to be determined later
>   
>   I think I would make that:
> 
>     REVISION  "200608140000Z"
>     DESCRIPTION
>             "Initial version of this MIB module, published as RFC yyyy."
>     -- RFC-Editor, replace yyyy with actual RFC number & remove this note
>     ::= { mib-2 nnn }  -- to be assigned by IANA.
>     -- RFC Editor: replace nnn with IANA-assigned number & remove this note
> 
> - To avoid later comments, I would also add this to the DESCRIPTION
>   clause of the MODULE-IDENTITY itself:
> 
>            Copyright (C) The Internet Society (2006).  This version of
>            this MIB module is part of RFC yyyy;  see the RFC itself for
>            full legal notices."
> 
>    -- RFC Editor: replace yyyy with actual RFC number & remove this note
 
Oops.  All of this WG's other recent drafts have the required boilerplate;
I'm not sure how this one slipped through without it.

> - I wonder if we would not better rename these TCs (for naming consistency):
> 
>      FcIeType, FcPortState, FcPortTxType
>  
>   and name them instead as follows:
> 
>      T11FcIeType, T11FcPortState, T11FcPortTxType
> 
>   Or are these 3 TCs extending the set of FcXxxx TCs in RFC4044?
>   If so, the I'd suggest to add at least a small SMI comment to state that,
>   so that it is clear why the names are as chosen.
 
I named them to be consistent with FcPortType, and, *if* we were updating
RFC4044, then I'd put them in there, but we're not.   So, rather than
add a "small SMI comment", I'd prefer to change their names.

> - For consistency, but also for betetr info in the DESCRIPTION clause,
>   I would consider to change:
> 
>   FcPortTxType ::= TEXTUAL-CONVENTION
>     STATUS  current
>     DESCRIPTION
>             "The technology of the port transceiver:
> 
>                 unknown        - unknown (includes the 'null' type)
>                 other          - some other technology
>                 shortwave850nm - Short wave laser - SN (850 nm)
>                 longwave1550nm - Long wave laser - LL (1550 nm)
>                 longwave1310nm - Long wave laser cost
>                                  reduced - LC (1310 nm)
>                 electrical     - Electrical - EL."
> 
>   into:
> 
>   FcPortTxType ::= TEXTUAL-CONVENTION
>     STATUS  current
>     DESCRIPTION
>             "The technology of the port transceiver:
> 
>                 unknown(1)        - unknown (includes the 'null' type)
>                 other(2)          - some other technology
>                 shortwave850nm(3) - Short wave laser - SN (850 nm)
>                 longwave1550nm(4) - Long wave laser - LL (1550 nm)
>                 longwave1310nm(5) - Long wave laser cost
>                                     reduced - LC (1310 nm)
>                 electrical(6)     - Electrical - EL."
 
OK.

> - I am a bit surprised by:
> 
>   T11ListIndexPointer ::= TEXTUAL-CONVENTION
>     STATUS  current
>     DESCRIPTION
>             "Objects with this syntax point to a list of elements
>             contained in a table, by holding the same value as the
>             object with syntax T11ListIndex defined in the table's
>             INDEX clause, or, zero to indicate an empty list.
>             The definition of an object with this syntax must
>             identify the table(s) into which it points."
>     SYNTAX  Unsigned32 -- the default range of (0..4294967295)
> 
>   First, I would make it:  SYNTAX Unsigned32 (0..4294967295)
>   instead of putting that in a SMI comment field.
 
The reason I added the ASN.1 comment was to dispel all ambiguity,
i.e., to make it clear that the definition intentionally uses the
default range.  Thus, there is no reason to include the default range
explicitly in the syntax.  Why do we have a default range if we're not
allowed to use it ??

>   Second, I think we normally would use a name of 
> 
>     T11ListIndexOrZero ::= TEXTUAL-CONVENTION
> 
>   To complement the T11ListIndex TC, which does not include the zaero.
> 
>   Third, we also normally do not prescribe what a value of zero means,
>   but we normally say something aka (this is from InetrfaceIndexOrZero):
> 
>             "This textual convention is an extension of the
>             InterfaceIndex convention.  The latter defines a greater
>             than zero value used to identify an interface or interface
>             sub-layer in the managed system.  This extension permits the
>             additional value of zero.  the value zero is object-specific
>             and must therefore be defined as part of the description of
>             any object which uses this syntax.  Examples of the usage of
>             zero might include situations where interface was unknown,
>             or when none or all interfaces need to be referenced."
> 
>   We in fact have quite a few of these XxxSomeIndex and XxxSomeIndexOrZero
>   TCs, which all (i believe) follow/use that same concept. I would strongly
>   suggest that we do so here as well.
> 
>   Mmmm... I see that for some other TCs in the FC/IMSS/IPS space you do
>   not follow the InterfaceIndex/InetrfaceInexOrZero so closely either.
>   Oh well... Up to you and the WG. I personally like the InterfaceIndeOrZero
>   approach better. 
 
OK, I'll rename the TC to T11ListIndexPointerOrZero.

> - I see REFERENCE clauses aka:
> 
>     REFERENCE
>             "ANSI INCITS xxx-200x, Fibre Channel - Generic Services 5,
>             FC-GS-5 T11/Project 1677-D/Rev 8, Table 124."
> 
>   which relates to this reference (I guess):
> 
>    [FC-GS-5]
>      "Fibre Channel - Generic Services - 5 (FC-GS-5)", ANSI INCITS
>      xxx-200x, T11/Project 1677-D/Rev 8.00
>      http://www.t11.org/t11/stat.nsf/upnum/1677-d, September 2004.
> 
>   Do we know when we will get a stable reference?
>   It is normative, so we may have to say something about that.
> 
>   I guess Keith already stated that David or Claudio should answer this 
>   question.
 
Claudio said this morning that revision 8.5 is the final one.
So, I need to go ahead and update the MIB based on Rev 8.5,
including adding any new enumerations which have been defined
since Rev 8.0.

> - For t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh,
>   is the value in these objects included in teh range? My read would
>   say they are. But we may want to make that clear by stating it?
 
OK, I'll change:

            "The discovery by a particular switch operates
            within all existing Fabrics that have a fabric
            index within a specific range.  ...
to:
            "The discovery by a particular switch operates
            within all existing Fabrics that have a fabric
            index within a specific inclusive range.  ...

> - For t11FcsFabricDiscoveryStart, how long does discovery take?
>   The reason I ask, is that if it may take a while, that we might
>   want to consider a value like "discoveryInProgress(3) ??
>   Just thinking aloud, I can also live with what we have in there now.
 
I think this is already available since 'inProgress' is one of the
defined values for t11FcsDiscoveryStatus.

> - t11FcsFabricDiscoveryTable
>   I guess that this table gets created/instantiated by the agent everytime
>   it starts. There are no default values for the two objects 
>   t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh.
>   So how is the behavioud if I issue a DiscoveryStart when these objects
>   have not been SET yet? Should we define DEFVALs?

Just adding DEFVALs would be a temptation to write sloppy applications,
because an NMS can not be sure whether a particular entry has been used
or not since the last reboot.  Thus, invoking DiscoveryStart without
checking the values of RangeLow and RangeHigh, would be very sloppy.
Given that an application needs to check, then it also has to change
the values if they're wrong.  Thus, the simplest way to write such an
application is to always specify the range explicitly (i.e., write
RangeLow and RangeHigh) at the same time as invoking DiscoveryStart.

So, I propose to add a recommendation to the DESCRIPTION like this:

  t11FcsFabricDiscoveryStart  OBJECT-TYPE
      SYNTAX       INTEGER {
                       start(1),
                       noOp(2)
                   }
      MAX-ACCESS   read-write
      STATUS       current
      DESCRIPTION
              "This object provides the capability to trigger the start
              of a discovery by a Fabric Configuration Server.  If this
              object is set to 'start', then the discovery is started on
              those fabrics which have their fabric index value in the
              range specified by t11FcsFabricDiscoveryRangeLow and
              t11FcsFabricDiscoveryRangeHigh.  It is recommended that
              whenever an instance of this object is set to 'start',
              that the desired range be concurrently specified by
              setting the corresponding instances of
              t11FcsFabricDiscoveryRangeLow and
              t11FcsFabricDiscoveryRangeHigh.

> - Given the DESCRIPTION clause of t11FcsFabricDiscoveryStart, I 
>   suggest to add  DEFVAL { noOp }

Since the value when read is always 'noOp', to specify a DEFVAL would
either be redundant, or worse, it would weaken the definition because a
DEFVAL is only advisory, whereas the statement:  "the value when read
is always 'noOp'" is mandatory.

> - I suppose that SETTING t11FcsDiscoveryStatus to one of
>                      inProgress(1),
>                      completed(2),
>   would have no effect? I.e. it would be ignored?
>   Whatever the intended behaviour is to be, we probably do best to
>   be specific as to what we want an agent to do.
> 
>   I personally kind of like to add something to the MODULE-COMPLIANCE<
>   which states that the WRITE-SYNTAX is  localOnly(3) and that
>   the SYNTAX is all 3 values. I think that expresses that only the
>   one value that makes sense can be SET/written.
> 
>   I personally might do a similar thing for t11FcsFabricDiscoveryStart,
>   but that one at least explains what to do if I set the value to
>   something that does not trigger an action.
 
I prefer to add a sentence to the DESCRIPTION of t11FcsDiscoveryStatus,
like this:

            It is an error for a manager to set the value of this
            object to anything other than 'localOnly'."

> - t11FcsDiscoveryStatus has no persistency (or so is my reading of
>   the DESCRIPTION clause) and will be set to localOnly upon a restart?
>   If so, it might be usefull to add a sentence about that, just to be
>   explicit and clear.
 
It already has this sentence:

            Initially when the switch comes up, all instances of this
            object have the value: 'localOnly'

Do you want me to change "switch comes up" to "agent restarts" ??

> - For objects t11FcsIeName and t11FcsIeDomainId, I wonder if a zero
>   (i.e. zero length OCTET STRING) are really valid. If not, then we
>   should add a SIZE and RANGE restriction.
 
FC-GS-5 says:

  6.2.3.2.1 Interconnect Element Name

  The format of the Interconnect Element Name attribute, as used by the
  Fabric Configuration Server, shall be identical to the Name_Identifier
  format defined in FC-FS. If the Interconnect Element is a Switch (see
  FC-SW), the Interconnect Element Name attribute shall be the
  Switch_Name of the Switch.

  This standard does not define how this attribute is registered with the
  Fabric Configuration Server.  The null value for the Interconnect
  Element Name attribute is 00 00 00 00 00 00 00 00h.

and

  6.2.3.2.3 Interconnect Element Domain Identifier

  The format of the Interconnect Element Domain Identifier attribute, as
  used by the Fabric Configuration Server, shall be identical to the
  Domain Identifier format defined in FC-SW-3.

  This standard does not define how this attribute is registered with the
  Fabric Configuration Server.  The null value for the Interconnect
  Element Domain Identifier attribute is 00h.

Since t11FcsIeDomainId can have a value of zero, FcDomainIdOrZero
(which is defined as "SYNTAX  Integer32 (0..239)")  should not be
restricted.

For t11FcsIeName, the "null" value is specified as all zeros, rather
than the zero-length value.  So, yes, I'll add a restricted range:

  t11FcsIeName  OBJECT-TYPE
      SYNTAX       FcNameIdOrZero (SIZE(8 | 16))

> - This definition seems strange:
> 
>   t11FcsIeFabricName  OBJECT-TYPE
>     SYNTAX       FcNameIdOrZero
>     MAX-ACCESS   read-only
>     STATUS       current
>     DESCRIPTION
>             "The Fabric_Name (WWN) of this Interconnect Element.
>             When the Fabric_Name is unknown, this object contains
>             the all-zeros value: x'00 00 00 00 00 00 00 00'."
>     REFERENCE
>             "ANSI INCITS xxx-200x, Fibre Channel - Generic Services 5,
>             FC-GS-5 T11/Project 1677-D/Rev 8, section 6.2.3.2.5."
>     DEFVAL { '0000000000000000'h }
>     ::= { t11FcsIeEntry 5 }

I'll add a restricted range here too.

  t11FcsIeFabricName  OBJECT-TYPE
      SYNTAX       FcNameIdOrZero (SIZE(8 | 16))

> - I see this:
> 
>   t11FcsIeMgmtAddrListIndex  OBJECT-TYPE
>     SYNTAX       T11ListIndexPointer
>     MAX-ACCESS   read-only
>     STATUS       current
>     DESCRIPTION
>             "The management address list for this Interconnect Element.
>             This object points to an entry in the
>             t11FcsMgmtAddrListTable."
> 
>   Reading the DESCRIPTIOn clause, I wonder why one would not use a 
>   RowPointer. The fact is that the pointer does not point to "an entry"
>   in the t11FcsMgmtAddrListTable, but to a SET of such entries.
>   So I guess the DESCRIPTION clause could be clarified.

It is sufficient (and simpler) for this TC to be an Unsigned32, whereas
RowPointer is an OID.
 
As a clarification, I've added this sentence to T11ListIndexPointerOrZero's
DESCRIPTION:

              Note that such a table could have one row per list, or
              it could have one row per element of a list.
 
> - I see:
>  
>   t11FcsIeInfoList  OBJECT-TYPE
>     SYNTAX       OCTET STRING (SIZE (0..252))
>     MAX-ACCESS   read-only
>     STATUS       current
>     DESCRIPTION
>             "The information list for this Interconnect Element.
>             This object contains the following substrings in order:
>             vendor name, model name/number and release code/level,
>             followed by zero or more substrings of vendor-specific
>             information. Each substring is terminated with a byte
>             containing a null value (x'00')."
> 
>   And that reads as if it is ASCII information to be (potentially) 
>   consumed by human beings.  So in that case, the IETF wants it to
>   be an internationalized string.  Comment?
 
FC-GS-5 requires the individual values to be ASCII strings (terminated
by nulls).  I'll edit the DESCRIPTION to be:

            The value of this object is formatted as specified in
            FC-GS-5, i.e., it contains the following substrings in
            order:  vendor name, model name/number and release
            code/level, followed by zero or more substrings of
            vendor-specific information. Each substring is terminated
            with a byte containing a null value (x'00')."

> - I see:
> 
>   t11FcsMgmtAddr  OBJECT-TYPE
>     SYNTAX       SnmpAdminString
>     MAX-ACCESS   read-only
>     STATUS       current
>     DESCRIPTION
>             "The management address of this entry.
>             The format of this object may be based on the
>             format of the Uniform Resource Locator (URL).
>             For example, for SNMP, see RFC 4088."
> 
>   So it syas "the format MAY be based on..." (my emphasis on MAY).
>   So, does that mean it may also be based on something else?
>   How do I determine what the actual format is?
 
On re-reading FC-GS-5, I see that it's required to be a URL, and
it's the use of 4088 which is not required.  So, I'll change it to:

            The format of this object is a Uniform Resource Locator
            (URL), e.g., for SNMP, see RFC 4088."

> - SMICng gave a warning about the indexing of
> 
>   t11FcsPortListEntry  OBJECT-TYPE
>     SYNTAX       T11FcsPortListEntry
>     MAX-ACCESS   not-accessible
>     STATUS       current
>     DESCRIPTION
>             "An entry which identifies that the port which has the
>             port name, t11FcsPortName, is in a particular list of
>             ports, which is known to a switch (identified by
>             fcmInstanceIndex and fcmSwitchIndex)."
>     INDEX   { fcmInstanceIndex,  fcmSwitchIndex,
>               t11FcsPortListIndex, t11FcsPortName }
>     ::= { t11FcsPortListTable 1 }
> 
>   I read Keiths explanation, which seemed fine. But now that I am
>   reviewing the MIB module in details and try to understand things,
>   now I am no so sure this is goodness.
> 
>   So, that t11FcsPortname is a value (embedded in the index) that
>   should help me find more detailed info, right?
>   So how do I find that info? I think I need to go to the
>   t11FcsPortTable, which is indexed by:
> 
>     INDEX   { fcmInstanceIndex, fcmSwitchIndex,
>               t11FcsFabricIndex, t11FcsPortName }
> 
>   So assuming that the index values for fcmInstanceIndex, fcmSwitchIndex,
>   are the same in both tables, I can see that I can pick up 3 index
>   values from the list of t11FcsPortsList in the t11FcsPortsListTable.
>   But I am missing the 3rd index of the t11FcsPortnameTable, namely
>   t11FcsFabricIndex. So how am I going to wuickly pick that up?
>   Or how exactly are the tables connected/linked?
> 
>   Maybe I need to study it deeper... but I'd prefer an explanation of
>   the people who created these tables with the current indexing schemes.
 
To generate an answer to your question, I needed to re-review the
structure of the tables, and in doing so, I now think that the current
structure is more open-ended/flexible than it needs to be -- having a
less open-ended structure would make the MIB simpler.  Specifically,
the MIB currently has a table whose only purpose is to identify a list
of (not necessarily related) ports.  However,

- each IE is either a virtual IE attached to one virtual Fabric, or
  (if virtual Fabrics are not in use) it's a physical IE.
- each port is either a virtual port attached to one virtual Fabric, or
  (if virtual Fabrics are not in use) it's a physical port.
- GS-5 mentions that an IE has a "port list" and has a dotted line from the
  "Interconnect Element Object" to the "Port Object" in its "Figure 7 --
  Interconnect Element and Port attributes".
- However, all ports in an IE's port list will be attached to the same 
  Fabric as that IE is attached to.  In other words, the relationship
  between IEs and ports is hierarchical.
- Thus, it would be simpler to:

  - delete the t11FcsPortListTable,
  - delete the t11FcsIePortListIndex object, and
  - insert t11FcsIeName into the INDEX of the t11FcsPortTable, i.e.,
    change the INDEX-ing of the t11FcsPortTable to be:

      INDEX   { fcmInstanceIndex, fcmSwitchIndex, t11FcsFabricIndex,
                t11FcsIeName, t11FcsPortName }

Increasing the INDEX clause from four to five objects makes it a little
more cumbersome, but the length is still far short of the maximum length.

With these changes, while there will no longer be any explicit mention
of a "port list" in the MIB, the list of ports on an IE will be all
the rows in t11FcsPortTable which have the same values for the first
four index objects, i.e., the value of t11FcsPortName will be the only
index value for which they differ.  So, a "port list" is (implicitly)
a set of adjacent rows in the t11FcsPortTable.

David, since this is a MIB design change, may I suggest you ask the WG
for approval of this as a separate/individual question.

> - for
>  
>   t11FcsPortName  OBJECT-TYPE
>     SYNTAX       FcNameIdOrZero
>     MAX-ACCESS   not-accessible
>     STATUS       current
>     DESCRIPTION
>             "The Port_Name (WWN) of the port for which this row
>             contains information."
> 
>   I wonder if a zero value (zero length OCTET STRING) is really valid?
>   If not, then we may need to limit it with a SIZE paramter aka
>     SYNTAX       FcNameIdOrZero SIZE (8 | 16)
> 
>   But,  I do see that in sect "6.2.3.3.1 Port Name" of document
>   http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf, it says:
> 
>       The null value for the Port Name attribute is
>       00 00 00 00 00 00 00 00h.
> 
>   So... is the SYNTAX of FcNameIdOrZero appropriate here? 
>   In any event, the name SIZE seems to be fixed at 8 octets for the
>   PortName, so at least one would then define the syntax as:
> 
>     SYNTAX       FcNameIdOrZero (SIZE (8))
 
A length of 16 is still a possibility -- section 6.2.3.3.1 refers to
FC-FS, in which section 15 (table 66) includes one format which has a
length of 128 (bits).

So, I'll chaneg it to:
 
      SYNTAX       FcNameIdOrZero (SIZE(8 | 16))

> - For:
> 
>   t11FcsPortModuleType  OBJECT-TYPE
>     SYNTAX       Unsigned32 (0..255)
>     MAX-ACCESS   read-only
>     STATUS       current
>     DESCRIPTION
>             "The port module type of this port."
>     REFERENCE
>             "ANSI INCITS xxx-200x, Fibre Channel - Generic Services 5,
>             FC-GS-5 T11/Project 1677-D/Rev 8, section 6.2.3.3.4."
> 
>   It seems better to create a TC that ENUMerates the valid values?

The choice between using either an enumerated value, or, a numeric
value to be looked up in another specification, is a trade-off of
convenience versus maintenance.  For something which changes
frequently, it's better that the MIB *not* contain a list which is
frequently out-of-date; for something which changes infrequently, it's
better to have the convenience of enumeration.
 
Specifically, for those objects defined in this MIB as enumerations,
when a new value is defined in T11, the new value cannot be used in the
MIB until the MIB is updated.  When the MIB syntax is Unsigned32,
new values can be used in the MIB as soon as they are defined by T11.

So, we intentionally chose to specify some objects in this MIB as
enumerations, and others as binary values, based on the frequency at
which new values can be expected to be defined and used -- not just in
the now completed GS-5, but also in GS-6 and its successors.

> - For:
> 
>   t11FcsPortSpeedCapab  OBJECT-TYPE
>     SYNTAX       OCTET STRING (SIZE (2))
> 
>   It seems that the references document and section say that it is a BITS
>   construct ??
> 
> - Same for t11FcsPortOperSpeed
 
While the Capability could be a BITS, OperSpeed would only ever have one
bit set, i.e., not a BITS.  However, both of these are further examples of
the enumerated versus numeric trade-off mentioned above.  That is, port
speed is another area where new enumerations can be expected and will
need to be used.

> - For:
> 
>   t11FcsPlatformName  OBJECT-TYPE
>     SYNTAX       OCTET STRING (SIZE (0..255))
> 
>   It seems to me that the SYNTAX better be:
> 
>     SYNTAX       OCTET STRING (SIZE (0 | 3..256))
> 
>   because http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf
>   section 6.2.3.4.2 tells me:
> 
>     The Platform Name attribute may be registered using the
>     protocol described in 6.2.2.3. The null value for the
>     Platform Name attribute is a zero-length Platform Name.
> 
>   So maybe that is how we can get a length of zero. But I am
>   not even sure about that. It is also possible that the
>   first byte would be valued at zero. Is the format octet 
>   included in this case? Not clear from the PDF file for me.
> 
>   If I understand the PDF file correctly, then (it speaks about
>   reserved to be of length 254-m) then there are 2 octets (1 for
>   length, one for format) plus 254 for the actual name. So that
>   would be a max size of 256 in my view.
 
Many of the format specifications in the GS-5 spec. are like this:

              Logical Name length (m)     1
              Logical Name                m
              Reserved                  255-m

where the aggregate length (of the three sub-fields) is 256 bytes.

So, the way that I interpret the Platform Name field:

              Platform Name length (m)     1
              Platform Name                m
              Platform Name Format         1
              Reserved                   254-m

is similarly, to have an aggregate length is 256 bytes.  Therefore, the
correct MIB syntax is:

     SYNTAX       OCTET STRING (SIZE (0..254))

where the range is the value of m.

> - Several objects in the t11FcsPlatformTable
>   (like t11FcsPlatformVendorId, t11FcsPlatformProductId , etc)
>   suggest (based on the SYNTAX of SnmpAdminString) that the value
>   can be an internationalized human readable string.
>   But the table 121 in the PDF file, section 6.2.3.4.5 seems to
>   tell me that they are all ASCII. So what is it?

It's the format as specified in section 6.2.3.4.5, which is a
subset of SnmpAdminString, which I believe means that using
SnmpAdminString as the syntax is fine.

>   I know that IETF is not happy with using DisplayString, but if
>   that is what the underlying technology (outside IETF) uses, then
>   we should at least not suggest that it is different.
>   I could accept that we say "we want to be prepared for UTF-8 
>   strings, but for now it is ASCII as per DC-GS-5)". But it 
>   might be good to then explicitly state so in the DESCRIPTION
>   clauses of these objects.
> 
>   At the other hand, the objects are all read-only, and so even
>   if they only present ASCII data (in UTF-8 that is exactly the
>   same), then it would still be fine.

How about I leave it as SnmpAdminString, and point to GS-5 for
the definition of which characters are valid:

            "The identifier of the vendor of this platform, in
            the format specified by FC-GS-5."

>   I also wonder if the length for t11FcsPlatformVendorId,
>   t11FcsPlatformProductId can actually be zero, because table
>   121 says that these are REQUIRED fields.

The table gives their minimum length when they are present, *but*
a "Platform Attribute Block" doesn't necessarily contain them all.
 
> - For:
> 
>   t11FcsPlatformFC4Types  OBJECT-TYPE
>     SYNTAX       OCTET STRING (SIZE (0 | 32))
> 
>   should be 
>     SYNTAX       OCTET STRING (SIZE (0 | 20))
> 
>   that is what I read in table 121 of
>   http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf

The text which follows the table says:

   Supported FC-4 Types: This is an 8 word (256 bit) bit mask that
   indicates what FC-4 types are supported on this platform (see 5.2.3.8).
   FCP-2 (FC-4 type 08h) is represented by bit 8 of word 0. The Fabric
   Configuration Server shall not attempt validation of the FC-4 Types
   attribute, and any value shall be accepted for this attribute.

I think the table has a typo.

> - Object t11FcsNodeName. Is it supposed to represent this:
> 
>   6.2.3.4.6 Platform Node Name
>      The format of the Platform Node Name attribute, as used by
>      the Fabric Configuration Server, shall be identical to the
>      Name_Identifier format defined in FC-FS. Zero or more
>      Platform Node Name attributes may be associated with a 
>      Platform object. Node Names are registered to associate
>      a Platform with the Nodes.
>      This attribute may be registered using the protocol described
>      in 6.2.2.3. The null value for the platform Node Name
>      attribute is 00 00 00 00 00 00 00 00h
> 
>   That last description of 8 hex zeroes for a null value seems
>   to conflict with the underlying 
> 
>     SYNTAX       FcNameIdOrZero
> 
>   that you are using in the MIB.
 
Ok, I'll change it to:
 
      SYNTAX       FcNameIdOrZero (SIZE(8 | 16))

> - W.r.t.
>  
>   t11FcsNotifyControlTable OBJECT-TYPE
>     SYNTAX       SEQUENCE OF T11FcsNotifyControlEntry
>     MAX-ACCESS   not-accessible
>     STATUS       current
>     DESCRIPTION
>             "A table of control information for notifications
>             generated due to Fabric Configuration Server events.
> 
>             Values written to objects in this table should be
>             persistent/retained over agent reboots."
> 
>   I have the same questions/concerns about the "should be persistent"
>   as I had for the RSCN MIB module. 
>   So we can probably resolve this one in the same way (or leave it
>   if everyone thinks that I worry too much).
 
OK.

> - It might be good to rename the notifications (for example)
> 
>     t11FcsReqRejectNotify NOTIFICATION-TYPE
> 
>   from xxxxNotify to xxxxNotification.

I chose to use t11FcsReqRejectNotify because t11FcsReqRejectNotification
is 33 characters long, and I think using t11FcsReqRejectNotify is a
clearer abbreviation than t11FcsReqRejNotification.
I guess I could go for:

     t11FcsRqRejectNotification NOTIFICATION-TYPE

if you prefer.

>   But I agree that this is really nitpicking. 
>   For consistency with (most) other MOB modules and notifications
>   I think my argument makes sense though.
> 
> - For the notifications (and the control there-of), it again seems
>   that the Transport Area may want us to say somehting about the
>   max number of nitifications to be expected per second/minute/xxx
>   or to provide a control varianle that a NMS can SET.
 
Their motivation is good, and is applicable to data-plane events, but
asking for a max number per unit time for every type of notification
is too simplistic.  E.g., it's unreasonable to ask how many
t11FcsDiscoveryCompleteNotify notifications can be generated in a
second/minute/xxx -- how big is the network, how many virtual fabrics
need to be discovered, how quickly can the operator ask for another
discovery after the last one completes ??

If a max rate is specified by an NMS, such that notifications can be
suppressed due to their volume, then there needs to be some mechanism
for the NMS to know that suppression(s) have happened/are happening,
which means more notification-types and objects need to be defined.
That is, it increases the complexity, which is not warranted unless
there can really be a "flood" of notifications.

For notifications, like all the ones in this MIB, which are generated
due to control plane events (and providing that none of them are able
to start a chain-reaction), the extra complexity is not warranted.

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



From imss-bounces@ietf.org Wed Sep 06 08:52:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GKwsl-0002rl-Ca; Wed, 06 Sep 2006 08:51:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GKwsk-0002qi-NY
	for imss@ietf.org; Wed, 06 Sep 2006 08:51:54 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GKwsg-0007mM-H4
	for imss@ietf.org; Wed, 06 Sep 2006 08:51:54 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k86CpdUK014765;
	Wed, 6 Sep 2006 07:51:40 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK9J6G>; Wed, 6 Sep 2006 14:51:38 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96A66@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>
Subject: RE: [imss] WG Last Call: draft-ietf-imss-fc-fcs-mib-00.txt
Date: Wed, 6 Sep 2006 14:51:38 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c2e2c4cc85c1e4abb3543006fe55789b
Cc: imss@ietf.org
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

Inline

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Wednesday, September 06, 2006 00:04
> To: bwijnen@lucent.com
> Cc: imss@ietf.org
> Subject: Re: [imss] WG Last Call: draft-ietf-imss-fc-fcs-mib-00.txt
> 
> 
> Bert,
> 
> Thanks for the comments.  My responses are below.
> 
> Keith.
> -----------------
> 
> > - In the MODULE-IDENTITY, I see:
> > 
> >     REVISION  "200608140000Z"
> >     DESCRIPTION
> >             "Initial version of this MIB module."
> >     ::= { mib-2 nnn }                     -- to be determined later
> >   
> >   I think I would make that:
> > 
> >     REVISION  "200608140000Z"
> >     DESCRIPTION
> >             "Initial version of this MIB module, published 
> as RFC yyyy."
> >     -- RFC-Editor, replace yyyy with actual RFC number & 
> remove this note
> >     ::= { mib-2 nnn }  -- to be assigned by IANA.
> >     -- RFC Editor: replace nnn with IANA-assigned number & 
> remove this note
> > 
> > - To avoid later comments, I would also add this to the DESCRIPTION
> >   clause of the MODULE-IDENTITY itself:
> > 
> >            Copyright (C) The Internet Society (2006).  This 
> version of
> >            this MIB module is part of RFC yyyy;  see the 
> RFC itself for
> >            full legal notices."
> > 
> >    -- RFC Editor: replace yyyy with actual RFC number & 
> remove this note
>  
> Oops.  All of this WG's other recent drafts have the required 
> boilerplate;
> I'm not sure how this one slipped through without it.
> 

Thanks

> > - I wonder if we would not better rename these TCs (for 
> naming consistency):
> > 
> >      FcIeType, FcPortState, FcPortTxType
> >  
> >   and name them instead as follows:
> > 
> >      T11FcIeType, T11FcPortState, T11FcPortTxType
> > 
> >   Or are these 3 TCs extending the set of FcXxxx TCs in RFC4044?
> >   If so, the I'd suggest to add at least a small SMI 
> comment to state that,
> >   so that it is clear why the names are as chosen.
>  
> I named them to be consistent with FcPortType, and, *if* we 
> were updating
> RFC4044, then I'd put them in there, but we're not.   So, rather than
> add a "small SMI comment", I'd prefer to change their names.
> 

Sounds good to me

> > - For consistency, but also for betetr info in the 
> DESCRIPTION clause,
> >   I would consider to change:
> > 
> >   FcPortTxType ::= TEXTUAL-CONVENTION
> >     STATUS  current
> >     DESCRIPTION
> >             "The technology of the port transceiver:
> > 
> >                 unknown        - unknown (includes the 'null' type)
> >                 other          - some other technology
> >                 shortwave850nm - Short wave laser - SN (850 nm)
> >                 longwave1550nm - Long wave laser - LL (1550 nm)
> >                 longwave1310nm - Long wave laser cost
> >                                  reduced - LC (1310 nm)
> >                 electrical     - Electrical - EL."
> > 
> >   into:
> > 
> >   FcPortTxType ::= TEXTUAL-CONVENTION
> >     STATUS  current
> >     DESCRIPTION
> >             "The technology of the port transceiver:
> > 
> >                 unknown(1)        - unknown (includes the 
> 'null' type)
> >                 other(2)          - some other technology
> >                 shortwave850nm(3) - Short wave laser - SN (850 nm)
> >                 longwave1550nm(4) - Long wave laser - LL (1550 nm)
> >                 longwave1310nm(5) - Long wave laser cost
> >                                     reduced - LC (1310 nm)
> >                 electrical(6)     - Electrical - EL."
>  
> OK.
> 
thanks

> > - I am a bit surprised by:
> > 
> >   T11ListIndexPointer ::= TEXTUAL-CONVENTION
> >     STATUS  current
> >     DESCRIPTION
> >             "Objects with this syntax point to a list of elements
> >             contained in a table, by holding the same value as the
> >             object with syntax T11ListIndex defined in the table's
> >             INDEX clause, or, zero to indicate an empty list.
> >             The definition of an object with this syntax must
> >             identify the table(s) into which it points."
> >     SYNTAX  Unsigned32 -- the default range of (0..4294967295)
> > 
> >   First, I would make it:  SYNTAX Unsigned32 (0..4294967295)
> >   instead of putting that in a SMI comment field.
>  
> The reason I added the ASN.1 comment was to dispel all ambiguity,
> i.e., to make it clear that the definition intentionally uses the
> default range.  Thus, there is no reason to include the default range
> explicitly in the syntax.  Why do we have a default range if we're not
> allowed to use it ??
> 

You are allowed to do so. I normally prefer to make it 100%
clear (if possible in machine readable form)
And... since you agree with the below, to be consistent with
other xxxOrZero TCs (like InterfaceIndexOrZero for example).

But I won't loose sleep if you do not do this.
I just wrote how I looked at it to try and help be clear and
consistent.

> >   Second, I think we normally would use a name of 
> > 
> >     T11ListIndexOrZero ::= TEXTUAL-CONVENTION
> > 
> >   To complement the T11ListIndex TC, which does not include 
> the zaero.
> > 
> >   Third, we also normally do not prescribe what a value of 
> zero means,
> >   but we normally say something aka (this is from 
> InetrfaceIndexOrZero):
> > 
> >             "This textual convention is an extension of the
> >             InterfaceIndex convention.  The latter defines a greater
> >             than zero value used to identify an interface 
> or interface
> >             sub-layer in the managed system.  This 
> extension permits the
> >             additional value of zero.  the value zero is 
> object-specific
> >             and must therefore be defined as part of the 
> description of
> >             any object which uses this syntax.  Examples of 
> the usage of
> >             zero might include situations where interface 
> was unknown,
> >             or when none or all interfaces need to be referenced."
> > 
> >   We in fact have quite a few of these XxxSomeIndex and 
> XxxSomeIndexOrZero
> >   TCs, which all (i believe) follow/use that same concept. 
> I would strongly
> >   suggest that we do so here as well.
> > 
> >   Mmmm... I see that for some other TCs in the FC/IMSS/IPS 
> space you do
> >   not follow the InterfaceIndex/InetrfaceInexOrZero so 
> closely either.
> >   Oh well... Up to you and the WG. I personally like the 
> InterfaceIndeOrZero
> >   approach better. 
>  
> OK, I'll rename the TC to T11ListIndexPointerOrZero.
> 

Thanks

> > - I see REFERENCE clauses aka:
> > 
> >     REFERENCE
> >             "ANSI INCITS xxx-200x, Fibre Channel - Generic 
> Services 5,
> >             FC-GS-5 T11/Project 1677-D/Rev 8, Table 124."
> > 
> >   which relates to this reference (I guess):
> > 
> >    [FC-GS-5]
> >      "Fibre Channel - Generic Services - 5 (FC-GS-5)", ANSI INCITS
> >      xxx-200x, T11/Project 1677-D/Rev 8.00
> >      http://www.t11.org/t11/stat.nsf/upnum/1677-d, September 2004.
> > 
> >   Do we know when we will get a stable reference?
> >   It is normative, so we may have to say something about that.
> > 
> >   I guess Keith already stated that David or Claudio should 
> answer this 
> >   question.
>  
> Claudio said this morning that revision 8.5 is the final one.
> So, I need to go ahead and update the MIB based on Rev 8.5,
> including adding any new enumerations which have been defined
> since Rev 8.0.
> 

Thanks. I had expected something like that ;-)

> > - For t11FcsFabricDiscoveryRangeLow and 
> t11FcsFabricDiscoveryRangeHigh,
> >   is the value in these objects included in teh range? My read would
> >   say they are. But we may want to make that clear by stating it?
>  
> OK, I'll change:
> 
>             "The discovery by a particular switch operates
>             within all existing Fabrics that have a fabric
>             index within a specific range.  ...
> to:
>             "The discovery by a particular switch operates
>             within all existing Fabrics that have a fabric
>             index within a specific inclusive range.  ...
> 

thanks

> > - For t11FcsFabricDiscoveryStart, how long does discovery take?
> >   The reason I ask, is that if it may take a while, that we might
> >   want to consider a value like "discoveryInProgress(3) ??
> >   Just thinking aloud, I can also live with what we have in 
> there now.
>  
> I think this is already available since 'inProgress' is one of the
> defined values for t11FcsDiscoveryStatus.
> 

Ah... yes... I see that now
Sorry I didn't match them earlier

> > - t11FcsFabricDiscoveryTable
> >   I guess that this table gets created/instantiated by the 
> agent everytime
> >   it starts. There are no default values for the two objects 
> >   t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh.
> >   So how is the behavioud if I issue a DiscoveryStart when 
> these objects
> >   have not been SET yet? Should we define DEFVALs?
> 
> Just adding DEFVALs would be a temptation to write sloppy 
> applications,
> because an NMS can not be sure whether a particular entry has 
> been used
> or not since the last reboot.  Thus, invoking DiscoveryStart without
> checking the values of RangeLow and RangeHigh, would be very sloppy.
> Given that an application needs to check, then it also has to change
> the values if they're wrong.  Thus, the simplest way to write such an
> application is to always specify the range explicitly (i.e., write
> RangeLow and RangeHigh) at the same time as invoking DiscoveryStart.
> 
> So, I propose to add a recommendation to the DESCRIPTION like this:
> 
>   t11FcsFabricDiscoveryStart  OBJECT-TYPE
>       SYNTAX       INTEGER {
>                        start(1),
>                        noOp(2)
>                    }
>       MAX-ACCESS   read-write
>       STATUS       current
>       DESCRIPTION
>               "This object provides the capability to trigger 
> the start
>               of a discovery by a Fabric Configuration 
> Server.  If this
>               object is set to 'start', then the discovery is 
> started on
>               those fabrics which have their fabric index value in the
>               range specified by t11FcsFabricDiscoveryRangeLow and
>               t11FcsFabricDiscoveryRangeHigh.  It is recommended that
>               whenever an instance of this object is set to 'start',
>               that the desired range be concurrently specified by
>               setting the corresponding instances of
>               t11FcsFabricDiscoveryRangeLow and
>               t11FcsFabricDiscoveryRangeHigh.
> 

Works for me.

> > - Given the DESCRIPTION clause of t11FcsFabricDiscoveryStart, I 
> >   suggest to add  DEFVAL { noOp }
> 
> Since the value when read is always 'noOp', to specify a DEFVAL would
> either be redundant, or worse, it would weaken the definition 
> because a
> DEFVAL is only advisory, whereas the statement:  "the value when read
> is always 'noOp'" is mandatory.
> 

Agree. Thanks for reminding me the exact details

> > - I suppose that SETTING t11FcsDiscoveryStatus to one of
> >                      inProgress(1),
> >                      completed(2),
> >   would have no effect? I.e. it would be ignored?
> >   Whatever the intended behaviour is to be, we probably do best to
> >   be specific as to what we want an agent to do.
> > 
> >   I personally kind of like to add something to the 
> MODULE-COMPLIANCE<
> >   which states that the WRITE-SYNTAX is  localOnly(3) and that
> >   the SYNTAX is all 3 values. I think that expresses that only the
> >   one value that makes sense can be SET/written.
> > 
> >   I personally might do a similar thing for 
> t11FcsFabricDiscoveryStart,
> >   but that one at least explains what to do if I set the value to
> >   something that does not trigger an action.
>  
> I prefer to add a sentence to the DESCRIPTION of 
> t11FcsDiscoveryStatus,
> like this:
> 
>             It is an error for a manager to set the value of this
>             object to anything other than 'localOnly'."
> 

It kind of works for me.
But was there not this (maybe it is just implied in my earleir IBM
snmp implementation, but I do recall I did this because of a report
in one of the interoperability tests we had) fact that one would/should
always be able to do a SET for a value that was just READ?

> > - t11FcsDiscoveryStatus has no persistency (or so is my reading of
> >   the DESCRIPTION clause) and will be set to localOnly upon 
> a restart?
> >   If so, it might be usefull to add a sentence about that, 
> just to be
> >   explicit and clear.
>  
> It already has this sentence:
> 
>             Initially when the switch comes up, all instances of this
>             object have the value: 'localOnly'
> 
> Do you want me to change "switch comes up" to "agent restarts" ??
> 

Well, for sure when the agent restarts, the switch might have just stayed
in the same state (already up) I guess.

Either way... in any event, it was not immediately clear to me when
I read it the first time. WIth your explanation, I can see it could
be read that way.
So Up to you if you want to clarify.


> > - For objects t11FcsIeName and t11FcsIeDomainId, I wonder if a zero
> >   (i.e. zero length OCTET STRING) are really valid. If not, then we
> >   should add a SIZE and RANGE restriction.
>  
> FC-GS-5 says:
> 
>   6.2.3.2.1 Interconnect Element Name
> 
>   The format of the Interconnect Element Name attribute, as 
> used by the
>   Fabric Configuration Server, shall be identical to the 
> Name_Identifier
>   format defined in FC-FS. If the Interconnect Element is a 
> Switch (see
>   FC-SW), the Interconnect Element Name attribute shall be the
>   Switch_Name of the Switch.
> 
>   This standard does not define how this attribute is 
> registered with the
>   Fabric Configuration Server.  The null value for the Interconnect
>   Element Name attribute is 00 00 00 00 00 00 00 00h.
> 
> and
> 
>   6.2.3.2.3 Interconnect Element Domain Identifier
> 
>   The format of the Interconnect Element Domain Identifier 
> attribute, as
>   used by the Fabric Configuration Server, shall be identical to the
>   Domain Identifier format defined in FC-SW-3.
> 
>   This standard does not define how this attribute is 
> registered with the
>   Fabric Configuration Server.  The null value for the Interconnect
>   Element Domain Identifier attribute is 00h.
> 
> Since t11FcsIeDomainId can have a value of zero, FcDomainIdOrZero
> (which is defined as "SYNTAX  Integer32 (0..239)")  should not be
> restricted.
> 
> For t11FcsIeName, the "null" value is specified as all zeros, rather
> than the zero-length value.  So, yes, I'll add a restricted range:
> 
>   t11FcsIeName  OBJECT-TYPE
>       SYNTAX       FcNameIdOrZero (SIZE(8 | 16))
> 

Thanks

> > - This definition seems strange:
> > 
> >   t11FcsIeFabricName  OBJECT-TYPE
> >     SYNTAX       FcNameIdOrZero
> >     MAX-ACCESS   read-only
> >     STATUS       current
> >     DESCRIPTION
> >             "The Fabric_Name (WWN) of this Interconnect Element.
> >             When the Fabric_Name is unknown, this object contains
> >             the all-zeros value: x'00 00 00 00 00 00 00 00'."
> >     REFERENCE
> >             "ANSI INCITS xxx-200x, Fibre Channel - Generic 
> Services 5,
> >             FC-GS-5 T11/Project 1677-D/Rev 8, section 6.2.3.2.5."
> >     DEFVAL { '0000000000000000'h }
> >     ::= { t11FcsIeEntry 5 }
> 
> I'll add a restricted range here too.
> 
>   t11FcsIeFabricName  OBJECT-TYPE
>       SYNTAX       FcNameIdOrZero (SIZE(8 | 16))
> 

It works syntax wise. It sort of conflicts with the zero-length-string
I guess. But at least SYNTAX wise we're now in sync with the TC again.

Thanks.

> > - I see this:
> > 
> >   t11FcsIeMgmtAddrListIndex  OBJECT-TYPE
> >     SYNTAX       T11ListIndexPointer
> >     MAX-ACCESS   read-only
> >     STATUS       current
> >     DESCRIPTION
> >             "The management address list for this 
> Interconnect Element.
> >             This object points to an entry in the
> >             t11FcsMgmtAddrListTable."
> > 
> >   Reading the DESCRIPTIOn clause, I wonder why one would not use a 
> >   RowPointer. The fact is that the pointer does not point 
> to "an entry"
> >   in the t11FcsMgmtAddrListTable, but to a SET of such entries.
> >   So I guess the DESCRIPTION clause could be clarified.
> 
> It is sufficient (and simpler) for this TC to be an 
> Unsigned32, whereas RowPointer is an OID.
>  
That is true and so I undestand somewhat why you want to do this.

> As a clarification, I've added this sentence to 
> T11ListIndexPointerOrZero's
> DESCRIPTION:
> 
>               Note that such a table could have one row per list, or
>               it could have one row per element of a list.
>  

Thanks

> > - I see:
> >  
> >   t11FcsIeInfoList  OBJECT-TYPE
> >     SYNTAX       OCTET STRING (SIZE (0..252))
> >     MAX-ACCESS   read-only
> >     STATUS       current
> >     DESCRIPTION
> >             "The information list for this Interconnect Element.
> >             This object contains the following substrings in order:
> >             vendor name, model name/number and release code/level,
> >             followed by zero or more substrings of vendor-specific
> >             information. Each substring is terminated with a byte
> >             containing a null value (x'00')."
> > 
> >   And that reads as if it is ASCII information to be (potentially) 
> >   consumed by human beings.  So in that case, the IETF wants it to
> >   be an internationalized string.  Comment?
>  
> FC-GS-5 requires the individual values to be ASCII strings (terminated
> by nulls).  I'll edit the DESCRIPTION to be:
> 
>             The value of this object is formatted as specified in
>             FC-GS-5, i.e., it contains the following substrings in
>             order:  vendor name, model name/number and release
>             code/level, followed by zero or more substrings of
>             vendor-specific information. Each substring is terminated
>             with a byte containing a null value (x'00')."
> 

I think it is indeed good to add that explanation.
Wonder how IESG will react to the ASCII for human-consumption.

Does T11 not worry about international (non-ASCII based)  people?

> > - I see:
> > 
> >   t11FcsMgmtAddr  OBJECT-TYPE
> >     SYNTAX       SnmpAdminString
> >     MAX-ACCESS   read-only
> >     STATUS       current
> >     DESCRIPTION
> >             "The management address of this entry.
> >             The format of this object may be based on the
> >             format of the Uniform Resource Locator (URL).
> >             For example, for SNMP, see RFC 4088."
> > 
> >   So it syas "the format MAY be based on..." (my emphasis on MAY).
> >   So, does that mean it may also be based on something else?
> >   How do I determine what the actual format is?
>  
> On re-reading FC-GS-5, I see that it's required to be a URL, and
> it's the use of 4088 which is not required.  So, I'll change it to:
> 
>             The format of this object is a Uniform Resource Locator
>             (URL), e.g., for SNMP, see RFC 4088."
> 

But is a URL normally represented by UTF-8?
I doubt it?

I know that (RFC 2788) has:

  -- Uniform Resource Locators are stored in URLStrings.

  URLString ::= TEXTUAL-CONVENTION
      DISPLAY-HINT "255a"
      STATUS current
      DESCRIPTION
          "A Uniform Resource Locator represented in accordance
           with RFCs 1738 and 2368, presented in the NVT ASCII
           charset defined in RFC 854."
      SYNTAX OCTET STRING (SIZE (0..255))

Would that not be more appropriate?

There is currently a discussion going on w.r.t. URL TC on SIP 
list and some MIB doctors (like Juergen and Dan) are also involved.

> > - SMICng gave a warning about the indexing of
> > 
> >   t11FcsPortListEntry  OBJECT-TYPE
> >     SYNTAX       T11FcsPortListEntry
> >     MAX-ACCESS   not-accessible
> >     STATUS       current
> >     DESCRIPTION
> >             "An entry which identifies that the port which has the
> >             port name, t11FcsPortName, is in a particular list of
> >             ports, which is known to a switch (identified by
> >             fcmInstanceIndex and fcmSwitchIndex)."
> >     INDEX   { fcmInstanceIndex,  fcmSwitchIndex,
> >               t11FcsPortListIndex, t11FcsPortName }
> >     ::= { t11FcsPortListTable 1 }
> > 
> >   I read Keiths explanation, which seemed fine. But now that I am
> >   reviewing the MIB module in details and try to understand things,
> >   now I am no so sure this is goodness.
> > 
> >   So, that t11FcsPortname is a value (embedded in the index) that
> >   should help me find more detailed info, right?
> >   So how do I find that info? I think I need to go to the
> >   t11FcsPortTable, which is indexed by:
> > 
> >     INDEX   { fcmInstanceIndex, fcmSwitchIndex,
> >               t11FcsFabricIndex, t11FcsPortName }
> > 
> >   So assuming that the index values for fcmInstanceIndex, 
> fcmSwitchIndex,
> >   are the same in both tables, I can see that I can pick up 3 index
> >   values from the list of t11FcsPortsList in the 
> t11FcsPortsListTable.
> >   But I am missing the 3rd index of the t11FcsPortnameTable, namely
> >   t11FcsFabricIndex. So how am I going to wuickly pick that up?
> >   Or how exactly are the tables connected/linked?
> > 
> >   Maybe I need to study it deeper... but I'd prefer an 
> explanation of
> >   the people who created these tables with the current 
> indexing schemes.
>  
> To generate an answer to your question, I needed to re-review the
> structure of the tables, and in doing so, I now think that the current
> structure is more open-ended/flexible than it needs to be -- having a
> less open-ended structure would make the MIB simpler.  Specifically,
> the MIB currently has a table whose only purpose is to identify a list
> of (not necessarily related) ports.  However,
> 
> - each IE is either a virtual IE attached to one virtual Fabric, or
>   (if virtual Fabrics are not in use) it's a physical IE.
> - each port is either a virtual port attached to one virtual 
> Fabric, or
>   (if virtual Fabrics are not in use) it's a physical port.
> - GS-5 mentions that an IE has a "port list" and has a dotted 
> line from the
>   "Interconnect Element Object" to the "Port Object" in its 
> "Figure 7 --
>   Interconnect Element and Port attributes".
> - However, all ports in an IE's port list will be attached to 
> the same 
>   Fabric as that IE is attached to.  In other words, the relationship
>   between IEs and ports is hierarchical.
> - Thus, it would be simpler to:
> 
>   - delete the t11FcsPortListTable,
>   - delete the t11FcsIePortListIndex object, and
>   - insert t11FcsIeName into the INDEX of the t11FcsPortTable, i.e.,
>     change the INDEX-ing of the t11FcsPortTable to be:
> 
>       INDEX   { fcmInstanceIndex, fcmSwitchIndex, t11FcsFabricIndex,
>                 t11FcsIeName, t11FcsPortName }
> 
> Increasing the INDEX clause from four to five objects makes 
> it a little
> more cumbersome, but the length is still far short of the 
> maximum length.
> 
> With these changes, while there will no longer be any explicit mention
> of a "port list" in the MIB, the list of ports on an IE will be all
> the rows in t11FcsPortTable which have the same values for the first
> four index objects, i.e., the value of t11FcsPortName will be the only
> index value for which they differ.  So, a "port list" is (implicitly)
> a set of adjacent rows in the t11FcsPortTable.
> 
> David, since this is a MIB design change, may I suggest you ask the WG
> for approval of this as a separate/individual question.
> 

Good to read your re-review and conclusion that things can be
organized more hierarchically and simpler.

The Warning about "inconsistent indexing" (or whatever the exact warning was)
from SMICng is one that I always take with a grain of salt, but it has turned
out that it is always good to check and make sure that the indexing scheme
that one has developed is indeed the best that we can do.

Thanks
> > - for
> >  
> >   t11FcsPortName  OBJECT-TYPE
> >     SYNTAX       FcNameIdOrZero
> >     MAX-ACCESS   not-accessible
> >     STATUS       current
> >     DESCRIPTION
> >             "The Port_Name (WWN) of the port for which this row
> >             contains information."
> > 
> >   I wonder if a zero value (zero length OCTET STRING) is 
> really valid?
> >   If not, then we may need to limit it with a SIZE paramter aka
> >     SYNTAX       FcNameIdOrZero SIZE (8 | 16)
> > 
> >   But,  I do see that in sect "6.2.3.3.1 Port Name" of document
> >   http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf, it says:
> > 
> >       The null value for the Port Name attribute is
> >       00 00 00 00 00 00 00 00h.
> > 
> >   So... is the SYNTAX of FcNameIdOrZero appropriate here? 
> >   In any event, the name SIZE seems to be fixed at 8 octets for the
> >   PortName, so at least one would then define the syntax as:
> > 
> >     SYNTAX       FcNameIdOrZero (SIZE (8))
>  
> A length of 16 is still a possibility -- section 6.2.3.3.1 refers to
> FC-FS, in which section 15 (table 66) includes one format which has a
> length of 128 (bits).
> 
> So, I'll chaneg it to:
>  
>       SYNTAX       FcNameIdOrZero (SIZE(8 | 16))
> 
OK, thanks

> > - For:
> > 
> >   t11FcsPortModuleType  OBJECT-TYPE
> >     SYNTAX       Unsigned32 (0..255)
> >     MAX-ACCESS   read-only
> >     STATUS       current
> >     DESCRIPTION
> >             "The port module type of this port."
> >     REFERENCE
> >             "ANSI INCITS xxx-200x, Fibre Channel - Generic 
> Services 5,
> >             FC-GS-5 T11/Project 1677-D/Rev 8, section 6.2.3.3.4."
> > 
> >   It seems better to create a TC that ENUMerates the valid values?
> 
> The choice between using either an enumerated value, or, a numeric
> value to be looked up in another specification, is a trade-off of
> convenience versus maintenance.  For something which changes
> frequently, it's better that the MIB *not* contain a list which is
> frequently out-of-date; for something which changes infrequently, it's
> better to have the convenience of enumeration.
>  
> Specifically, for those objects defined in this MIB as enumerations,
> when a new value is defined in T11, the new value cannot be 
> used in the
> MIB until the MIB is updated.  When the MIB syntax is Unsigned32,
> new values can be used in the MIB as soon as they are defined by T11.
> 
> So, we intentionally chose to specify some objects in this MIB as
> enumerations, and others as binary values, based on the frequency at
> which new values can be expected to be defined and used -- not just in
> the now completed GS-5, but also in GS-6 and its successors.
> 

OK, I can accept that. AS long as we know why we do things, I am fine.
Another way to address the "is updated often" is of course to make it
an external TC (in a separate module, possibly maintained by IANA or
some registration authority). Up to the WG as to what they want to do.

> > - For:
> > 
> >   t11FcsPortSpeedCapab  OBJECT-TYPE
> >     SYNTAX       OCTET STRING (SIZE (2))
> > 
> >   It seems that the references document and section say 
> that it is a BITS
> >   construct ??
> > 
> > - Same for t11FcsPortOperSpeed
>  
> While the Capability could be a BITS, OperSpeed would only 
> ever have one
> bit set, i.e., not a BITS.  However, both of these are 
> further examples of
> the enumerated versus numeric trade-off mentioned above.  
> That is, port
> speed is another area where new enumerations can be expected and will
> need to be used.
> 

Same response as above for the enumeration

> > - For:
> > 
> >   t11FcsPlatformName  OBJECT-TYPE
> >     SYNTAX       OCTET STRING (SIZE (0..255))
> > 
> >   It seems to me that the SYNTAX better be:
> > 
> >     SYNTAX       OCTET STRING (SIZE (0 | 3..256))
> > 
> >   because http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf
> >   section 6.2.3.4.2 tells me:
> > 
> >     The Platform Name attribute may be registered using the
> >     protocol described in 6.2.2.3. The null value for the
> >     Platform Name attribute is a zero-length Platform Name.
> > 
> >   So maybe that is how we can get a length of zero. But I am
> >   not even sure about that. It is also possible that the
> >   first byte would be valued at zero. Is the format octet 
> >   included in this case? Not clear from the PDF file for me.
> > 
> >   If I understand the PDF file correctly, then (it speaks about
> >   reserved to be of length 254-m) then there are 2 octets (1 for
> >   length, one for format) plus 254 for the actual name. So that
> >   would be a max size of 256 in my view.
>  
> Many of the format specifications in the GS-5 spec. are like this:
> 
>               Logical Name length (m)     1
>               Logical Name                m
>               Reserved                  255-m
> 
> where the aggregate length (of the three sub-fields) is 256 bytes.
> 
> So, the way that I interpret the Platform Name field:
> 
>               Platform Name length (m)     1
>               Platform Name                m
>               Platform Name Format         1
>               Reserved                   254-m
> 
> is similarly, to have an aggregate length is 256 bytes.  
> Therefore, the
> correct MIB syntax is:
> 
>      SYNTAX       OCTET STRING (SIZE (0..254))
> 
> where the range is the value of m.
> 

So you will not include the "Format" octet?
So how is an NMS supposed to figure out the format?


> > - Several objects in the t11FcsPlatformTable
> >   (like t11FcsPlatformVendorId, t11FcsPlatformProductId , etc)
> >   suggest (based on the SYNTAX of SnmpAdminString) that the value
> >   can be an internationalized human readable string.
> >   But the table 121 in the PDF file, section 6.2.3.4.5 seems to
> >   tell me that they are all ASCII. So what is it?
> 
> It's the format as specified in section 6.2.3.4.5, which is a
> subset of SnmpAdminString, which I believe means that using
> SnmpAdminString as the syntax is fine.
> 

I understand that ASCII does indeed fit into an SnmpAdminString.
So there is no SYNTAX error from that point of view.
It is just that (at least I, but I expect others as well) when
I see SnmpAdminString I think "human readable internationalized UTF-8"
So it sort of puts the reader/operator/apps-developer on the wrong
foot I think. More below..

> >   I know that IETF is not happy with using DisplayString, but if
> >   that is what the underlying technology (outside IETF) uses, then
> >   we should at least not suggest that it is different.
> >   I could accept that we say "we want to be prepared for UTF-8 
> >   strings, but for now it is ASCII as per DC-GS-5)". But it 
> >   might be good to then explicitly state so in the DESCRIPTION
> >   clauses of these objects.
> > 
> >   At the other hand, the objects are all read-only, and so even
> >   if they only present ASCII data (in UTF-8 that is exactly the
> >   same), then it would still be fine.
> 
> How about I leave it as SnmpAdminString, and point to GS-5 for
> the definition of which characters are valid:
> 
>             "The identifier of the vendor of this platform, in
>             the format specified by FC-GS-5."
> 

Works for me.
And if T11 then ever makes it internaionalized, it possibly still
works with this object.

> >   I also wonder if the length for t11FcsPlatformVendorId,
> >   t11FcsPlatformProductId can actually be zero, because table
> >   121 says that these are REQUIRED fields.
> 
> The table gives their minimum length when they are present, *but*
> a "Platform Attribute Block" doesn't necessarily contain them all.
>  

OK. I did not find that so quickly in the T11 spec. But I believe you
(i.e. I am too lazy to go check again).

> > - For:
> > 
> >   t11FcsPlatformFC4Types  OBJECT-TYPE
> >     SYNTAX       OCTET STRING (SIZE (0 | 32))
> > 
> >   should be 
> >     SYNTAX       OCTET STRING (SIZE (0 | 20))
> > 
> >   that is what I read in table 121 of
> >   http://www.t11.org/ftp/t11/pub/fc/gs-5/06-192v2.pdf
> 
> The text which follows the table says:
> 
>    Supported FC-4 Types: This is an 8 word (256 bit) bit mask that
>    indicates what FC-4 types are supported on this platform 
> (see 5.2.3.8).
>    FCP-2 (FC-4 type 08h) is represented by bit 8 of word 0. The Fabric
>    Configuration Server shall not attempt validation of the FC-4 Types
>    attribute, and any value shall be accepted for this attribute.
> 
> I think the table has a typo.
> 
I see. So someone will pick up the typo-problem with T11 I assume?


> > - Object t11FcsNodeName. Is it supposed to represent this:
> > 
> >   6.2.3.4.6 Platform Node Name
> >      The format of the Platform Node Name attribute, as used by
> >      the Fabric Configuration Server, shall be identical to the
> >      Name_Identifier format defined in FC-FS. Zero or more
> >      Platform Node Name attributes may be associated with a 
> >      Platform object. Node Names are registered to associate
> >      a Platform with the Nodes.
> >      This attribute may be registered using the protocol described
> >      in 6.2.2.3. The null value for the platform Node Name
> >      attribute is 00 00 00 00 00 00 00 00h
> > 
> >   That last description of 8 hex zeroes for a null value seems
> >   to conflict with the underlying 
> > 
> >     SYNTAX       FcNameIdOrZero
> > 
> >   that you are using in the MIB.
>  
> Ok, I'll change it to:
>  
>       SYNTAX       FcNameIdOrZero (SIZE(8 | 16))
> 
Thanks

> > - W.r.t.
> >  
> >   t11FcsNotifyControlTable OBJECT-TYPE
> >     SYNTAX       SEQUENCE OF T11FcsNotifyControlEntry
> >     MAX-ACCESS   not-accessible
> >     STATUS       current
> >     DESCRIPTION
> >             "A table of control information for notifications
> >             generated due to Fabric Configuration Server events.
> > 
> >             Values written to objects in this table should be
> >             persistent/retained over agent reboots."
> > 
> >   I have the same questions/concerns about the "should be 
> persistent"
> >   as I had for the RSCN MIB module. 
> >   So we can probably resolve this one in the same way (or leave it
> >   if everyone thinks that I worry too much).
>  
> OK.
> 

So what was the solution? Leave it as is and conclude that I worry 
too much? This is what you and I discussed about this:

> > > Bert:
> > >   Do we all think that "should be retained over agent reboots" is
> > >   good (and deterministic) enough? It is a lowercase should, and so 
> > >   any implementation that does not keep this over a reboot seems
> > >   still compliant. In other words, I have no deterministic way
> > >   at an NMS to figure out if this is persistent or not.
> >  
> > Keith:
> > Some systems store this type of information in an ASCII-formatted
> > "configuration file" which they keep in non-volatile memory, but also
> > have the capability for the file to be reloaded at boot time.  One of
> > the reasons why such configuration files have typically (until recently)
> > been formatted in ASCII is so that they can be edited by an administrator
> > to change the parameters prior to the device dowloading it (but
> > presumably, the same can now be done with XML-formatted files and
> > XML-based editors.)  In such a situation, you are correct that there is
> > no deterministic way for the agent to tell an NMS whether the 
> > parameter was persistent.
> > 
> 
> Bert:
> Mmm.. I had not even considered that. That is, that the "persistent info"
> can manually (or possibly by some other means, like CLI, NETCONF,
> what have you) be changed. I guess such is always the case, in that
> if we declare (in a MIB module) that data MUST be persistent/nonVolatile,
> that some admin can come in and whipe out (or change) the file 
> (or nonVolatile memory) that contains the "persistent data" 
> and it is gone. This is true for all MIB modules we have defined, 
> even for those that have a StorageType object inclued in a row.
> 
> What I had in mind was, that an implementation can decide to NOT save any
> data (that has been changed via an SNMP-SET) in non-volatile memory. 
> The desription clause does leave that open to any implementer.
> 
> I know this same sort of discussion has happened in other WGs.
> And I would rather see a "must" than a "should" in the text.
> But I am not gonna loose sleep if you keep it as is.
> 

So I still won't loose sleep over it... 
Yet I would still prefer "must". 
Just me I guess.

> > - It might be good to rename the notifications (for example)
> > 
> >     t11FcsReqRejectNotify NOTIFICATION-TYPE
> > 
> >   from xxxxNotify to xxxxNotification.
> 
> I chose to use t11FcsReqRejectNotify because 
> t11FcsReqRejectNotification
> is 33 characters long, and I think using t11FcsReqRejectNotify is a
> clearer abbreviation than t11FcsReqRejNotification.
> I guess I could go for:
> 
>      t11FcsRqRejectNotification NOTIFICATION-TYPE
> 
> if you prefer.
> 

I guess ity is a subjective matter of taste.
I personally don't worry about the 32-character length limit that we
used in the old (many tyears ago) days.


> >   But I agree that this is really nitpicking. 
> >   For consistency with (most) other MOB modules and notifications

I meant MIB, not MOB of course ;-)

> >   I think my argument makes sense though.
> > 
> > - For the notifications (and the control there-of), it again seems
> >   that the Transport Area may want us to say somehting about the
> >   max number of nitifications to be expected per second/minute/xxx
> >   or to provide a control varianle that a NMS can SET.
>  
> Their motivation is good, and is applicable to data-plane events, but
> asking for a max number per unit time for every type of notification
> is too simplistic.  E.g., it's unreasonable to ask how many
> t11FcsDiscoveryCompleteNotify notifications can be generated in a
> second/minute/xxx -- how big is the network, how many virtual fabrics
> need to be discovered, how quickly can the operator ask for another
> discovery after the last one completes ??
> 
> If a max rate is specified by an NMS, such that notifications can be
> suppressed due to their volume, then there needs to be some mechanism
> for the NMS to know that suppression(s) have happened/are happening,
> which means more notification-types and objects need to be defined.
> That is, it increases the complexity, which is not warranted unless
> there can really be a "flood" of notifications.
> 
> For notifications, like all the ones in this MIB, which are generated
> due to control plane events (and providing that none of them are able
> to start a chain-reaction), the extra complexity is not warranted.
> 

OK, I can buy that argument.
If I were Transport AD, I would then ask for a paragraph or two that
explains why this is not an issue for this MIB module.
See, that explains it to everyone, and at the same time shows that
indeed the WG considered it and consciously decided that such is not
needed. 
Oh well.... I guess now I sound too much as if I were still an AD
Sorry about that ;-)

Bert

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



From imss-bounces@ietf.org Thu Sep 07 12:10:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLMRv-0005J3-P2; Thu, 07 Sep 2006 12:09:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLMNa-0004RK-VC
	for imss@ietf.org; Thu, 07 Sep 2006 12:05:26 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLMAG-0001U6-8p
	for imss@ietf.org; Thu, 07 Sep 2006 11:51:41 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k87Fol7o026280;
	Thu, 7 Sep 2006 10:50:48 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK0B4X>; Thu, 7 Sep 2006 17:50:47 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96D51@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Black_David@emc.com, imss@ietf.org
Date: Thu, 7 Sep 2006 17:50:44 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: dromasca@avaya.com
Subject: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
	draft-ietf-imss-f c-zs-mib-00.txt
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

T11-FC-FABRIC-LOCK-MIB review

--------- questions/comments

- DESSCIPTION clause of t11FLockApplicationID says:
           The value assigned to identify the 'application' for a
           lock established via Acquire Change Authorization (ACA)
           request is: 'D0'h (208 decimal).  This value will be
           documented in a future revision of the FC-SW-nn
           specification."

   Do we have any idea as to "when such future FC-SW-nn will show
   up ?? If not, is this acceptable?

- For t11FLockInitiator, in the case the SNMP, would it not be 
  wise/usefull to add the snmpSecuityName?

- Reading:

   t11FLockRowStatus OBJECT-TYPE
      SYNTAX        RowStatus
      MAX-ACCESS    read-create
      STATUS        current
      DESCRIPTION
           "The status of this conceptual row.

           A row for which the value of t11FLockInitiatorType is
           not 'snmp' cannot be deleted via this object."

  I wonder:
  - can a row be set to notReady or notInservice for rows that
    were not created by 'snmp'? I guess not, but one could get
    the impression that such is possible based on this one 
    sentence
  - What is the persistence behaviour of a row created via snmp?
    Probably nonVolatile? But would be good to say something
    about it.

- SO I see:

    t11FLockStatus OBJECT-TYPE
        SYNTAX        INTEGER {
                      active(1),
                      settingUp(2),
                      rejectFailure(3),
                      otherFailure(4)
                  }

  and wonder what will happen if the lock gets released?
  not sure I understand how such happens, but I would assume a lock does
  not stay forever once it has become active, does it?
  Does the entry disappear in that case? 


--------- NITS

- in t11FLockEntry DESCRIPTION clause I read 4th para:

          Recently, a distinct value of Application_ID has also been
          assigned/reserved as a means of distinguishing locks
          established via Acquire Change Authorization (ACA)
          requests.  With this recent assignment, an Application_ID

  I think I would remove "Recently" and "recent".
  This document is intended for a reasonably long lifespan in the
  future, no?

- REFERENCE clauses of course need to be updated.

- for t11FLockActiveGroup, the deascription clause does not say that
  (if write/create-mode is supported) that a lock can also be
  established.

Bert

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



From imss-bounces@ietf.org Thu Sep 07 16:27:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLQTK-0005oD-19; Thu, 07 Sep 2006 16:27:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLQTJ-0005mO-4X
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:37 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLQTI-0004gr-PC
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:37 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k87KQMVm009244;
	Thu, 7 Sep 2006 15:26:23 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK01X8>; Thu, 7 Sep 2006 22:26:22 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96D68@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "David T. Perkins" <dperkins@dsperkins.com>
Date: Thu, 7 Sep 2006 22:26:14 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: imss@ietf.org, Black_David@emc.com
Subject: [imss] RE: [MIB-DOCTORS] WG last call review:
	T11-FC-FABRIC-LOCK-MIB in draft-ietf-imss-f c-zs-mib-00.txt
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

Thanks for your follow up/reaction Dave.

See my response inline

> -----Original Message-----
> From: David T. Perkins [mailto:dperkins@dsperkins.com]
> Sent: Thursday, September 07, 2006 21:00
> To: Wijnen, Bert (Bert)
> Cc: Black_David@emc.com; imss@ietf.org
> Subject: Re: [MIB-DOCTORS] WG last call review: T11-FC-FABRIC-LOCK-MIB
> in draft-ietf-imss-f c-zs-mib-00.txt
> 
> 
> HI,
> 
> For your generic question "can a row be set to notReady or 
> notInservice for rows that were not created by 'snmp'?"
> I disagree with your response of "I guess not".
> 

Aha... it was a guess. I was not sure. 
What I wanted to trigegr is that it gets documented.

Your writeup of scenarios below helps the WG (I hope) to
figure out what it wants and then to document that.

more below

> The generic answer is always "it depends". 
> 
> Note that I'm biased againest supporting "notReady" and "notInService"
> because they add much complexity to the implementation of agent
> access routines, and believe that well designed MIB modules can
> live without them (and createAndWait).
> 

I certainly agree with the "try to NOT REQUIRE createAndWait" support.
But this WG (and the main author(s)) of the WG MIB documents seem to
think it is fine cause they never make that optional via an OBJECT
clause in the MODULE-COMPLIANCE. So I would prefer they would do so,
but I dont; think that we (as MIB doctors or MIB reviewers can 
tell them taht they MUST follow our (subjective) opreferences.

But maybe this discussion between you and me helps some revisit
this topic. Anyway, at WG Last Call, this is probably not the 
best moment to bring this up or at least not to DEMAND change.

> But back to your question...
> Consider the following scenario:
> 1) rows created via SNMP in table A
> 2) configuration saved
> 3) system rebooted
> 4) on startup the system reads saved configuration
>    and "applies" it, which result in rows created in table A
> 5) an SNMP set creates additional rows in table A
> 6) CLI commands are executed that creates additional rows in table A
> 7) operation of the managed subsystem creates rows in table A
> 
> Are the rows created by system startup "different" than rows
> create by other means? 
> First, I believe that there are two classes of rows:
>  1) those created during operation of the managed subsystem
>  2) those created by management action
> And for both, there may be semantics that control the deletion
> of the rows and the persistence of the rows. Note that I'm
> also biased againest use of the StorageType TC, since many
> systems don't support saving individual instances of configuration.
> Configuration persistance is all or nothing, and config
> can be saved to specific targets (which is not directly supported
> by the StorageType TC (note: I hear the "but contexts can be
> used to specify different targets" song in the background
> (which is a dream))).
> 
> So the "depends" to me means that the MIB module designer
> must specify the semantics to say exactly what should be
> supported.
> 

Above is for the WG to discuss and decide I think.

> On other questions, see inline...
> 
> On Thu, 7 Sep 2006, Wijnen, Bert (Bert) wrote:
> > T11-FC-FABRIC-LOCK-MIB review
> > 
> > --------- questions/comments
> > 
> > - DESSCIPTION clause of t11FLockApplicationID says:
> >            The value assigned to identify the 'application' for a
> >            lock established via Acquire Change Authorization (ACA)
> >            request is: 'D0'h (208 decimal).  This value will be
> >            documented in a future revision of the FC-SW-nn
> >            specification."
> > 
> >    Do we have any idea as to "when such future FC-SW-nn will show
> >    up ?? If not, is this acceptable?
> > 
> > - For t11FLockInitiator, in the case the SNMP, would it not be 
> >   wise/usefull to add the snmpSecuityName?
> Don't know that complete context of this. Please note that
> there is a broken design pattern used in several of the DISMAN
> MIB modules that save the snmpSecuityName in a "secret" location.
> This presents problems, so don't do that. If you are to
> save an Initiator name, make sure it is accessible, and
> that the process works if the initiation is done via other
> management interfaces, sich as the CLI, WEB interface, or
> a specific protocol. 
> 

I was bringing up the question. 
It may help figure out who tried to lock.
And in case multiple operators are at the same NMS, maybe if "bert"
creates a lock, maybe he does not want "perkins" to release it????
Just thinking aloud here.

For me, such does not need to be a secret. Just normal access
control.

Bert
> > - Reading:
> > 
> >    t11FLockRowStatus OBJECT-TYPE
> >       SYNTAX        RowStatus
> >       MAX-ACCESS    read-create
> >       STATUS        current
> >       DESCRIPTION
> >            "The status of this conceptual row.
> > 
> >            A row for which the value of t11FLockInitiatorType is
> >            not 'snmp' cannot be deleted via this object."
> > 
> >   I wonder:
> >   - can a row be set to notReady or notInservice for rows that
> >     were not created by 'snmp'? I guess not, but one could get
> >     the impression that such is possible based on this one 
> >     sentence
> >   - What is the persistence behaviour of a row created via snmp?
> >     Probably nonVolatile? But would be good to say something
> >     about it.
> > 
> > - SO I see:
> > 
> >     t11FLockStatus OBJECT-TYPE
> >         SYNTAX        INTEGER {
> >                       active(1),
> >                       settingUp(2),
> >                       rejectFailure(3),
> >                       otherFailure(4)
> >                   }
> > 
> >   and wonder what will happen if the lock gets released?
> >   not sure I understand how such happens, but I would 
> assume a lock does
> >   not stay forever once it has become active, does it?
> >   Does the entry disappear in that case? 
> > 
> > 
> > --------- NITS
> > 
> > - in t11FLockEntry DESCRIPTION clause I read 4th para:
> > 
> >           Recently, a distinct value of Application_ID has also been
> >           assigned/reserved as a means of distinguishing locks
> >           established via Acquire Change Authorization (ACA)
> >           requests.  With this recent assignmFrom imss-bounces@ietf.org Thu Sep 07 16:27:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLQTK-0005oD-19; Thu, 07 Sep 2006 16:27:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLQTJ-0005mO-4X
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:37 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLQTI-0004gr-PC
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:37 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k87KQMVm009244;
	Thu, 7 Sep 2006 15:26:23 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK01X8>; Thu, 7 Sep 2006 22:26:22 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96D68@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "David T. Perkins" <dperkins@dsperkins.com>
Date: Thu, 7 Sep 2006 22:26:14 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: imss@ietf.org, Black_David@emc.com
Subject: [imss] RE: [MIB-DOCTORS] WG last call review:
	T11-FC-FABRIC-LOCK-MIB in draft-ietf-imss-f c-zs-mib-00.txt
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

Thanks for your follow up/reaction Dave.

See my response inline

> -----Original Message-----
> From: David T. Perkins [mailto:dperkins@dsperkins.com]
> Sent: Thursday, September 07, 2006 21:00
> To: Wijnen, Bert (Bert)
> Cc: Black_David@emc.com; imss@ietf.org
> Subject: Re: [MIB-DOCTORS] WG last call review: T11-FC-FABRIC-LOCK-MIB
> in draft-ietf-imss-f c-zs-mib-00.txt
> 
> 
> HI,
> 
> For your generic question "can a row be set to notReady or 
> notInservice for rows that were not created by 'snmp'?"
> I disagree with your response of "I guess not".
> 

Aha... it was a guess. I was not sure. 
What I wanted to trigegr is that it gets documented.

Your writeup of scenarios below helps the WG (I hope) to
figure out what it wants and then to document that.

more below

> The generic answer is always "it depends". 
> 
> Note that I'm biased againest supporting "notReady" and "notInService"
> because they add much complexity to the implementation of agent
> access routines, and believe that well designed MIB modules can
> live without them (and createAndWait).
> 

I certainly agree with the "try to NOT REQUIRE createAndWait" support.
But this WG (and the main author(s)) of the WG MIB documents seem to
think it is fine cause they never make that optional via an OBJECT
clause in the MODULE-COMPLIANCE. So I would prefer they would do so,
but I dont; think that we (as MIB doctors or MIB reviewers can 
tell them taht they MUST follow our (subjective) opreferences.

But maybe this discussion between you and me helps some revisit
this topic. Anyway, at WG Last Call, this is probably not the 
best moment to bring this up or at least not to DEMAND change.

> But back to your question...
> Consider the following scenario:
> 1) rows created via SNMP in table A
> 2) configuration saved
> 3) system rebooted
> 4) on startup the system reads saved configuration
>    and "applies" it, which result in rows created in table A
> 5) an SNMP set creates additional rows in table A
> 6) CLI commands are executed that creates additional rows in table A
> 7) operation of the managed subsystem creates rows in table A
> 
> Are the rows created by system startup "different, an Application_ID
> > 
> >   I think I would remove "Recently" and "recent".
> >   This document is intended for a reasonably long lifespan in the
> >   future, no?
> > 
> > - REFERENCE clauses of course need to be updated.
> > 
> > - for t11FLockActiveGroup, the deascription clause does not say that
> >   (if write/create-mode is supported) that a lock can also be
> >   established.
> > 
> > Bert
> Regards,
> /david t. perkins
> 

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

From imss-bounces@ietf.org Thu Sep 07 16:27:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLQTG-0005kR-Nf; Thu, 07 Sep 2006 16:27:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLQTF-0005k3-NG
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:33 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLQTE-0004gP-Cj
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:33 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k87KQMap009242;
	Thu, 7 Sep 2006 15:26:23 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK01X7>; Thu, 7 Sep 2006 22:26:22 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96D6A@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Black_David@emc.com, imss@ietf.org
Subject: RE: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in draft-i
	etf-imss-f c-zs-mib-00.txt
Date: Thu, 7 Sep 2006 22:26:15 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: 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

I also see another few NITs now that I am reviewing the 2nd 
MIB module in the same document.

- t11FLockRejectReasonCode OBJECT-TYPE
    SYNTAX        T11NsGs4RejectReasonCode
    MAX-ACCESS    read-only
    STATUS        current
    DESCRIPTION
           "When the value of the corresponding instance of
           t11FLockStatus is 'rejected', this object contains
           the rejection's reason code."

  Based on the ENUMerated values for t11FlockStatus, I 
  think we should change 'rejected' into 'rejectFailure'.

- same for t11FLockRejectReasonCodeExp
  and t11FLockRejectReasonVendorCode

- Now that I see t11ZsServerReasonCode, I wonder if the 2nd
  para in the DESCRIPTION clause would also make sense for
  the t11FLockRejectReasonCode object

- do the SIZE for t11ZsServerReasonCodeExp
  and t11ZsServerReasonVendorCode possibly also make sense for 
  t11FLockRejectReasonCodeExp, t11FLockRejectReasonVendorCode
  that is allowing for a SIZE of zero?


Bert

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Thursday, September 07, 2006 17:51
> To: Black_David@emc.com; imss@ietf.org
> Cc: dromasca@avaya.com
> Subject: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
> draft-ietf-imss-f c-zs-mib-00.txt
> 
> 
> T11-FC-FABRIC-LOCK-MIB review
> 
> --------- questions/comments
> 
> - DESSCIPTION clause of t11FLockApplicationID says:
>            The value assigned to identify the 'application' for a
>            lock established via Acquire Change Authorization (ACA)
>            request is: 'D0'h (208 decimal).  This value will be
>            documented in a future revision ent" than rows
> create by other means? 
> First, I believe that there are two classes of rows:
>  1) those created during operation of the managed subsystem
>  2) those created by management action
> And for both, there may be semantics that control the deletion
> of the rows and the persistence of the rows. Note that I'm
> also biased againest use of the StorageType TC, since many
> systems don't support saving individual instances of configuration.
> Configuration persistance is all or nothing, and config
> can be saved to specific targets (which is not directly supported
> by the StorageType TC (note: I hear the "but contexts can be
> used to specify different targets" song in the background
> (which is a dream))).
> 
> So the "depends" to me means that the MIB module designer
> must specify the semantics to say exactly what should be
> supported.
> 

Above is for the WG to discuss and decide I think.

> On other questions, see inline...
> 
> On Thu, 7 Sep 2006, Wijnen, Bert (Bert) wrote:
> > T11-FC-FABRIC-LOCK-MIB review
> > 
> > --------- questions/comments
> > 
> > - DESSCIPTION clause of t11FLockApplicationID says:
> >            The value assigned to identify the 'application' for a
> >            lock established via Acquire Change Authorization (ACA)
> >            request is: 'D0'h (208 decimal).  This value will be
> >            documented in a future revision of the FC-SW-nn
> >            specification."
> > 
> >    Do we have any idea as to "when such future FC-SW-nn will show
> >    up ?? If not, is this acceptable?
> > 
> > - For t11FLockInitiator, in the case the SNMP, would it not be 
> >   wise/usefull to add the snmpSecuityName?
> Don't know that complete context of this. Please note that
> there is a broken design pattern used in several of the DISMAN
> MIB modules that save the snmpSecuityName in a "secret" location.
> This presents problems, so don't do that. If you are to
> save an Initiator name, make sure it is accessible, and
> that the process works if the initiation is done via other
> management interfaces, sich as the CLI, WEB interface, or
> a specific protocol. 
> 

I was bringing up the question. 
It may help figure out who tried to lock.
And in case multiple operators are at the same NMS, maybe if "bert"
creates a lock, maybe he does not want "perkins" to release it????
Just thinking aloud here.

For me, such does not need to be a secret. Just normal access
control.

Bert
> > - Reading:
> > 
> >    t11FLockRowStatus OBJECT-TYPE
> >       SYNTAX        RowStatus
> >       MAX-ACCESS    read-create
> >       STATUS        current
> >       DESCRIPTION
> >            "The status of this conceptual row.
> > 
> >            A row for which the value of t11FLockInitiatorType is
> >            not 'snmp' cannot be deleted via this object."
> > 
> >   I wonder:
> >   - can a row be set to notReady or notInservice for rows that
> >     were not created by 'snmp'? I guess not, but one could get
> >     the impression that such is possible based on this one 
> >     sentence
> >   - What is the persistence behaviour of a row created via snmp?
> >     Probably nonVolatile? But would be good to say something
> >     about it.
> > 
> > - SO I see:
> > 
> >     t11FLockStatus OBJECT-TYPE
> >         SYNTAX        INTEGER {
> >                       active(1),
> >                       settingUp(2),
> >                       rejectFailure(3),
> >                       otherFailure(4)
> >                   }
> > 
> >   and wonder what will happen if the lock gets released?
> >   not sure I understand how such happens, but I would 
> assume a lock does
> >   not stay forever once it has become active, does it?
> >   Does the entry disappear in that case? 
> > 
> > 
> > --------- NITS
> > 
> > - in t11FLockEntry DESCRIPTION clause I read 4th para:
> > 
> >           Recently, a distinct value of Application_ID has also been
> >           assigned/reserved as a means of distinguishing locks
> >           established via Acquire Change Authorization (ACA)
> >           requests.  With this recent assignmof the FC-SW-nn
>            specification."
> 
>    Do we have any idea as to "when such future FC-SW-nn will show
>    up ?? If not, is this acceptable?
> 
> - For t11FLockInitiator, in the case the SNMP, would it not be 
>   wise/usefull to add the snmpSecuityName?
> 
> - Reading:
> 
>    t11FLockRowStatus OBJECT-TYPE
>       SYNTAX        RowStatus
>       MAX-ACCESS    read-create
>       STATUS        current
>       DESCRIPTION
>            "The status of this conceptual row.
> 
>            A row for which the value of t11FLockInitiatorType is
>            not 'snmp' cannot be deleted via this object."
> 
>   I wonder:
>   - can a row be set to notReady or notInservice for rows that
>     were not created by 'snmp'? I guess not, but one could get
>     the impression that such is possible based on this one 
>     sentence
>   - What is the persistence behaviour of a row created via snmp?
>     Probably nonVolatile? But would be good to say something
>     about it.
> 
> - SO I see:
> 
>     t11FLockStatus OBJECT-TYPE
>         SYNTAX        INTEGER {
>                       active(1),
>                       settingUp(2),
>                       rejectFailure(3),
>                       otherFailure(4)
>                   }
> 
>   and wonder what will happen if the lock gets released?
>   not sure I understand how such happens, but I would assume 
> a lock does
>   not stay forever once it has become active, does it?
>   Does the entry disappear in that case? 
> 
> 
> --------- NITS
> 
> - in t11FLockEntry DESCRIPTION clause I read 4th para:
> 
>           Recently, a distinct value of Application_ID has also been
>           assigned/reserved as a means of distinguishing locks
>           established via Acquire Change Authorization (ACA)
>           requests.  With this recent assignment, an Application_ID
> 
>   I think I would remove "Recently" and "recent".
>   This document is intended for a reasonably long lifespan in the
>   future, no?
> 
> - REFERENCE clauses of course need to be updated.
> 
> - for t11FLockActiveGroup, the deascription clause does not say that
>   (if write/create-mode is supported) that a lock can also be
>   established.
> 
> Bert
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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





ent, an Application_ID
> > 
> >   I think I would remove "Recently" and "recent".
> >   This document is intended for a reasonably long lifespan in the
> >   future, no?
> > 
> > - REFERENCE clauses of course need to be updated.
> > 
> > - for t11FLockActiveGroup, the deascription clause does not say that
> >   (if write/create-mode is supported) that a lock can also be
> >   established.
> > 
> > Bert
> Regards,
> /david t. perkins
> 

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

From imss-bounces@ietf.org Thu Sep 07 16:27:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLQTG-0005kR-Nf; Thu, 07 Sep 2006 16:27:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLQTF-0005k3-NG
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:33 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLQTE-0004gP-Cj
	for imss@ietf.org; Thu, 07 Sep 2006 16:27:33 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k87KQMap009242;
	Thu, 7 Sep 2006 15:26:23 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK01X7>; Thu, 7 Sep 2006 22:26:22 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96D6A@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Black_David@emc.com, imss@ietf.org
Subject: RE: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in draft-i
	etf-imss-f c-zs-mib-00.txt
Date: Thu, 7 Sep 2006 22:26:15 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: 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

I also see another few NITs now that I am reviewing the 2nd 
MIB module in the same document.

- t11FLockRejectReasonCode OBJECT-TYPE
    SYNTAX        T11NsGs4RejectReasonCode
    MAX-ACCESS    read-only
    STATUS        current
    DESCRIPTION
           "When the value of the corresponding instance of
           t11FLockStatus is 'rejected', this object contains
           the rejection's reason code."

  Based on the ENUMerated values for t11FlockStatus, I 
  think we should change 'rejected' into 'rejectFailure'.

- same for t11FLockRejectReasonCodeExp
  and t11FLockRejectReasonVendorCode

- Now that I see t11ZsServerReasonCode, I wonder if the 2nd
  para in the DESCRIPTION clause would also make sense for
  the t11FLockRejectReasonCode object

- do the SIZE for t11ZsServerReasonCodeExp
  and t11ZsServerReasonVendorCode possibly also make sense for 
  t11FLockRejectReasonCodeExp, t11FLockRejectReasonVendorCode
  that is allowing for a SIZE of zero?


Bert

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Thursday, September 07, 2006 17:51
> To: Black_David@emc.com; imss@ietf.org
> Cc: dromasca@avaya.com
> Subject: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
> draft-ietf-imss-f c-zs-mib-00.txt
> 
> 
> T11-FC-FABRIC-LOCK-MIB review
> 
> --------- questions/comments
> 
> - DESSCIPTION clause of t11FLockApplicationID says:
>            The value assigned to identify the 'application' for a
>            lock established via Acquire Change Authorization (ACA)
>            request is: 'D0'h (208 decimal).  This value will be
>            documented in a future revision of the FC-SW-nn
>            specification."
> 
>    Do we have any idea as to "when such future FC-SW-nn will show
>    up ?? If not, is this acceptable?
> 
> - For t11FLockInitiator, in the case the SNMP, would it not be 
>   wise/usefull to add the snmpSecuityName?
> 
> - Reading:
> 
>    t11FLockRowStatus OBJECT-TYPE
>       SYNTAX        RowStatus
>       MAX-ACCESS    read-create
>       STATUS        current
>       DESCRIPTION
>            "The status of this conceptual row.
> 
>            A row for which the value of t11FLockInitiatorType is
>            not 'snmp' cannot be deleted via this object."
> 
>   I wonder:
>   - can a row be set to notReady or notInservice for rows that
>     were not created by 'snmp'? I guess not, but one could get
>     the impression that such is possible based on this one 
>     sentence
>   - What is the persistence behaviour of a row created via snmp?
>     Probably nonVolatile? But would be good to say something
>     about it.
> 
> - SO I see:
> 
>     t11FLockStatus OBJECT-TYPE
>         SYNTAX        INTEGER {
>                       active(1),
>                       settingUp(2),
>                       rejectFailure(3),
>                       otherFailure(4)
>                   }
> 
>   and wonder what will happen if the lock gets released?
>   not sure I understand how such happens, but I would assume 
> a lock does
>   not stay forever once it has become active, does it?
>   Does the entry disappear in that case? 
> 
> 
> --------- NITS
> 
> - in t11FLockEntry DESCRIPTION clause I read 4th para:
> 
>           Recently, a distinct value of Application_ID has also been
>           assigned/reserved as a means of distinguishing locks
>           established via Acquire Change Authorization (ACA)
>           requests.  With this recent assignment, an Application_ID
> 
>   I think I would remove "Recently" and "recent".
>   This document is intended for a reasonably long lifespan in the
>   future, no?
> 
> - REFERENCE clauses of course need to be updated.
> 
> - for t11FLockActiveGroup, the deascription clause does not say that
>   (if write/create-mode is supported) that a lock can also be
>   established.
> 
> Bert
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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





From imss-bounces@ietf.org Thu Sep 07 17:18:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLRGC-0000Hp-Tr; Thu, 07 Sep 2006 17:18:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLRGB-0000Hh-Fx
	for imss@ietf.org; Thu, 07 Sep 2006 17:18:07 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLRGA-0008KR-1q
	for imss@ietf.org; Thu, 07 Sep 2006 17:18:07 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k87LHPSl010690;
	Thu, 7 Sep 2006 16:17:25 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK0FF4>; Thu, 7 Sep 2006 23:17:24 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96D70@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Black_David@emc.com, imss@ietf.org
Date: Thu, 7 Sep 2006 23:17:22 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1
Cc: dromasca@avaya.com
Subject: [imss] WG last call review: T11-FC-ZONE-SERVER-MIB in
	draft-ietf-imss-f c-zs-mib-00.txt
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

T11-FC-ZONE-SERVER-MIB

--------- questions/comments

- Would it be better to rename T11ZoningName to T11ZsZoningName?
  This for naming consistency and avoiding possible future name
  clashes.

- For t11ZsServerDistribute
          Setting this object will fail if the corresponding
          instance of t11ZsServerOperationMode has the value
          'enhanced', or if the corresponding instance of
          t11ZsZoneSetResult has the value 'inProgress'."
  
  will fail with what? I assume/think 'inconsistentValue'.
  Might be good to state so, to ensure proper implementation.

- Now that I see t11ZsServerReasonCode, I wonder if the 2nd
  para in the DESCRIPTION clause would also make sense for
  the t11FLockRejectReasonCode object

- do the SIZE for t11ZsServerReasonCodeExp
  and t11ZsServerReasonVendorCode possibly also make sense for 
  t11FLockRejectReasonCodeExp, t11FLockRejectReasonVendorCode
  that is allowing for a SIZE of zero?
 
- I wonder why this

    t11ZsServerDefaultZoneSetting OBJECT-TYPE
        SYNTAX       INTEGER {
                        permit(1),
                        deny(2)
                     }

  Is not done with a TruthValue possibly using a different
  descriptor.
  Not a fatal flaw though, but a missed opportunity for
  re-use in my view. Unless if one expects more values in
  the future.

  For t11ZsServerMergeControlSetting it is less obvious, but the
  same question could be asked I guess.

- I see:
    t11ZsSetName OBJECT-TYPE
        SYNTAX       T11ZoningName
        MAX-ACCESS   read-create
        STATUS       current
        DESCRIPTION
           "The name of this Zone Set. The t11ZsSetName should
           be unique within a fabric.

           The Zone Set can be renamed by setting this object
           to a new value."

  and wonder if the rename can also be done while the row is in
  'active' state !!??

- I am not sure I understand this:

    t11ZsSetEntry  OBJECT-TYPE
        SYNTAX       T11ZsSetEntry
        MAX-ACCESS   not-accessible
        STATUS       current
        DESCRIPTION
           "Each entry contains information about a Zone Set
           in the Zone Set database of a particular fabric
           (identified by the value of t11ZsServerFabricIndex)
           on a particular switch (identified by values of
           fcmInstanceIndex and fcmSwitchIndex).

           A Zone Set is created containing zero or more
           existing Zones.  As and when new Zones are created
           (as rows in the t11ZsZoneTable), they can be added
           to a Zone Set by creating an entry for each in the
           t11ZsSetZoneTable.

           The StorageType of a row in this table is specified by
           the instance of t11ZsServerDatabaseStorageType which is
           INDEX-ed by the same values of fcmInstanceIndex,
           fcmSwitchIndex and t11ZsServerFabricIndex."
        INDEX   { fcmInstanceIndex, fcmSwitchIndex,
                  t11ZsServerFabricIndex, t11ZsSetIndex }
        ::= { t11ZsSetTable 1 }

  So it seems to me I can do SNMP SET to create an entry in this
  table. But is is not clear if, when I do so, and entry in the 
  t11ZsServerTable must already exist or not. Probably so,
  because it uses the actual (index) objects from that table.
  But in practice, can an SNMP utility not just create entries
  with index values that do not really exists in the base
  table? I'd like to know how the agent is supposed to react.

  So if the base table entrues must exist first,
  then it would be good to say so, i.e. spell it out.
  And to say what happens if it does not yet exist.
  If not, then I wonder how/when the entry in that t11ZsServerTable
  does get created, because otherwise it is unclear how/if/when
  the persistency works.
  
  And what when I delete the row? Does it have any effect on the
  associated rows in t11ZsServerTable. Possibly not. But I am
  not sure how I can determine that based on the current
  DESCRIPTION clauses.

- I have the same/similar question for t11ZsZoneEntry

- Can t11ZsZoneAttribBlock be changed while row is active?

  such questions can be asked for more read-write/read-create
  objects in this MIB module. I won't keep repeating.

- For t11ZsSetZoneEntry, it seems that the 3 other tables MUST
  have an existing associated entry(entries) before creating 
  an entry in this row makes sense. But maybe it is OK to 
  prepare this table before the other tables have been 
  completed/created?

- for t11ZsSetZoneRowStatus I wonder what happens if this
  one has a value of active, byt the rowstatus in some of
  the other (base) tables have a value of notInservice or
  notReady ??

  Are we all supposed to try and figure this out, or would it
  be better to put something about this in the various
  DESCRIPTION clauses?

- In fact the whole fate-sharing between all the tables may
  need to be described. I see some of it in section 5.5. and
  5.6 of the document, but also from that I do not yet see
  what the implications are if the rowstatus in one table is
  notInservice, while others are actve or  maybe notReady,
  or maybe do not (yet) exist.
  I must also admit that I have not studied the T11 documents 
  much (in fact very little) yet. But I'd hope that these
  basic question would be answered in the IETF MIB document
  itself.

- I see no persistency behaviour (or a link to the StorageType
  objects in the base table in t11ZsActivateTable.
  I think it is clear that the writable objects are all
  volatile (they seem to be control objects that cause an
  action when SET).

- For namingconsistency in:
    T11ZsActiveZoneEntry ::= SEQUENCE {
       t11ZsActiveZoneIndex      Unsigned32,
       t11ZsActiveZoneName       T11ZoningName,
       t11ZsActiveBroadcast      TruthValue,
       t11ZsActiveHardZoning     TruthValue
    }
  I would insert a "Zone" before "Broadcast" and before "Hardzoning"

  By the way, t11ZsActiveZoneSetName in the T11ZsActiveEntry might be
  (at first sight) perceived to be in the T11ZsActiveZoneEntry.
  I understand why it has that name, but it may consfuse some
  people.

- t11ZsActiveBroadcast and t11ZsActiveHardZoning both have in
  their DESCRIPTION clauses:
             This object is only instantiated in Enhanced mode."

  would we not want to specify that in a MODULE-COMPLIANCE for 
  basic mode and one for enhanced mode?



--------- NITS/TYPOs

- In one but last para of DESCRIPTION clause of MODULE-IDENTITY

     When this MIB is used for Basic Zoning Management, the same
     set of MIBs objects as used for Enhanced mode are used to

  s/MIBs objects/MIB objects/

- In t11ZsServerFabricIndex, the last 2 paragraphs of the
  DESCRIPTION clause seem redundant with the DESCRIPTION clause
  of the TC itself. I would remove them. The idea of a TC is
  to have one place (namely in the DESCRIPTION clause of the TC)
  to describe the (basic) semantics of the objects that use 
  the TC as a SYNTAX.

- t11ZsServerCapabilityObject
  I think I would rename zonesetDb(1) to zoneSetDb(1)
  but this is pretty subjective taste of course.

- last para of description clasue of t11ZsServerDatabaseStorageType

           This value of this object is a...

  s/This/The/ ??
  
- For t11ZsAttribType maybe add "other values reserved" in the 
  DESCRIPTION clause. I went looking it up, because in an 
  earlier object we had E0-EF as Vendor specific. So I thought
  that might also be the case here. But the text in the 
  REFERENCEd docment/section told me they are reserved.

- for
   t11ZsActivateRequest OBJECT-TYPE
     SYNTAX       Unsigned32 (0..4294967295)
     MAX-ACCESS   read-write
     STATUS       current
     DESCRIPTION
           "Setting this object to a value is a request for a
           Zone Set to be activated on the fabric which is
           represented by this row.  The Zone Set to be
           activated is the one for which t11ZsSetIndex has
           the same value.

           If a Zone Set is already active on a fabric when a
           request is made to activate a different one on that
           fabric, then the existing Zone Set is automatically
           deactivated and the specified Zone Set is activated
           in its place.

           The value of this object when read is always 0."

   It seems that setting the value to zero has no effect. Right?
   But zero seems to also have special meaning. Oh well. I might
   indicate it by using 
     SYNTAX       Unsigned32 (0 | 1..4294967295)
   but that is subjective taste I guess.

- similarly, for

    t11ZsFabricIndex OBJECT-TYPE
        SYNTAX       Unsigned32 (0..4096)

  I think I would use  

        SYNTAX       Unsigned32 (0..4095 | 4096)

  to indicate that 4096 has special meaning.

  Maybe I would even create a 

      T11FabricIndexOrAll ::= TEXTUAL-CONVENTION

  So it could if an "ALL" option is needed in the future that it is
  (or at least can be) done in a consistent maner.

- I personally prefer to name notifications xxxNotification instead
  of naming them xxxNotify. But I admit that that is subjective.


Bert

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



From imss-bounces@ietf.org Thu Sep 07 19:46:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLTa3-0007Ko-JD; Thu, 07 Sep 2006 19:46:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLPGf-0006gv-Ff
	for imss@ietf.org; Thu, 07 Sep 2006 15:10:29 -0400
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLP8M-0006lj-IQ
	for imss@ietf.org; Thu, 07 Sep 2006 15:01:55 -0400
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.13.6/8.13.6) with ESMTP id k87J0MY6017981;
	Thu, 7 Sep 2006 12:00:22 -0700
Received: from localhost (dperkins@localhost)
	by shell4.bayarea.net (8.13.6/8.12.11/Submit) with ESMTP id
	k87J0DwN017948; Thu, 7 Sep 2006 12:00:22 -0700
X-Authentication-Warning: shell4.bayarea.net: dperkins owned process doing -bs
Date: Thu, 7 Sep 2006 12:00:13 -0700 (PDT)
From: "David T. Perkins" <dperkins@dsperkins.com>
X-Sender: dperkins@shell4.bayarea.net
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B1550AA96D51@nl0006exch001u.nl.lucent.com>
Message-ID: <Pine.LNX.4.10.10609071127220.7428-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
X-Mailman-Approved-At: Thu, 07 Sep 2006 19:46:46 -0400
Cc: imss@ietf.org, Black_David@emc.com
Subject: [imss] Re: [MIB-DOCTORS] WG last call review:
 T11-FC-FABRIC-LOCK-MIB in draft-ietf-imss-f c-zs-mib-00.txt
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

HI,

For your generic question "can a row be set to notReady or notInservice
for rows that were not created by 'snmp'?"
I disagree with your response of "I guess not".

The generic answer is always "it depends". 

Note that I'm biased againest supporting "notReady" and "notInService"
because they add much complexity to the implementation of agent
access routines, and believe that well designed MIB modules can
live without them (and createAndWait).

But back to your question...
Consider the following scenario:
1) rows created via SNMP in table A
2) configuration saved
3) system rebooted
4) on startup the system reads saved configuration
   and "applies" it, which result in rows created in table A
5) an SNMP set creates additional rows in table A
6) CLI commands are executed that creates additional rows in table A
7) operation of the managed subsystem creates rows in table A

Are the rows created by system startup "different" than rows
create by other means? 
First, I believe that there are two classes of rows:
 1) those created during operation of the managed subsystem
 2) those created by management action
And for both, there may be semantics that control the deletion
of the rows and the persistence of the rows. Note that I'm
also biased againest use of the StorageType TC, since many
systems don't support saving individual instances of configuration.
Configuration persistance is all or nothing, and config
can be saved to specific targets (which is not directly supported
by the StorageType TC (note: I hear the "but contexts can be
used to specify different targets" song in the background
(which is a dream))).

So the "depends" to me means that the MIB module designer
must specify the semantics to say exactly what should be
supported.

On other questions, see inline...

On Thu, 7 Sep 2006, Wijnen, Bert (Bert) wrote:
> T11-FC-FABRIC-LOCK-MIB review
> 
> --------- questions/comments
> 
> - DESSCIPTION clause of t11FLockApplicationID says:
>            The value assigned to identify the 'application' for a
>            lock established via Acquire Change Authorization (ACA)
>            request is: 'D0'h (208 decimal).  This value will be
>            documented in a future revision of the FC-SW-nn
>            specification."
> 
>    Do we have any idea as to "when such future FC-SW-nn will show
>    up ?? If not, is this acceptable?
> 
> - For t11FLockInitiator, in the case the SNMP, would it not be 
>   wise/usefull to add the snmpSecuityName?
Don't know that complete context of this. Please note that
there is a broken design pattern used in several of the DISMAN
MIB modules that save the snmpSecuityName in a "secret" location.
This presents problems, so don't do that. If you are to
save an Initiator name, make sure it is accessible, and
that the process works if the initiation is done via other
management interfaces, sich as the CLI, WEB interface, or
a specific protocol. 

> - Reading:
> 
>    t11FLockRowStatus OBJECT-TYPE
>       SYNTAX        RowStatus
>       MAX-ACCESS    read-create
>       STATUS        current
>       DESCRIPTION
>            "The status of this conceptual row.
> 
>            A row for which the value of t11FLockInitiatorType is
>            not 'snmp' cannot be deleted via this object."
> 
>   I wonder:
>   - can a row be set to notReady or notInservice for rows that
>     were not created by 'snmp'? I guess not, but one could get
>     the impression that such is possible based on this one 
>     sentence
>   - What is the persistence behaviour of a row created via snmp?
>     Probably nonVolatile? But would be good to say something
>     about it.
> 
> - SO I see:
> 
>     t11FLockStatus OBJECT-TYPE
>         SYNTAX        INTEGER {
>                       active(1),
>                       settingUp(2),
>                       rejectFailure(3),
>                       otherFailure(4)
>                   }
> 
>   and wonder what will happen if the lock gets released?
>   not sure I understand how such happens, but I would assume a lock does
>   not stay forever once it has become active, does it?
>   Does the entry disappear in that case? 
> 
> 
> --------- NITS
> 
> - in t11FLockEntry DESCRIPTION clause I read 4th para:
> 
>           Recently, a distinct value of Application_ID has also been
>           assigned/reserved as a means of distinguishing locks
>           established via Acquire Change Authorization (ACA)
>           requests.  With this recent assignment, an Application_ID
> 
>   I think I would remove "Recently" and "recent".
>   This document is intended for a reasonably long lifespan in the
>   future, no?
> 
> - REFERENCE clauses of course need to be updated.
> 
> - for t11FLockActiveGroup, the deascription clause does not say that
>   (if write/create-mode is supported) that a lock can also be
>   established.
> 
> Bert
Regards,
/david t. perkins


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



From imss-bounces@ietf.org Fri Sep 08 11:43:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLiVJ-00038k-Fc; Fri, 08 Sep 2006 11:42:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLiVI-00038c-AY
	for imss@ietf.org; Fri, 08 Sep 2006 11:42:52 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLiVG-0008EM-P7
	for imss@ietf.org; Fri, 08 Sep 2006 11:42:52 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 08 Sep 2006 08:42:50 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k88Fgo4n031672; Fri, 8 Sep 2006 08:42:50 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k88FgnYp025153;
	Fri, 8 Sep 2006 08:42:49 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id IAA27259;
	Fri, 8 Sep 2006 08:41:45 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609081541.IAA27259@cisco.com>
Subject: Re: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
To: bwijnen@lucent.com
Date: Fri, 8 Sep 2006 08:41:45 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 07, 2006 05:50:44 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=4643; t=1157730170; x=1158594170;
	c=relaxed/simple; s=sjdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20WG=20last=20call=20review=3A=20T11-FC-FABRIC-LOCK-MIB=2
	0in; X=v=3Dcisco.com=3B=20h=3D4h7PwFWEwrnbGje6cEXeZKfSHs0=3D;
	b=pfVuDguAi2cjJttZyJmakoR3rizf9rWOAwA1aP4bBk+kt6VI4efxmcrCLz+cbBuN2cNDHflq
	q17F/X1rqUYORZIly+pzecBi0daiGGReBYPBhl2ySxroV/Z70Gk74bTN;
Authentication-Results: sj-dkim-1.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: imss@ietf.org, Black_David@emc.com, 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

> T11-FC-FABRIC-LOCK-MIB review
> 
> --------- questions/comments
> 
> - DESSCIPTION clause of t11FLockApplicationID says:
>            The value assigned to identify the 'application' for a
>            lock established via Acquire Change Authorization (ACA)
>            request is: 'D0'h (208 decimal).  This value will be
>            documented in a future revision of the FC-SW-nn
>            specification."
> 
>    Do we have any idea as to "when such future FC-SW-nn will show
>    up ?? If not, is this acceptable?
 
My understanding is that FC-SW-4 is closed, and it lists 'D0'h as one
of the reserved values.  The long-time editor of FC-SW-nn sent an email
message dated 8Aug06 to the T11.5 mailing-list with the assignment of
a range of values including 'D0'h for this purpose.  The assignment
will be documented in FC-SW-5 which is approved as a new project, but
there is no initial draft of it yet.

Would you like a formal liaison message from T11 to the IETF stating
what number has been assigned ??

> - For t11FLockInitiator, in the case the SNMP, would it not be 
>   wise/usefull to add the snmpSecuityName?
 
I suggest it should be possible to be a compliant implementation of this
MIB even for an SNMPv1/SNMPv2 implementation which doesn't support SNMPv3.
So, if we define an object to hold the value of snmpSecurityName, we
need to define what value that object will have in an agent which does
not implement the SNMP-COMMUNITY-MIB (in which snmpCommunitySecurityName
is defined).  What value would you propose ??

> - Reading:
> 
>    t11FLockRowStatus OBJECT-TYPE
>       SYNTAX        RowStatus
>       MAX-ACCESS    read-create
>       STATUS        current
>       DESCRIPTION
>            "The status of this conceptual row.
> 
>            A row for which the value of t11FLockInitiatorType is
>            not 'snmp' cannot be deleted via this object."
> 
>   I wonder:
>   - can a row be set to notReady or notInservice for rows that
>     were not created by 'snmp'? I guess not, but one could get
>     the impression that such is possible based on this one 
>     sentence

How about we change "be deleted" to "have its status changed" ??

>   - What is the persistence behaviour of a row created via snmp?
>     Probably nonVolatile? But would be good to say something
>     about it.
 
No, I think it should be volatile, because an agent restart is the
equivalent of the "various error situations" mentioned in the last
paragraph of t11FLockEntry's DESCRIPTION.  Yes, I'll add some text.

> - SO I see:
> 
>     t11FLockStatus OBJECT-TYPE
>         SYNTAX        INTEGER {
>                       active(1),
>                       settingUp(2),
>                       rejectFailure(3),
>                       otherFailure(4)
>                   }
> 
>   and wonder what will happen if the lock gets released?
>   not sure I understand how such happens, but I would assume a lock does
>   not stay forever once it has become active, does it?

No.  It gets released explicitly or implicitly (as mentioned above). 

>   Does the entry disappear in that case? 
 
Yes, because the table is defined as the list of all *current* locks.
 
> --------- NITS
> 
> - in t11FLockEntry DESCRIPTION clause I read 4th para:
> 
>           Recently, a distinct value of Application_ID has also been
>           assigned/reserved as a means of distinguishing locks
>           established via Acquire Change Authorization (ACA)
>           requests.  With this recent assignment, an Application_ID
> 
>   I think I would remove "Recently" and "recent".
>   This document is intended for a reasonably long lifespan in the
>   future, no?
 
OK, how about I can change it to:

          Not long before this MIB was defined, a distinct value of
          Application_ID was also assigned/reserved as the means to
          distinguish locks established via Acquire Change
	  Authorization (ACA) requests.  This additional assignment
	  allows an Application_ID to be used to uniquely identify a
	  lock amongst all active locks established either by an EACA
	  or by an ACA.

> - REFERENCE clauses of course need to be updated.
 
Right.

> - for t11FLockActiveGroup, the description clause does not say that
>   (if write/create-mode is supported) that a lock can also be
>   established.
 
I don't understand.  One of the objects in the t11FLockActiveGroup is
t11FLockRowStatus, which is defined with a MAX-ACCESS of read-create
and a MIN-ACCESS of read-only.  So, what do you want clarified ??

Keith.

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



From imss-bounces@ietf.org Fri Sep 08 11:49:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLibR-0008Ow-Ay; Fri, 08 Sep 2006 11:49:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLibQ-0008Or-0W
	for imss@ietf.org; Fri, 08 Sep 2006 11:49:12 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLibO-0000En-FH
	for imss@ietf.org; Fri, 08 Sep 2006 11:49:11 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 08 Sep 2006 08:49:10 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k88Fn9l7017861; Fri, 8 Sep 2006 08:49:09 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k88Fn9QV023837;
	Fri, 8 Sep 2006 08:49:09 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id IAA28020;
	Fri, 8 Sep 2006 08:48:04 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609081548.IAA28020@cisco.com>
Subject: Re: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in draft-i
To: bwijnen@lucent.com
Date: Fri, 8 Sep 2006 08:48:04 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 07, 2006 10:26:15 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=4552; t=1157730549; x=1158594549;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20WG=20last=20call=20review=3A=20T11-FC-FABRIC-LOCK-MIB=2
	0in=20draft-i;
	X=v=3Dcisco.com=3B=20h=3DM5DD5f2yIkW7qYyaXakVkxDoml0=3D;
	b=hDYV7TUgLRCHAyGGBcMF0BwsA6rk/uIYx6kLFkZDRcl5FKgH0HBtYuLpUh2gAze7grE8W3tX
	lSzJNQZZFUN7FghnSYlBDqrzX0uh7nBhSjDIia/VBZah/kzKaGzQjFFt;
Authentication-Results: sj-dkim-3.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: imss@ietf.org, Black_David@emc.com, 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

Sure, I'll make the changes you suggest.

Keith.

> I also see another few NITs now that I am reviewing the 2nd 
> MIB module in the same document.
> 
> - t11FLockRejectReasonCode OBJECT-TYPE
>     SYNTAX        T11NsGs4RejectReasonCode
>     MAX-ACCESS    read-only
>     STATUS        current
>     DESCRIPTION
>            "When the value of the corresponding instance of
>            t11FLockStatus is 'rejected', this object contains
>            the rejection's reason code."
> 
>   Based on the ENUMerated values for t11FlockStatus, I 
>   think we should change 'rejected' into 'rejectFailure'.
> 
> - same for t11FLockRejectReasonCodeExp
>   and t11FLockRejectReasonVendorCode
> 
> - Now that I see t11ZsServerReasonCode, I wonder if the 2nd
>   para in the DESCRIPTION clause would also make sense for
>   the t11FLockRejectReasonCode object
> 
> - do the SIZE for t11ZsServerReasonCodeExp
>   and t11ZsServerReasonVendorCode possibly also make sense for 
>   t11FLockRejectReasonCodeExp, t11FLockRejectReasonVendorCode
>   that is allowing for a SIZE of zero?
> 
> 
> Bert
> 
> > -----Original Message-----
> > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> > Sent: Thursday, September 07, 2006 17:51
> > To: Black_David@emc.com; imss@ietf.org
> > Cc: dromasca@avaya.com
> > Subject: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
> > draft-ietf-imss-f c-zs-mib-00.txt
> > 
> > 
> > T11-FC-FABRIC-LOCK-MIB review
> > 
> > --------- questions/comments
> > 
> > - DESSCIPTION clause of t11FLockApplicationID says:
> >            The value assigned to identify the 'application' for a
> >            lock established via Acquire Change Authorization (ACA)
> >            request is: 'D0'h (208 decimal).  This value will be
> >            documented in a future revision of the FC-SW-nn
> >            specification."
> > 
> >    Do we have any idea as to "when such future FC-SW-nn will show
> >    up ?? If not, is this acceptable?
> > 
> > - For t11FLockInitiator, in the case the SNMP, would it not be 
> >   wise/usefull to add the snmpSecuityName?
> > 
> > - Reading:
> > 
> >    t11FLockRowStatus OBJECT-TYPE
> >       SYNTAX        RowStatus
> >       MAX-ACCESS    read-create
> >       STATUS        current
> >       DESCRIPTION
> >            "The status of this conceptual row.
> > 
> >            A row for which the value of t11FLockInitiatorType is
> >            not 'snmp' cannot be deleted via this object."
> > 
> >   I wonder:
> >   - can a row be set to notReady or notInservice for rows that
> >     were not created by 'snmp'? I guess not, but one could get
> >     the impression that such is possible based on this one 
> >     sentence
> >   - What is the persistence behaviour of a row created via snmp?
> >     Probably nonVolatile? But would be good to say something
> >     about it.
> > 
> > - SO I see:
> > 
> >     t11FLockStatus OBJECT-TYPE
> >         SYNTAX        INTEGER {
> >                       active(1),
> >                       settingUp(2),
> >                       rejectFailure(3),
> >                       otherFailure(4)
> >                   }
> > 
> >   and wonder what will happen if the lock gets released?
> >   not sure I understand how such happens, but I would assume 
> > a lock does
> >   not stay forever once it has become active, does it?
> >   Does the entry disappear in that case? 
> > 
> > 
> > --------- NITS
> > 
> > - in t11FLockEntry DESCRIPTION clause I read 4th para:
> > 
> >           Recently, a distinct value of Application_ID has also been
> >           assigned/reserved as a means of distinguishing locks
> >           established via Acquire Change Authorization (ACA)
> >           requests.  With this recent assignment, an Application_ID
> > 
> >   I think I would remove "Recently" and "recent".
> >   This document is intended for a reasonably long lifespan in the
> >   future, no?
> > 
> > - REFERENCE clauses of course need to be updated.
> > 
> > - for t11FLockActiveGroup, the deascription clause does not say that
> >   (if write/create-mode is supported) that a lock can also be
> >   established.
> > 
> > Bert
> > 
> > _______________________________________________
> > imss mailing list
> > imss@ietf.org
> > https://www1.ietf.org/mailman/listinfo/imss
> > 
> 
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
> 

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



From imss-bounces@ietf.org Fri Sep 08 13:01:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLjiq-0000h7-K8; Fri, 08 Sep 2006 13:00:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLjip-0000dh-KV
	for imss@ietf.org; Fri, 08 Sep 2006 13:00:55 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLjio-0001Fv-1u
	for imss@ietf.org; Fri, 08 Sep 2006 13:00:55 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 08 Sep 2006 10:00:54 -0700
X-IronPort-AV: i="4.08,232,1154934000"; 
	d="scan'208"; a="319241707:sNHT36039156"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k88H0rXX012629; Fri, 8 Sep 2006 10:00:53 -0700
Received: from [10.21.80.168] (sjc-vpn4-168.cisco.com [10.21.80.168])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k88H0q6W022558;
	Fri, 8 Sep 2006 10:00:52 -0700 (PDT)
Message-ID: <4501A1BF.6040801@cisco.com>
Date: Fri, 08 Sep 2006 10:00:47 -0700
From: Claudio DeSanti <cds@cisco.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Keith McCloghrie <kzm@cisco.com>
Subject: Re: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
References: <200609081541.IAA27259@cisco.com>
In-Reply-To: <200609081541.IAA27259@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=5386; t=1157734853; x=1158598853;
	c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=cds@cisco.com; z=From:Claudio=20DeSanti=20<cds@cisco.com>
	|Subject:Re=3A=20[imss]=20WG=20last=20call=20review=3A=20T11-FC-FABRIC-LOCK-MIB=2
	0in; X=v=3Dcisco.com=3B=20h=3DNfyg2JD6u2efb5B9DniIRTK+40s=3D;
	b=WLVrX31JYdms4x5kc3D23rE05zeMK24d0DdK7248xnJ7MqsBQV2WMDQK0+PM7fDXyAgSeS3Z
	AJqc7ciBbk84t96U9g+TuP99ifl7OpAOj839jzzFcmW8/CZs+1cGutsb;
Authentication-Results: sj-dkim-5.cisco.com; header.From=cds@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: bwijnen@lucent.com, dromasca@avaya.com, Steve Wilson <swilson@Brocade.COM>,
	Black_David@emc.com, imss@ietf.org
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

Keith,

in a different conversation (unfortunately not happened on this list) 
with the FC-SW-x editor, we agreed that the proper value should be FFh, 
255 decimal. The first revision of FC-SW-5 is expected to contain this 
assignment.
Thanks,

                          Claudio.


Keith McCloghrie wrote:
>> T11-FC-FABRIC-LOCK-MIB review
>>
>> --------- questions/comments
>>
>> - DESSCIPTION clause of t11FLockApplicationID says:
>>            The value assigned to identify the 'application' for a
>>            lock established via Acquire Change Authorization (ACA)
>>            request is: 'D0'h (208 decimal).  This value will be
>>            documented in a future revision of the FC-SW-nn
>>            specification."
>>
>>    Do we have any idea as to "when such future FC-SW-nn will show
>>    up ?? If not, is this acceptable?
>>     
>  
> My understanding is that FC-SW-4 is closed, and it lists 'D0'h as one
> of the reserved values.  The long-time editor of FC-SW-nn sent an email
> message dated 8Aug06 to the T11.5 mailing-list with the assignment of
> a range of values including 'D0'h for this purpose.  The assignment
> will be documented in FC-SW-5 which is approved as a new project, but
> there is no initial draft of it yet.
>
> Would you like a formal liaison message from T11 to the IETF stating
> what number has been assigned ??
>
>   
>> - For t11FLockInitiator, in the case the SNMP, would it not be 
>>   wise/usefull to add the snmpSecuityName?
>>     
>  
> I suggest it should be possible to be a compliant implementation of this
> MIB even for an SNMPv1/SNMPv2 implementation which doesn't support SNMPv3.
> So, if we define an object to hold the value of snmpSecurityName, we
> need to define what value that object will have in an agent which does
> not implement the SNMP-COMMUNITY-MIB (in which snmpCommunitySecurityName
> is defined).  What value would you propose ??
>
>   
>> - Reading:
>>
>>    t11FLockRowStatus OBJECT-TYPE
>>       SYNTAX        RowStatus
>>       MAX-ACCESS    read-create
>>       STATUS        current
>>       DESCRIPTION
>>            "The status of this conceptual row.
>>
>>            A row for which the value of t11FLockInitiatorType is
>>            not 'snmp' cannot be deleted via this object."
>>
>>   I wonder:
>>   - can a row be set to notReady or notInservice for rows that
>>     were not created by 'snmp'? I guess not, but one could get
>>     the impression that such is possible based on this one 
>>     sentence
>>     
>
> How about we change "be deleted" to "have its status changed" ??
>
>   
>>   - What is the persistence behaviour of a row created via snmp?
>>     Probably nonVolatile? But would be good to say something
>>     about it.
>>     
>  
> No, I think it should be volatile, because an agent restart is the
> equivalent of the "various error situations" mentioned in the last
> paragraph of t11FLockEntry's DESCRIPTION.  Yes, I'll add some text.
>
>   
>> - SO I see:
>>
>>     t11FLockStatus OBJECT-TYPE
>>         SYNTAX        INTEGER {
>>                       active(1),
>>                       settingUp(2),
>>                       rejectFailure(3),
>>                       otherFailure(4)
>>                   }
>>
>>   and wonder what will happen if the lock gets released?
>>   not sure I understand how such happens, but I would assume a lock does
>>   not stay forever once it has become active, does it?
>>     
>
> No.  It gets released explicitly or implicitly (as mentioned above). 
>
>   
>>   Does the entry disappear in that case? 
>>     
>  
> Yes, because the table is defined as the list of all *current* locks.
>  
>   
>> --------- NITS
>>
>> - in t11FLockEntry DESCRIPTION clause I read 4th para:
>>
>>           Recently, a distinct value of Application_ID has also been
>>           assigned/reserved as a means of distinguishing locks
>>           established via Acquire Change Authorization (ACA)
>>           requests.  With this recent assignment, an Application_ID
>>
>>   I think I would remove "Recently" and "recent".
>>   This document is intended for a reasonably long lifespan in the
>>   future, no?
>>     
>  
> OK, how about I can change it to:
>
>           Not long before this MIB was defined, a distinct value of
>           Application_ID was also assigned/reserved as the means to
>           distinguish locks established via Acquire Change
> 	  Authorization (ACA) requests.  This additional assignment
> 	  allows an Application_ID to be used to uniquely identify a
> 	  lock amongst all active locks established either by an EACA
> 	  or by an ACA.
>
>   
>> - REFERENCE clauses of course need to be updated.
>>     
>  
> Right.
>
>   
>> - for t11FLockActiveGroup, the description clause does not say that
>>   (if write/create-mode is supported) that a lock can also be
>>   established.
>>     
>  
> I don't understand.  One of the objects in the t11FLockActiveGroup is
> t11FLockRowStatus, which is defined with a MAX-ACCESS of read-create
> and a MIN-ACCESS of read-only.  So, what do you want clarified ??
>
> Keith.
>
> _______________________________________________
> imss mailing list
> imss@ietf.org
> https://www1.ietf.org/mailman/listinfo/imss
>
>   

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



From imss-bounces@ietf.org Fri Sep 08 15:04:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLleM-0007iE-CW; Fri, 08 Sep 2006 15:04:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLleL-0007i8-3O
	for imss@ietf.org; Fri, 08 Sep 2006 15:04:25 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLleK-0004OY-Nc
	for imss@ietf.org; Fri, 08 Sep 2006 15:04:25 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k88J3aqA016440;
	Fri, 8 Sep 2006 14:03:37 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BK0WSF>; Fri, 8 Sep 2006 21:03:35 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA96E3F@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>, bwijnen@lucent.com
Subject: RE: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
Date: Fri, 8 Sep 2006 21:03:33 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c
Cc: imss@ietf.org, Black_David@emc.com, 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

Inline

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Friday, September 08, 2006 17:42
> To: bwijnen@lucent.com
> Cc: Black_David@emc.com; imss@ietf.org; dromasca@avaya.com
> Subject: Re: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
> 
> 
> > T11-FC-FABRIC-LOCK-MIB review
> > 
> > --------- questions/comments
> > 
> > - DESSCIPTION clause of t11FLockApplicationID says:
> >            The value assigned to identify the 'application' for a
> >            lock established via Acquire Change Authorization (ACA)
> >            request is: 'D0'h (208 decimal).  This value will be
> >            documented in a future revision of the FC-SW-nn
> >            specification."
> > 
> >    Do we have any idea as to "when such future FC-SW-nn will show
> >    up ?? If not, is this acceptable?
>  
> My understanding is that FC-SW-4 is closed, and it lists 'D0'h as one
> of the reserved values.  The long-time editor of FC-SW-nn sent an email
> message dated 8Aug06 to the T11.5 mailing-list with the assignment of
> a range of values including 'D0'h for this purpose.  The assignment
> will be documented in FC-SW-5 which is approved as a new project, but
> there is no initial draft of it yet.
> 
And Claudio already seems to say it is a value of 255.
Shows that it is BEST to try and get agreement and document.

> Would you like a formal liaison message from T11 to the IETF stating
> what number has been assigned ??
> 

For me personally, I just am trying to make sure we all know/agree what
the value is (can be). And it seems we have no agreement on that yet.

It is up to your WG chair and or AD to decide if the want/need a formal 
liaison statement. 

> > - For t11FLockInitiator, in the case the SNMP, would it not be 
> >   wise/usefull to add the snmpSecuityName?
>  
> I suggest it should be possible to be a compliant implementation of this
> MIB even for an SNMPv1/SNMPv2 implementation which doesn't support SNMPv3.

Well, in IETF terms we have made CNMPv1 and SNMPv2c HISTORIC.
I understand there may be implementation that are still nto SNMPv3
compliant. But we're defining a stds track MIB here, and should (in my view)
assume that people are not using our full STD SNMP version.

> So, if we define an object to hold the value of snmpSecurityName, we
> need to define what value that object will have in an agent which does
> not implement the SNMP-COMMUNITY-MIB (in which snmpCommunitySecurityName
> is defined).  What value would you propose ??
> 

I feel that we do NOT have to spec out what people who are not coming along 
to the current IETF standards need to do in old (HISTORIC) code.

In my view they could implement just the SNMP-COMMUNITY-MIB and use
that mapping. They could alos use some imeplementation-specific or
som ad-hoc mechanism... it is not IETF standards compliant anyway, so why
would we worry.

For the security considerations, we also do not give advise on what to do if
a vendor/customers tsick to SNMPv1/v2c. We RECOMMEND to not use that, but if 
they ignore that and just do SNMPv1/v2c, they are on their own. Also for this
topic.

> > - Reading:
> > 
> >    t11FLockRowStatus OBJECT-TYPE
> >       SYNTAX        RowStatus
> >       MAX-ACCESS    read-create
> >       STATUS        current
> >       DESCRIPTION
> >            "The status of this conceptual row.
> > 
> >            A row for which the value of t11FLockInitiatorType is
> >            not 'snmp' cannot be deleted via this object."
> > 
> >   I wonder:
> >   - can a row be set to notReady or notInservice for rows that
> >     were not created by 'snmp'? I guess not, but one could get
> >     the impression that such is possible based on this one 
> >     sentence
> 
> How about we change "be deleted" to "have its status changed" ??
> 

that at least makes it clear. Thanks.

> >   - What is the persistence behaviour of a row created via snmp?
> >     Probably nonVolatile? But would be good to say something
> >     about it.
>  
> No, I think it should be volatile, because an agent restart is the
> equivalent of the "various error situations" mentioned in the last
> paragraph of t11FLockEntry's DESCRIPTION.  Yes, I'll add some text.
> 

Thanks, looking forward to the text.

> > - SO I see:
> > 
> >     t11FLockStatus OBJECT-TYPE
> >         SYNTAX        INTEGER {
> >                       active(1),
> >                       settingUp(2),
> >                       rejectFailure(3),
> >                       otherFailure(4)
> >                   }
> > 
> >   and wonder what will happen if the lock gets released?
> >   not sure I understand how such happens, but I would assume a lock does
> >   not stay forever once it has become active, does it?
> 
> No.  It gets released explicitly or implicitly (as mentioned above). 
> 

Might be good to also state that somewhere in a DESCRIPTION clause.

> >   Does the entry disappear in that case? 
>  
> Yes, because the table is defined as the list of all *current* locks.
>  

Also that should be documented in a DESCRIPTION clause... but 
the list is NOT a list of all *current* locks. Because the Status allows
for errors like rejectFailure/other failure. In that case it is NOT
a current lock, is it? How long will such a row exist?


> > --------- NITS
> > 
> > - in t11FLockEntry DESCRIPTION clause I read 4th para:
> > 
> >           Recently, a distinct value of Application_ID has also been
> >           assigned/reserved as a means of distinguishing locks
> >           established via Acquire Change Authorization (ACA)
> >           requests.  With this recent assignment, an Application_ID
> > 
> >   I think I would remove "Recently" and "recent".
> >   This document is intended for a reasonably long lifespan in the
> >   future, no?
>  
> OK, how about I can change it to:
> 
>           Not long before this MIB was defined, a distinct value of
>           Application_ID was also assigned/reserved as the means to
>           distinguish locks established via Acquire Change
> 	  Authorization (ACA) requests.  This additional assignment
> 	  allows an Application_ID to be used to uniquely identify a
> 	  lock amongst all active locks established either by an EACA
> 	  or by an ACA.
> 

That is better.
I do not see why you need "Noy long before this MIB was defined".
It seems superfluous to me too. But it is better than "Recently".

> > - REFERENCE clauses of course need to be updated.
>  
> Right.
> 
> > - for t11FLockActiveGroup, the description clause does not say that
> >   (if write/create-mode is supported) that a lock can also be
> >   established.
>  
> I don't understand.  One of the objects in the t11FLockActiveGroup is
> t11FLockRowStatus, which is defined with a MAX-ACCESS of read-create
> and a MIN-ACCESS of read-only.  So, what do you want clarified ??
> 

The GROUP DESCRIPTION clause states:

    DESCRIPTION
           "A collection of objects containing information
           about current fabric locks."

That sounds as if it is only for reading/monitoring.
Where as (at least according to MAX-ACCESS clause) you can also use
it to actually create/establish a lock.

As I said, it is a NIT.

Bert
> Keith.
> 

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



From imss-bounces@ietf.org Mon Sep 11 16:35:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GMsUY-00049v-Iq; Mon, 11 Sep 2006 16:34:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GMsUX-00049q-EV
	for imss@ietf.org; Mon, 11 Sep 2006 16:34:53 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GMsUW-0007nF-JJ
	for imss@ietf.org; Mon, 11 Sep 2006 16:34:53 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 11 Sep 2006 13:34:52 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8BKYqfr015876; Mon, 11 Sep 2006 13:34:52 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k8BKYpYp028324;
	Mon, 11 Sep 2006 13:34:51 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id NAA01744;
	Mon, 11 Sep 2006 13:33:46 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609112033.NAA01744@cisco.com>
Subject: Re: [imss] WG last call review: T11-FC-ZONE-SERVER-MIB in
To: bwijnen@lucent.com
Date: Mon, 11 Sep 2006 13:33:46 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 07, 2006 11:17:22 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=16157; t=1158006892; x=1158870892;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20WG=20last=20call=20review=3A=20T11-FC-ZONE-SERVER-MIB=2
	0in; X=v=3Dcisco.com=3B=20h=3DzwXAaKTd1FawHaAN/5DEG7WkNiU=3D;
	b=p9NgsMYoHXJ6Bwr9fFbIZXZJQiJgNhopVrmgMe01vp9bPfmsnyG25raA5Rxxq/IGMIsTJo3F
	gY8JdEANbjIsvvDUc1ktuV4l2ytzIm7mb+nojmouxAKoRgQ6sbrQ1jas;
Authentication-Results: sj-dkim-3.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e9d8c60d9288f2c774f26bab15869505
Cc: imss@ietf.org, Black_David@emc.com, 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

Thanks for the comments.  Responses below.

Keith.
---------------------------

> T11-FC-ZONE-SERVER-MIB
> 
> --------- questions/comments
> 
> - Would it be better to rename T11ZoningName to T11ZsZoningName?
>   This for naming consistency and avoiding possible future name
>   clashes.
 
First, I would agree if its name was ZoningName, but prepended with
"T11", the odds of it having any affect on "future name clashes" is
negligible.

Second, I regret that I named T11NsGs4RejectReasonCode with an
"Ns" in the middle -- it would have been better to have named it
T11Gs4RejectReasonCode, or better still T11GsRejectReasonCode, 
because it has been used in several FC MIBs for protocols defined in
FC-GS-nn, i.e., it is not specific to the Name Server and not specific
to FC-GS-4.

Third, if used in another MIB, the place where it is defined is
specified in the IMPORTS clause, and thus, doesn't have to be explicit
from the name.

Nevertheless, if you insist that I repeat my past mistakes:-), OK.

> - For t11ZsServerDistribute
>           Setting this object will fail if the corresponding
>           instance of t11ZsServerOperationMode has the value
>           'enhanced', or if the corresponding instance of
>           t11ZsZoneSetResult has the value 'inProgress'."
>   
>   will fail with what? I assume/think 'inconsistentValue'.
>   Might be good to state so, to ensure proper implementation.

I disagree.  I think it's bad practice to put error codes in
DESCRIPTIONs.  I just cricitized the IPSP WG MIBs for putting
'inconsistentValue' in their DESCRIPTIONs because that error code
is NOT used if and when any of the nine higher-precedence error
conditions prevails.

How about I change it to:

         When the corresponding instance of t11ZsServerOperationMode
         has the value 'enhanced', or when the corresponding instance
         of t11ZsZoneSetResult has the value 'inProgress', it
         is inconsistent to try to set the value of this object.

> - Now that I see t11ZsServerReasonCode, I wonder if the 2nd
>   para in the DESCRIPTION clause would also make sense for
>   the t11FLockRejectReasonCode object
 
OK.

> - do the SIZE for t11ZsServerReasonCodeExp
>   and t11ZsServerReasonVendorCode possibly also make sense for 
>   t11FLockRejectReasonCodeExp, t11FLockRejectReasonVendorCode
>   that is allowing for a SIZE of zero?
  
OK.

> - I wonder why this
> 
>     t11ZsServerDefaultZoneSetting OBJECT-TYPE
>         SYNTAX       INTEGER {
>                         permit(1),
>                         deny(2)
>                      }
> 
>   Is not done with a TruthValue possibly using a different
>   descriptor.
>   Not a fatal flaw though, but a missed opportunity for
>   re-use in my view. Unless if one expects more values in
>   the future.
> 
>   For t11ZsServerMergeControlSetting it is less obvious, but the
>   same question could be asked I guess.
 
Each object in question refers to the setting of a single bit, which
(obviously:-) takes the values 0 or 1, and so, yes, it would be possible
to define each object as a TruthValue which has two values 'true' and
'false'.  However, the FC-GS-5 spec does not define either bit as:
true/false.  Instead, it defines the behaviour when the bit is 0, and
the behaviour when the bit is 1.  I think it's better in these cases to
emphasize the commonality with FC-GS-5 by using the same definition,
rather than intepreting the definitions as true/false.

> - I see:
>     t11ZsSetName OBJECT-TYPE
>         SYNTAX       T11ZoningName
>         MAX-ACCESS   read-create
>         STATUS       current
>         DESCRIPTION
>            "The name of this Zone Set. The t11ZsSetName should
>            be unique within a fabric.
> 
>            The Zone Set can be renamed by setting this object
>            to a new value."
> 
>   and wonder if the rename can also be done while the row is in
>   'active' state !!??
 
It can.  I'll add a few words.

> - I am not sure I understand this:
> 
>     t11ZsSetEntry  OBJECT-TYPE
>         SYNTAX       T11ZsSetEntry
>         MAX-ACCESS   not-accessible
>         STATUS       current
>         DESCRIPTION
>            "Each entry contains information about a Zone Set
>            in the Zone Set database of a particular fabric
>            (identified by the value of t11ZsServerFabricIndex)
>            on a particular switch (identified by values of
>            fcmInstanceIndex and fcmSwitchIndex).
> 
>            A Zone Set is created containing zero or more
>            existing Zones.  As and when new Zones are created
>            (as rows in the t11ZsZoneTable), they can be added
>            to a Zone Set by creating an entry for each in the
>            t11ZsSetZoneTable.
> 
>            The StorageType of a row in this table is specified by
>            the instance of t11ZsServerDatabaseStorageType which is
>            INDEX-ed by the same values of fcmInstanceIndex,
>            fcmSwitchIndex and t11ZsServerFabricIndex."
>         INDEX   { fcmInstanceIndex, fcmSwitchIndex,
>                   t11ZsServerFabricIndex, t11ZsSetIndex }
>         ::= { t11ZsSetTable 1 }
> 
>   So it seems to me I can do SNMP SET to create an entry in this
>   table. But is is not clear if, when I do so, and entry in the 
>   t11ZsServerTable must already exist or not. Probably so,
>   because it uses the actual (index) objects from that table.
>   But in practice, can an SNMP utility not just create entries
>   with index values that do not really exists in the base
>   table? I'd like to know how the agent is supposed to react.
 
Well, yes, the row in the t11ZsServerTable must exist, but to say
"already exist" would mislead the reader because there's no RowStatus
in that table.  Instead, there's an entry in the t11ZsServerTable
for the Zone Server for a particular fabric on a particular switch.
I think that's already implicit in:

           "Each entry contains information about a Zone Set
           in the Zone Set database of a particular fabric
           (identified by the value of t11ZsServerFabricIndex)
           on a particular switch (identified by values of
           fcmInstanceIndex and fcmSwitchIndex).

In other words, this MIB about creating/editing information in the
Zone Set Database of existing Zone Servers, not for creating new
Zone Servers on switches and/or new Fabrics.

Would it help to insert "existing" in the above paragraph to try to
make it more explicit ??

>   So if the base table entrues must exist first,
>   then it would be good to say so, i.e. spell it out.
>   And to say what happens if it does not yet exist.
>   If not, then I wonder how/when the entry in that t11ZsServerTable
>   does get created, because otherwise it is unclear how/if/when
>   the persistency works.
>   
>   And what when I delete the row? Does it have any effect on the
>   associated rows in t11ZsServerTable. Possibly not. But I am
>   not sure how I can determine that based on the current
>   DESCRIPTION clauses.
 
Deleting a row from the t11ZsSetTable deletes the Zone Set from the
Zone Set Database maintained by the Zone Server, but does not
otherwise affect the Zone Server.

> - I have the same/similar question for t11ZsZoneEntry
 
So, shall I also insert "existing" into t11ZsZoneEntry's DESCRIPTION
to try to make it similarly more explicit ??

> - Can t11ZsZoneAttribBlock be changed while row is active?
> 
>   such questions can be asked for more read-write/read-create
>   objects in this MIB module. I won't keep repeating.
 
See the picture in section 5.6 -- all read-write objects in the
Zone Set Database can be modified at any time.  The reason that other
MIBs don't allow writes while a row is active is because they overload
the RowStatus for in-use/not-in-use as well as for create/delete.
In this MIB, only the Active Zone Set is in-use and it is read-only
except to be Activated/De-Activated.

I too don't want to keep repeating it.  So, suggest I add a paragraph
to the MODULE-IDENTITY's DESCRIPTION explaining that the MIB is a
combination of the Zone Set Database and the Active Zone Set, where all
objects representing the former are modifiable at any time whereas all
objects representing the latter are always read-only, other than by
completely overwritting the Active Zone Set by a subset of Zone
Set Database, or by completely deleting it.

> - For t11ZsSetZoneEntry, it seems that the 3 other tables MUST
>   have an existing associated entry(entries) before creating 
>   an entry in this row makes sense. But maybe it is OK to 
>   prepare this table before the other tables have been 
>   completed/created?
 
> - for t11ZsSetZoneRowStatus I wonder what happens if this
>   one has a value of active, byt the rowstatus in some of
>   the other (base) tables have a value of notInservice or
>   notReady ??
> 
>   Are we all supposed to try and figure this out, or would it
>   be better to put something about this in the various
>   DESCRIPTION clauses?
>
> - In fact the whole fate-sharing between all the tables may
>   need to be described. I see some of it in section 5.5. and
>   5.6 of the document, but also from that I do not yet see
>   what the implications are if the rowstatus in one table is
>   notInservice, while others are actve or  maybe notReady,
>   or maybe do not (yet) exist.
>   I must also admit that I have not studied the T11 documents 
>   much (in fact very little) yet. But I'd hope that these
>   basic question would be answered in the IETF MIB document
>   itself.
 
OK.

> - I see no persistency behaviour (or a link to the StorageType
>   objects in the base table in t11ZsActivateTable.
>   I think it is clear that the writable objects are all
>   volatile (they seem to be control objects that cause an
>   action when SET).
 
Persistency is fully specified in those objects which include
this statement: 

           When read, the value of this object is always xxx.

This statement:

           "A textual message indicating the reason for the
           most recent failure of a Zone Set activation or
           de-activation, or the zero-length string if no
           information is available.

allows an agent to retain the info for as long as it can.

I'll modify:

           The value 'none' indicates activation/de-activation
           has not been attempted.

by appending "since the last restart of the management system."

> - For namingconsistency in:
>     T11ZsActiveZoneEntry ::= SEQUENCE {
>        t11ZsActiveZoneIndex      Unsigned32,
>        t11ZsActiveZoneName       T11ZoningName,
>        t11ZsActiveBroadcast      TruthValue,
>        t11ZsActiveHardZoning     TruthValue
>     }
>   I would insert a "Zone" before "Broadcast" and before "Hardzoning"
 
I didn't do that because whereas t11ZsActiveZoneIndex is the Zone's
Index and t11ZsActiveZoneName is the Zone's Name, t11ZsActiveBroadcast
is not the Zone's Broadcast.  Further, t11ZsActiveBroadcast is about
"Broadcast Zoning", not "Zone Broadcast" -- t11ZsActiveZoneBroadcast
gives the wrong impression.  So, I guess it has to be
t11ZsActiveZoneBroadcastZoning.

>   By the way, t11ZsActiveZoneSetName in the T11ZsActiveEntry might be
>   (at first sight) perceived to be in the T11ZsActiveZoneEntry.
>   I understand why it has that name, but it may consfuse some
>   people.
> 
> - t11ZsActiveBroadcast and t11ZsActiveHardZoning both have in
>   their DESCRIPTION clauses:
>              This object is only instantiated in Enhanced mode."
> 
>   would we not want to specify that in a MODULE-COMPLIANCE for 
>   basic mode and one for enhanced mode?
 
They are both in the t11ZsEnhancedModeGroup, and it is specified as:

    GROUP        t11ZsEnhancedModeGroup
    DESCRIPTION
           "This group is mandatory only for those systems
           with Zone Servers which support Enhanced Mode."

which I believe is sufficient.
 
> --------- NITS/TYPOs
> 
> - In one but last para of DESCRIPTION clause of MODULE-IDENTITY
> 
>      When this MIB is used for Basic Zoning Management, the same
>      set of MIBs objects as used for Enhanced mode are used to
> 
>   s/MIBs objects/MIB objects/
> 
> - In t11ZsServerFabricIndex, the last 2 paragraphs of the
>   DESCRIPTION clause seem redundant with the DESCRIPTION clause
>   of the TC itself. I would remove them. The idea of a TC is
>   to have one place (namely in the DESCRIPTION clause of the TC)
>   to describe the (basic) semantics of the objects that use 
>   the TC as a SYNTAX.
 
If I recall correctly, I added them there due to some earlier
comment on an exactly-equivalent definition (I don't remember which
MIB it was in).

> - t11ZsServerCapabilityObject
>   I think I would rename zonesetDb(1) to zoneSetDb(1)
>   but this is pretty subjective taste of course.
> 
> - last para of description clasue of t11ZsServerDatabaseStorageType
> 
>            This value of this object is a...
> 
>   s/This/The/ ??
>   
> - For t11ZsAttribType maybe add "other values reserved" in the 
>   DESCRIPTION clause. I went looking it up, because in an 
>   earlier object we had E0-EF as Vendor specific. So I thought
>   that might also be the case here. But the text in the 
>   REFERENCEd docment/section told me they are reserved.
 
Values which are reserved today could easily be allocated tomorrow.
Values which are allocated today will likely stay allocated to the
same thing for a long time into the future.  Thus, listing the allocated
values and omitting the reserved values has the best chance of
continuing to be correct in the future.

> - for
>    t11ZsActivateRequest OBJECT-TYPE
>      SYNTAX       Unsigned32 (0..4294967295)
>      MAX-ACCESS   read-write
>      STATUS       current
>      DESCRIPTION
>            "Setting this object to a value is a request for a
>            Zone Set to be activated on the fabric which is
>            represented by this row.  The Zone Set to be
>            activated is the one for which t11ZsSetIndex has
>            the same value.
> 
>            If a Zone Set is already active on a fabric when a
>            request is made to activate a different one on that
>            fabric, then the existing Zone Set is automatically
>            deactivated and the specified Zone Set is activated
>            in its place.
> 
>            The value of this object when read is always 0."
> 
>    It seems that setting the value to zero has no effect. Right?
>    But zero seems to also have special meaning. Oh well. I might
>    indicate it by using 
>      SYNTAX       Unsigned32 (0 | 1..4294967295)
>    but that is subjective taste I guess.
>
> - similarly, for
> 
>     t11ZsFabricIndex OBJECT-TYPE
>         SYNTAX       Unsigned32 (0..4096)
> 
>   I think I would use  
> 
>         SYNTAX       Unsigned32 (0..4095 | 4096)
> 
>   to indicate that 4096 has special meaning.
 
The example which is most well-known (at least to me) of a "special
meaning" is InterfaceIndexOrZero which is not indicated like this.
Further, I don't know where, if anywhere, your convention is
documented, and I think you would have difficulty defining the
term "special meaning" if you did try to document it.

>   Maybe I would even create a 
> 
>       T11FabricIndexOrAll ::= TEXTUAL-CONVENTION
> 
>   So it could if an "ALL" option is needed in the future that it is
>   (or at least can be) done in a consistent maner.
 
If I thought that it would be re-used, then yes, I'd do this.
But, after so many (that I've lost count) Fibre Channel MIBs, and
now that I'm working on the last set (at least, the last scheduled
ones), I don't think it's worth it.

> - I personally prefer to name notifications xxxNotification instead
>   of naming them xxxNotify. But I admit that that is subjective.
> 
> Bert
> 

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



From imss-bounces@ietf.org Tue Sep 12 09:41:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GN8WJ-0006NT-Ga; Tue, 12 Sep 2006 09:41:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GN8WH-0006NO-T5
	for imss@ietf.org; Tue, 12 Sep 2006 09:41:45 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GN8WH-0008Uh-6R
	for imss@ietf.org; Tue, 12 Sep 2006 09:41:45 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k8CDe1jG026161;
	Tue, 12 Sep 2006 08:40:01 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BLA01J>; Tue, 12 Sep 2006 15:39:59 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AA973E7@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>
Subject: RE: [imss] WG last call review: T11-FC-ZONE-SERVER-MIB in
Date: Tue, 12 Sep 2006 15:40:00 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3da7e5d5ca82d58872786934e4963616
Cc: imss@ietf.org, Black_David@emc.com, 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

Inline

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Monday, September 11, 2006 22:34
> To: bwijnen@lucent.com
> Cc: Black_David@emc.com; imss@ietf.org; dromasca@avaya.com
> Subject: Re: [imss] WG last call review: T11-FC-ZONE-SERVER-MIB in
> 
> 
> Thanks for the comments.  Responses below.
> 
> Keith.
> ---------------------------
> 
> > T11-FC-ZONE-SERVER-MIB
> > 
> > --------- questions/comments
> > 
> > - Would it be better to rename T11ZoningName to T11ZsZoningName?
> >   This for naming consistency and avoiding possible future name
> >   clashes.
>  
> First, I would agree if its name was ZoningName, but prepended with
> "T11", the odds of it having any affect on "future name clashes" is
> negligible.
> 
Oh, if it did not start with T11, I would RECOMMEND to change it.
Now it is just a thought that I wanted you to consider.
If a name clash ever occurs, then it is 99.999% to happen in T11 space,
so the WG can decide.

> Second, I regret that I named T11NsGs4RejectReasonCode with an
> "Ns" in the middle -- it would have been better to have named it
> T11Gs4RejectReasonCode, or better still T11GsRejectReasonCode, 
> because it has been used in several FC MIBs for protocols defined in
> FC-GS-nn, i.e., it is not specific to the Name Server and not specific
> to FC-GS-4.
> 
> Third, if used in another MIB, the place where it is defined is
> specified in the IMPORTS clause, and thus, doesn't have to be explicit
> from the name.
> 
> Nevertheless, if you insist that I repeat my past mistakes:-), OK.
> 

I do not insist. I list what I see/perceive as things to consider and
that I prefer people take conscious decision on. If your (WG) decision
is to stick with what you have, I can live with it.

> > - For t11ZsServerDistribute
> >           Setting this object will fail if the corresponding
> >           instance of t11ZsServerOperationMode has the value
> >           'enhanced', or if the corresponding instance of
> >           t11ZsZoneSetResult has the value 'inProgress'."
> >   
> >   will fail with what? I assume/think 'inconsistentValue'.
> >   Might be good to state so, to ensure proper implementation.
> 
> I disagree.  I think it's bad practice to put error codes in
> DESCRIPTIONs. 

I agree if the errors are very obvious.
Unfortunately we have seen too many people who do not read the
sequence in RFC3416 very well and implement the wrong error
returncode. So that is why I bring it up.

> I just cricitized the IPSP WG MIBs for putting
> 'inconsistentValue' in their DESCRIPTIONs because that error code
> is NOT used if and when any of the nine higher-precedence error
> conditions prevails.
> 

Well, I agree that one has to explain in what circumstance the
inconsistentValue needs to be returned. Of course all goes accoring
to the steps listed in RFC3416

> How about I change it to:
> 
>          When the corresponding instance of t11ZsServerOperationMode
>          has the value 'enhanced', or when the corresponding instance
>          of t11ZsZoneSetResult has the value 'inProgress', it
>          is inconsistent to try to set the value of this object.
> 

That will do it for me.
Because I can determine from that when to return inconsistenValue ;-)

> > - Now that I see t11ZsServerReasonCode, I wonder if the 2nd
> >   para in the DESCRIPTION clause would also make sense for
> >   the t11FLockRejectReasonCode object
>  
> OK.
> 
thanks

> > - do the SIZE for t11ZsServerReasonCodeExp
> >   and t11ZsServerReasonVendorCode possibly also make sense for 
> >   t11FLockRejectReasonCodeExp, t11FLockRejectReasonVendorCode
> >   that is allowing for a SIZE of zero?
>   
> OK.
> 
thanks

> > - I wonder why this
> > 
> >     t11ZsServerDefaultZoneSetting OBJECT-TYPE
> >         SYNTAX       INTEGER {
> >                         permit(1),
> >                         deny(2)
> >                      }
> > 
> >   Is not done with a TruthValue possibly using a different descriptor.
> >   Not a fatal flaw though, but a missed opportunity for
> >   re-use in my view. Unless if one expects more values in
> >   the future.
> > 
> >   For t11ZsServerMergeControlSetting it is less obvious, but the
> >   same question could be asked I guess.
>  
> Each object in question refers to the setting of a single bit, which
> (obviously:-) takes the values 0 or 1, and so, yes, it would be possible
> to define each object as a TruthValue which has two values 'true' and
> 'false'.  However, the FC-GS-5 spec does not define either bit as:
> true/false.  Instead, it defines the behaviour when the bit is 0, and
> the behaviour when the bit is 1.  I think it's better in these cases to
> emphasize the commonality with FC-GS-5 by using the same definition,
> rather than intepreting the definitions as true/false.
> 

So it seems you are mapping a 1-bit value from the protocol to an object.
Makes sense. I guess if I had read the underlying protocol spec(s) better,
that I might have no asked the question. Hope you don't mind asking questions
as a new-reader of the MIB module.

> > - I see:
> >     t11ZsSetName OBJECT-TYPE
> >         SYNTAX       T11ZoningName
> >         MAX-ACCESS   read-create
> >         STATUS       current
> >         DESCRIPTION
> >            "The name of this Zone Set. The t11ZsSetName should
> >            be unique within a fabric.
> > 
> >            The Zone Set can be renamed by setting this object
> >            to a new value."
> > 
> >   and wonder if the rename can also be done while the row is in
> >   'active' state !!??
>  
> It can.  I'll add a few words.
> 
Thanks

> > - I am not sure I understand this:
> > 
> >     t11ZsSetEntry  OBJECT-TYPE
> >         SYNTAX       T11ZsSetEntry
> >         MAX-ACCESS   not-accessible
> >         STATUS       current
> >         DESCRIPTION
> >            "Each entry contains information about a Zone Set
> >            in the Zone Set database of a particular fabric
> >            (identified by the value of t11ZsServerFabricIndex)
> >            on a particular switch (identified by values of
> >            fcmInstanceIndex and fcmSwitchIndex).
> > 
> >            A Zone Set is created containing zero or more
> >            existing Zones.  As and when new Zones are created
> >            (as rows in the t11ZsZoneTable), they can be added
> >            to a Zone Set by creating an entry for each in the
> >            t11ZsSetZoneTable.
> > 
> >            The StorageType of a row in this table is specified by
> >            the instance of t11ZsServerDatabaseStorageType which is
> >            INDEX-ed by the same values of fcmInstanceIndex,
> >            fcmSwitchIndex and t11ZsServerFabricIndex."
> >         INDEX   { fcmInstanceIndex, fcmSwitchIndex,
> >                   t11ZsServerFabricIndex, t11ZsSetIndex }
> >         ::= { t11ZsSetTable 1 }
> > 
> >   So it seems to me I can do SNMP SET to create an entry in this
> >   table. But is is not clear if, when I do so, and entry in the 
> >   t11ZsServerTable must already exist or not. Probably so,
> >   because it uses the actual (index) objects from that table.
> >   But in practice, can an SNMP utility not just create entries
> >   with index values that do not really exists in the base
> >   table? I'd like to know how the agent is supposed to react.
>  
> Well, yes, the row in the t11ZsServerTable must exist, but to say
> "already exist" would mislead the reader because there's no RowStatus
> in that table.  Instead, there's an entry in the t11ZsServerTable
> for the Zone Server for a particular fabric on a particular switch.
> I think that's already implicit in:
> 
>            "Each entry contains information about a Zone Set
>            in the Zone Set database of a particular fabric
>            (identified by the value of t11ZsServerFabricIndex)
>            on a particular switch (identified by values of
>            fcmInstanceIndex and fcmSwitchIndex).
> 
> In other words, this MIB about creating/editing information in the
> Zone Set Database of existing Zone Servers, not for creating new
> Zone Servers on switches and/or new Fabrics.
> 
> Would it help to insert "existing" in the above paragraph to try to
> make it more explicit ??
> 

If you mean to change
            "Each entry contains information about a Zone Set
into
            "Each entry contains information about a existing Zone Set
then I think that would make it clearer (at least for me).
See, I sort of concluded that, but it is always nice (as a new implementer
of a spec that one did not co-develop/co-design) to get affirmation of what
you think needs to or can be done.

> >   So if the base table entrues must exist first,
> >   then it would be good to say so, i.e. spell it out.
> >   And to say what happens if it does not yet exist.
> >   If not, then I wonder how/when the entry in that t11ZsServerTable
> >   does get created, because otherwise it is unclear how/if/when
> >   the persistency works.
> >   
> >   And what when I delete the row? Does it have any effect on the
> >   associated rows in t11ZsServerTable. Possibly not. But I am
> >   not sure how I can determine that based on the current
> >   DESCRIPTION clauses.
>  
> Deleting a row from the t11ZsSetTable deletes the Zone Set from the
> Zone Set Database maintained by the Zone Server, but does not
> otherwise affect the Zone Server.
> 

I'd say that it might be good to add that to the t11ZsSetEntry 
DESCRIPTION clause.

> > - I have the same/similar question for t11ZsZoneEntry
>  
> So, shall I also insert "existing" into t11ZsZoneEntry's DESCRIPTION
> to try to make it similarly more explicit ??
> 
pls do so

> > - Can t11ZsZoneAttribBlock be changed while row is active?
> > 
> >   such questions can be asked for more read-write/read-create
> >   objects in this MIB module. I won't keep repeating.
>  
> See the picture in section 5.6 -- all read-write objects in the
> Zone Set Database can be modified at any time.  The reason that other
> MIBs don't allow writes while a row is active is because they overload
> the RowStatus for in-use/not-in-use as well as for create/delete.
> In this MIB, only the Active Zone Set is in-use and it is read-only
> except to be Activated/De-Activated.
> 
> I too don't want to keep repeating it.  So, suggest I add a paragraph
> to the MODULE-IDENTITY's DESCRIPTION explaining that the MIB is a
> combination of the Zone Set Database and the Active Zone Set, 
> where all
> objects representing the former are modifiable at any time whereas all
> objects representing the latter are always read-only, other than by
> completely overwritting the Active Zone Set by a subset of Zone
> Set Database, or by completely deleting it.
> 

That would be a good idea. Possibly adding a ptr to sect 5.6 in this 
document, so that when someone (in teh future) reads an exatrcted 
MIB, that they can find the info.

> > - For t11ZsSetZoneEntry, it seems that the 3 other tables MUST
> >   have an existing associated entry(entries) before creating 
> >   an entry in this row makes sense. But maybe it is OK to 
> >   prepare this table before the other tables have been 
> >   completed/created?
>  
> > - for t11ZsSetZoneRowStatus I wonder what happens if this
> >   one has a value of active, byt the rowstatus in some of
> >   the other (base) tables have a value of notInservice or
> >   notReady ??
> > 
> >   Are we all supposed to try and figure this out, or would it
> >   be better to put something about this in the various
> >   DESCRIPTION clauses?
> >
> > - In fact the whole fate-sharing between all the tables may
> >   need to be described. I see some of it in section 5.5. and
> >   5.6 of the document, but also from that I do not yet see
> >   what the implications are if the rowstatus in one table is
> >   notInservice, while others are actve or  maybe notReady,
> >   or maybe do not (yet) exist.
> >   I must also admit that I have not studied the T11 documents 
> >   much (in fact very little) yet. But I'd hope that these
> >   basic question would be answered in the IETF MIB document
> >   itself.
>  
> OK.
> 
thanks

> > - I see no persistency behaviour (or a link to the StorageType
> >   objects in the base table in t11ZsActivateTable.
> >   I think it is clear that the writable objects are all
> >   volatile (they seem to be control objects that cause an
> >   action when SET).
>  
> Persistency is fully specified in those objects which include
> this statement: 
> 
>            When read, the value of this object is always xxx.
> 
> This statement:
> 
>            "A textual message indicating the reason for the
>            most recent failure of a Zone Set activation or
>            de-activation, or the zero-length string if no
>            information is available.
> 
> allows an agent to retain the info for as long as it can.
> 
> I'll modify:
> 
>            The value 'none' indicates activation/de-activation
>            has not been attempted.
> 
> by appending "since the last restart of the management system."
> 

Thanks.
I'd have to go reread the whole MIB again if that addresses my
complete comment on persistency.

> > - For namingconsistency in:
> >     T11ZsActiveZoneEntry ::= SEQUENCE {
> >        t11ZsActiveZoneIndex      Unsigned32,
> >        t11ZsActiveZoneName       T11ZoningName,
> >        t11ZsActiveBroadcast      TruthValue,
> >        t11ZsActiveHardZoning     TruthValue
> >     }
> >   I would insert a "Zone" before "Broadcast" and before "Hardzoning"
>  
> I didn't do that because whereas t11ZsActiveZoneIndex is the Zone's
> Index and t11ZsActiveZoneName is the Zone's Name, t11ZsActiveBroadcast
> is not the Zone's Broadcast.  Further, t11ZsActiveBroadcast is about
> "Broadcast Zoning", not "Zone Broadcast" -- t11ZsActiveZoneBroadcast
> gives the wrong impression.  So, I guess it has to be
> t11ZsActiveZoneBroadcastZoning.
> 

That would then probably be better (but also longer, which I know you hate. 
I can live with names up to 64 characters these days).

Note that I am just pointing out where I perceive inconsistencies.
I appreciate your explanation as to why it exists here.
It is all within this t11ZsXxxx namespace, so it is not as dramatic
that I absolutely must see it changed. I would like that, but I understand
it is somewhat personal taste or personal strictness on naming.

> >   By the way, t11ZsActiveZoneSetName in the T11ZsActiveEntry might
> >   be (at first sight) perceived to be in the T11ZsActiveZoneEntry.
> >   I understand why it has that name, but it may consfuse some
> >   people.
> > 
> > - t11ZsActiveBroadcast and t11ZsActiveHardZoning both have in
> >   their DESCRIPTION clauses:
> >              This object is only instantiated in Enhanced mode."
> > 
> >   would we not want to specify that in a MODULE-COMPLIANCE for 
> >   basic mode and one for enhanced mode?
>  
> They are both in the t11ZsEnhancedModeGroup, and it is specified as:
> 
>     GROUP        t11ZsEnhancedModeGroup
>     DESCRIPTION
>            "This group is mandatory only for those systems
>            with Zone Servers which support Enhanced Mode."
> 
> which I believe is sufficient.
>  

I see (now that you point it out). 
Some (I may be one of them) like to not see "compliance/optional/required"
in DESCRIPTION clauses of objects, but ratehr see them in the MODULE-COMPLIANCE.
If they are in both places (and consistent) I can live with it.


> > --------- NITS/TYPOs
> > 
> > - In one but last para of DESCRIPTION clause of MODULE-IDENTITY
> > 
> >      When this MIB is used for Basic Zoning Management, the same
> >      set of MIBs objects as used for Enhanced mode are used to
> > 
> >   s/MIBs objects/MIB objects/
> > 
> > - In t11ZsServerFabricIndex, the last 2 paragraphs of the
> >   DESCRIPTION clause seem redundant with the DESCRIPTION clause
> >   of the TC itself. I would remove them. The idea of a TC is
> >   to have one place (namely in the DESCRIPTION clause of the TC)
> >   to describe the (basic) semantics of the objects that use 
> >   the TC as a SYNTAX.
>  
> If I recall correctly, I added them there due to some earlier
> comment on an exactly-equivalent definition (I don't remember which
> MIB it was in).
> 

Was that commen from me (meaning I would be inconsistent in my commenting)?
I am not saying that this is impossible, but in general I believe I do 
comment that we prefer to not to see a lot of stuff from the DESCRIPTION
clause of a TC repeated in teh DESCRIPTION clause of an object that
uses teh TC for its SYNTAX.

Not that this was under "NITS", so I am not too upset about it.

> > - t11ZsServerCapabilityObject
> >   I think I would rename zonesetDb(1) to zoneSetDb(1)
> >   but this is pretty subjective taste of course.
> > 
> > - last para of description clasue of t11ZsServerDatabaseStorageType
> > 
> >            This value of this object is a...
> > 
> >   s/This/The/ ??
> >   
> > - For t11ZsAttribType maybe add "other values reserved" in the 
> >   DESCRIPTION clause. I went looking it up, because in an 
> >   earlier object we had E0-EF as Vendor specific. So I thought
> >   that might also be the case here. But the text in the 
> >   REFERENCEd docment/section told me they are reserved.
>  
> Values which are reserved today could easily be allocated tomorrow.
> Values which are allocated today will likely stay allocated to the
> same thing for a long time into the future.  Thus, listing 
> the allocated
> values and omitting the reserved values has the best chance of
> continuing to be correct in the future.
> 

OK, but that is then inconsistent with the earlier object, and so that
is also why I got confused.

But again, it is a NIT, so I leave it up to you.

> > - for
> >    t11ZsActivateRequest OBJECT-TYPE
> >      SYNTAX       Unsigned32 (0..4294967295)
> >      MAX-ACCESS   read-write
> >      STATUS       current
> >      DESCRIPTION
> >            "Setting this object to a value is a request for a
> >            Zone Set to be activated on the fabric which is
> >            represented by this row.  The Zone Set to be
> >            activated is the one for which t11ZsSetIndex has
> >            the same value.
> > 
> >            If a Zone Set is already active on a fabric when a
> >            request is made to activate a different one on that
> >            fabric, then the existing Zone Set is automatically
> >            deactivated and the specified Zone Set is activated
> >            in its place.
> > 
> >            The value of this object when read is always 0."
> > 
> >    It seems that setting the value to zero has no effect. Right?
> >    But zero seems to also have special meaning. Oh well. I might
> >    indicate it by using 
> >      SYNTAX       Unsigned32 (0 | 1..4294967295)
> >    but that is subjective taste I guess.
> >
> > - similarly, for
> > 
> >     t11ZsFabricIndex OBJECT-TYPE
> >         SYNTAX       Unsigned32 (0..4096)
> > 
> >   I think I would use  
> > 
> >         SYNTAX       Unsigned32 (0..4095 | 4096)
> > 
> >   to indicate that 4096 has special meaning.
>  
> The example which is most well-known (at least to me) of a "special
> meaning" is InterfaceIndexOrZero which is not indicated like this.

Yep... defined along long time ago.
My suggested notation is used more and more.

> Further, I don't know where, if anywhere, your convention is
> documented, and I think you would have difficulty defining the
> term "special meaning" if you did try to document it.
> 

Forget my rambling if you rather not do it.
Not worth the time if we disagree.

> >   Maybe I would even create a 
> > 
> >       T11FabricIndexOrAll ::= TEXTUAL-CONVENTION
> > 
> >   So it could if an "ALL" option is needed in the future that it is
> >   (or at least can be) done in a consistent maner.
>  
> If I thought that it would be re-used, then yes, I'd do this.
> But, after so many (that I've lost count) Fibre Channel MIBs, and
> now that I'm working on the last set (at least, the last scheduled
> ones), I don't think it's worth it.
> 

OK... your call.

> > - I personally prefer to name notifications xxxNotification instead
> >   of naming them xxxNotify. But I admit that that is subjective.
> > 
> > Bert
> > 
> 

Bert

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



From imss-bounces@ietf.org Wed Sep 13 11:09:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNWMd-0005zR-4Z; Wed, 13 Sep 2006 11:09:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNWMb-0005zM-N8
	for imss@ietf.org; Wed, 13 Sep 2006 11:09:21 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNWMY-0002Gz-CJ
	for imss@ietf.org; Wed, 13 Sep 2006 11:09:21 -0400
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11])
	by mexforward.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k8DF9G3j029162
	for <imss@ietf.org>; Wed, 13 Sep 2006 11:09:16 -0400 (EDT)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com
	[10.254.64.53])
	by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k8DF8fat023705
	for <imss@ietf.org>; Wed, 13 Sep 2006 11:09:13 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by
	corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.0); 
	Wed, 13 Sep 2006 11:08:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Sep 2006 11:08:58 -0400
Message-ID: <F222151D3323874393F83102D614E05502B67363@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Index: AcbXRonG2BDbR2r8TpKZf62LAD0dRw==
To: <imss@ietf.org>
X-OriginalArrivalTime: 13 Sep 2006 15:08:59.0584 (UTC)
	FILETIME=[8A5F9400:01C6D746]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935,
	Antispam-Data: 2006.9.13.72943
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2,
	NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTE 0,
	__CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0,
	__IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0,
	__SANE_MSGID 0, __STOCK_SUBJ_7 0'
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [imss] (no subject)
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

First of all, I want to thank Bert for doing his usual
thorough job of MIB reviewing.  In looking over the
review emails, I've flagged about half a dozen issues
that require WG and/or WG chair attention - I will put
these (and any others that turn up between now and the
end of WG Last Call) into separate messages to the list
after completion of the Last Call in order to focus
attention on the decisions that need to be made.

Some of these items involve T11 interactions, and there
appear to be three such items:
1) The Good: FC-GS-5 is stable, and a REFERENCE update
	in the MIB drafts should suffice.
2) The Bad: FC-LS is not yet stable, and the currently-
	expected T11 date of October for its completion is
	unlikely to happen.  I'm one of the troublemakers,
	as I've (strongly) suggested that T11 use FC-LS to
	lay the groundwork for cleaning up a problem area
	in iFCP (RFC 4172).
3) The Ugly: T11 does not have an IANA equivalent, and
	hence we will need to come up with something to
	formalize the allocation and record it in some-
	thing reference-able prior to FC-SW-5 putting in
	an appearance.
The latter two are my responsibility to work through
T11 - expect an update after T11's meetings in the first
week of October.

Thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

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



From imss-bounces@ietf.org Thu Sep 14 11:20:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNt13-0004fe-Fc; Thu, 14 Sep 2006 11:20:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNt12-0004dx-Kz
	for imss@ietf.org; Thu, 14 Sep 2006 11:20:36 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNson-0005VU-7A
	for imss@ietf.org; Thu, 14 Sep 2006 11:07:58 -0400
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11])
	by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k8EF7s5L004419
	for <imss@ietf.org>; Thu, 14 Sep 2006 11:07:54 -0400 (EDT)
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com
	[10.254.64.54])
	by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k8EF7Pnv024725
	for <imss@ietf.org>; Thu, 14 Sep 2006 11:07:53 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by
	corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.0); 
	Thu, 14 Sep 2006 11:07:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Sep 2006 11:07:31 -0400
Message-ID: <F222151D3323874393F83102D614E05502B67377@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call comments on draft-ietf-imss-fc-zs-mib-00.txt
Thread-Index: AcbYD4AlJ8Wf7FGuR1CgTeIc9azYiQ==
To: <imss@ietf.org>
X-OriginalArrivalTime: 14 Sep 2006 15:07:31.0841 (UTC)
	FILETIME=[807CCF10:01C6D80F]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935,
	Antispam-Data: 2006.9.14.73443
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2,
	NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTE 0,
	__CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0,
	__IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0,
	__SANE_MSGID 0'
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [imss] Last Call comments on draft-ietf-imss-fc-zs-mib-00.txt
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

Section 3 is not a "Short" Overview of Fibre Channel ;-).  It could
usefully be broken into 3 subsections:
- Overview
- Zoning
- Zoning Configuration and Management

The first paragraph describing zoning says:

   Zones within a fabric provide a mechanism to control frame delivery
   between Nx_Ports ("Hard Zoning") or to expose selected views of Name
   Server information ("Soft Zoning").  This technique is similar to
   virtual private networks in that the fabric has the ability to group
   devices into Zones.

It needs an additional few sentences to explain what a zone does and
where it's enforced, specifically to make the following points:
- Communication is only possible when the communicating endpoints
	are members of a common zone.
- Hard zoning and soft zoning are two different means of realizing
	this.  Hard zoning is enforced in the fabric (i.e., switches)
	whereas soft zoning is enforced at the endpoints (e.g., HBAs)
	by relying on the endpoints to not send traffic to an N_Port_ID
	not obtained from the nameserver with a few exceptions for well
	known N_Port_IDs used to bootstrap the fabric (e.g., talk to the
	nameserver).

Section 5.4 ought to explain how an SNMP management client can determine
whether a fabric is operating in basic vs. enhanced mode.

Thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

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



From imss-bounces@ietf.org Thu Sep 14 12:16:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNtso-0007Xe-EE; Thu, 14 Sep 2006 12:16:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNtsm-0007Sc-JV
	for imss@ietf.org; Thu, 14 Sep 2006 12:16:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNtgl-0005dO-Dx
	for imss@ietf.org; Thu, 14 Sep 2006 12:03:45 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-5.cisco.com with ESMTP; 14 Sep 2006 09:03:42 -0700
X-IronPort-AV: i="4.09,165,1157353200"; 
	d="scan'208"; a="321263679:sNHT73560384"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8EG3fXg001215; Thu, 14 Sep 2006 09:03:41 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k8EG3fw7009515;
	Thu, 14 Sep 2006 09:03:41 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id JAA14545;
	Thu, 14 Sep 2006 09:02:33 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609141602.JAA14545@cisco.com>
Subject: Re: [imss] Last Call comments on draft-ietf-imss-fc-zs-mib-00.txt
To: Black_David@emc.com
Date: Thu, 14 Sep 2006 09:02:33 -0700 (PDT)
In-Reply-To: <no.id> from "Black_David@emc.com" at Sep 14, 2006 11:07:31 AM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1880; t=1158249821; x=1159113821;
	c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss]=20Last=20Call=20comments=20on=20draft-ietf-imss-fc-zs-mib
	-00.txt;
	X=v=3Dcisco.com=3B=20h=3DZSAdQs9zlfgRJCFddy60O3HsHl0=3D;
	b=EOmtmsGnohceRP1jWAgPOc9AhKna5pAPJ2/OLGI4cIHljNWaFwE3T9qY5KcKXvkRbU36lAEl
	Az/zX/8bzibcfdS9yhvFJR7Y1KIPmj6a7ux4lvOVGv4PLEFoP9xk9BRy;
Authentication-Results: sj-dkim-6.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: imss@ietf.org
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

> Section 3 is not a "Short" Overview of Fibre Channel ;-).  It could

OK, I'll just delete the "Short".

> usefully be broken into 3 subsections:
> - Overview

After deleting "Short", this would be better as "Introduction" or as
"General Overview".

> - Zoning
> - Zoning Configuration and Management

OK, I assume you're not suggesting a re-ordering, but just the insertion
of sub-section titles, e.g., insert "3.3  Zoning Configuration and
Management" immediately before::

   Zones are configured via a Fabric Zone Server, using ...
 
> The first paragraph describing zoning says:
> 
>    Zones within a fabric provide a mechanism to control frame delivery
>    between Nx_Ports ("Hard Zoning") or to expose selected views of Name
>    Server information ("Soft Zoning").  This technique is similar to
>    virtual private networks in that the fabric has the ability to group
>    devices into Zones.
> 
> It needs an additional few sentences to explain what a zone does and
> where it's enforced, specifically to make the following points:
> - Communication is only possible when the communicating endpoints
> 	are members of a common zone.
> - Hard zoning and soft zoning are two different means of realizing
> 	this.  Hard zoning is enforced in the fabric (i.e., switches)
> 	whereas soft zoning is enforced at the endpoints (e.g., HBAs)
> 	by relying on the endpoints to not send traffic to an N_Port_ID
> 	not obtained from the nameserver with a few exceptions for well
> 	known N_Port_IDs used to bootstrap the fabric (e.g., talk to the
> 	nameserver).
 
OK.

> Section 5.4 ought to explain how an SNMP management client can determine
> whether a fabric is operating in basic vs. enhanced mode.
 
OK.  I'll add a paragraph which mentions t11ZsServerOperationMode, and
probably t11ZsServerCapabilityObject as well.

Keith.

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



From imss-bounces@ietf.org Thu Sep 14 14:53:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GNwKj-0001gW-3u; Thu, 14 Sep 2006 14:53:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GNwKh-0001gR-WD
	for imss@ietf.org; Thu, 14 Sep 2006 14:53:08 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNwKe-0000ik-8G
	for imss@ietf.org; Thu, 14 Sep 2006 14:53:07 -0400
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11])
	by mexforward.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k8EIr14S002165; Thu, 14 Sep 2006 14:53:01 -0400 (EDT)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com
	[10.254.64.53])
	by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k8EIqnWx018853; Thu, 14 Sep 2006 14:53:00 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by
	corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.0); 
	Thu, 14 Sep 2006 14:52:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [imss] Last Call comments on draft-ietf-imss-fc-zs-mib-00.txt
Date: Thu, 14 Sep 2006 14:52:58 -0400
Message-ID: <F222151D3323874393F83102D614E05502B6737A@CORPUSMX20A.corp.emc.com>
In-Reply-To: <200609141602.JAA14545@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [imss] Last Call comments on draft-ietf-imss-fc-zs-mib-00.txt
Thread-Index: AcbYF3x+jchz/ne0Ty2R67me7q34AwAF1HxQ
To: <kzm@cisco.com>
X-OriginalArrivalTime: 14 Sep 2006 18:52:59.0041 (UTC)
	FILETIME=[FF53B910:01C6D82E]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935,
	Antispam-Data: 2006.9.14.110943
X-PerlMx-Spam: Gauge=, SPAM=2%, Reason='EMC_FROM_0+ -2, NO_REAL_NAME 0, __CT 0,
	__CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0,
	__HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: imss@ietf.org
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

> OK, I assume you're not suggesting a re-ordering, but just the
insertion
> of sub-section titles, e.g., insert "3.3  Zoning Configuration and
> Management" immediately before::
>=20
>    Zones are configured via a Fabric Zone Server, using ...

Yes.

Thanks,
--David

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]=20
> Sent: Thursday, September 14, 2006 12:03 PM
> To: Black, David
> Cc: imss@ietf.org
> Subject: Re: [imss] Last Call comments on=20
> draft-ietf-imss-fc-zs-mib-00.txt
>=20
> > Section 3 is not a "Short" Overview of Fibre Channel ;-).  It could
>=20
> OK, I'll just delete the "Short".
>=20
> > usefully be broken into 3 subsections:
> > - Overview
>=20
> After deleting "Short", this would be better as "Introduction" or as
> "General Overview".
>=20
> > - Zoning
> > - Zoning Configuration and Management
>=20
> OK, I assume you're not suggesting a re-ordering, but just the
insertion
> of sub-section titles, e.g., insert "3.3  Zoning Configuration and
> Management" immediately before::
>=20
>    Zones are configured via a Fabric Zone Server, using ...
> =20
> > The first paragraph describing zoning says:
> >=20
> >    Zones within a fabric provide a mechanism to control frame
delivery
> >    between Nx_Ports ("Hard Zoning") or to expose selected views of
Name
> >    Server information ("Soft Zoning").  This technique is similar to
> >    virtual private networks in that the fabric has the ability to
group
> >    devices into Zones.
> >=20
> > It needs an additional few sentences to explain what a zone does and
> > where it's enforced, specifically to make the following points:
> > - Communication is only possible when the communicating endpoints
> > 	are members of a common zone.
> > - Hard zoning and soft zoning are two different means of realizing
> > 	this.  Hard zoning is enforced in the fabric (i.e., switches)
> > 	whereas soft zoning is enforced at the endpoints (e.g., HBAs)
> > 	by relying on the endpoints to not send traffic to an N_Port_ID
> > 	not obtained from the nameserver with a few exceptions for well
> > 	known N_Port_IDs used to bootstrap the fabric (e.g., talk to the
> > 	nameserver).
> =20
> OK.
>=20
> > Section 5.4 ought to explain how an SNMP management client can
determine
> > whether a fabric is operating in basic vs. enhanced mode.
> =20
> OK.  I'll add a paragraph which mentions t11ZsServerOperationMode, and
> probably t11ZsServerCapabilityObject as well.
>=20
> Keith.
>=20

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



From imss-bounces@ietf.org Thu Sep 14 18:53:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GO05R-0005Dz-6h; Thu, 14 Sep 2006 18:53:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GO05N-0005BI-RC; Thu, 14 Sep 2006 18:53:33 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GO05L-00071A-FI; Thu, 14 Sep 2006 18:53:33 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k8EMrU5E032064; 
	Thu, 14 Sep 2006 15:53:30 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k8EMrU3q032063;
	Thu, 14 Sep 2006 15:53:30 -0700
Date: Thu, 14 Sep 2006 15:53:30 -0700
Message-Id: <200609142253.k8EMrU3q032063@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 4625 on Fibre Channel Routing Information MIB
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


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4625

        Title:      Fibre Channel Routing Information MIB 
        Author:     C. DeSanti, K. McCloghrie,
                    S. Kode, S. Gai
        Status:     Standards Track
        Date:       September 2006
        Mailbox:    cds@cisco.com, 
                    srinikode@yahoo.com, 
                    kzm@cisco.com
        Pages:      22
        Characters: 41278
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imss-fc-rtm-mib-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4625.txt

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for information related
to routing within a Fibre Channel fabric, which is independent of the
usage of a particular routing protocol.  [STANDARDS TRACK]

This document is a product of the Internet and Management Support for 
Storage Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



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



From imss-bounces@ietf.org Thu Sep 14 18:55:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GO079-00066c-2M; Thu, 14 Sep 2006 18:55:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GO075-00066G-Go; Thu, 14 Sep 2006 18:55:19 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GO074-0007NE-5K; Thu, 14 Sep 2006 18:55:19 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k8EMtHUE032080; 
	Thu, 14 Sep 2006 15:55:17 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k8EMtHT7032079;
	Thu, 14 Sep 2006 15:55:17 -0700
Date: Thu, 14 Sep 2006 15:55:17 -0700
Message-Id: <200609142255.k8EMtHT7032079@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 4626 on MIB for Fibre Channel's Fabric Shortest Path
	First (FSPF) Protocol
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


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4626

        Title:      MIB for Fibre Channel's Fabric 
                    Shortest Path First (FSPF) Protocol 
        Author:     C. DeSanti, V. Gaonkar,
                    K. McCloghrie, S. Gai
        Status:     Standards Track
        Date:       September 2006
        Mailbox:    cds@cisco.com, 
                    vgaonkar@cisco.com, 
                    kzm@cisco.com
        Pages:      36
        Characters: 67953
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imss-fc-fspf-mib-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4626.txt

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for information related
to the Fibre Channel network's Fabric Shortest Path First (FSPF)
routing protocol.  [STANDARDS TRACK]

This document is a product of the Internet and Management Support for 
Storage Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



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



From imss-bounces@ietf.org Sun Sep 17 13:20:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GP0Js-0000oS-Pl; Sun, 17 Sep 2006 13:20:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GP0Js-0000oK-31
	for imss@ietf.org; Sun, 17 Sep 2006 13:20:40 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GP0Jq-0000cS-Nv
	for imss@ietf.org; Sun, 17 Sep 2006 13:20:40 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k8HHD3jg030776
	for <imss@ietf.org>; Sun, 17 Sep 2006 13:13:03 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 17 Sep 2006 20:20:31 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B4397F5@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: imss WG Last Call: Fibre Channel RSCN, Fabric Config Svr,
	and Zone Svr MIBs
Thread-Index: AcbIpjYETqZKYTMhTCO9ZtEnajfsxgRxc7ZQ
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <Black_David@emc.com>, <imss@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: 
Subject: [imss] 
	RE: imss WG Last Call: Fibre Channel RSCN, Fabric Config Svr,
	and Zone Svr MIBs
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

draft-ietf-imss-fc-rscn-mib-00.txt

1. smilint complains about:=20

mibs/T11-FC-RSCN-MIB:217: [1] {internal-other} parse error, unexpected
LOWERCASE_IDENTIFIER, expecting '}' or ','
mibs/T11-FC-RSCN-MIB:227: [5] {internal-flushing} warning: flushing
recent incorrect declaration, see previous error(s)
mibs/T11-FC-RSCN-MIB:170: [2] {type-unknown} unknown type
`T11FcRscnStatsEntry'

All seem due to a missing comma in=20

t11FcRscnSwRscnRejects             Counter32

 2.=20
   Note that an interface's ifIndex value must be unique within an SNMP
   context, irrespective of how many Fibre Channel management instances
   (see below) and how many Fibre Channel switches are instrumented
   within that SNMP context.

What do we exactly mean by 'SNMP context' ? I believe that the meaning
is of a management domain modeled by SMIv2 MIBs or fiber channel
management instance, not necessarily SNMP-related.
draft-ietf-imss-fc-fcs-mib-00.txt got it better, 'SNMP context' is only
an example there.=20

3. The Security Considerations section does not really provide an
explanation about the hazards in intentionally or unintentionally
misconfiguring the read-write objects (probably suppressing information,
or flooding the network with undesired notifications)=20

draft-ietf-imss-fc-fcs-mib-00.txt

1. smilints returns 3 warnings:=20

T11-FC-FABRIC-CONFIG-SERVER-MIB:773: [5] {index-element-not-accessible}
warning: exactly one index element of row `t11FcsPortListEntry' must be
accessible
mibs/T11-FC-FABRIC-CONFIG-SERVER-MIB:80: [5] {type-without-format}
warning: type `T11ListIndex' has no format specification
mibs/T11-FC-FABRIC-CONFIG-SERVER-MIB:90: [5] {type-without-format}
warning: type `T11ListIndexPointer' has no format specification

2. Some of the read-write objects have no DEFVAL defined -
t11FcsFabricDiscoveryRangeLow, t11FcsFabricDiscoveryRangeHigh,
t11FcsFabricDiscoveryStart


 draft-ietf-imss-fc-zs-mib-00.txt

1. I was expecting the Security Considerations section of this document
to include more details about the security issues related to the
read-write objects in the MIB modules. While it is true that intentional
or unintentional misconfiguration can lead to some kind of connectivity
problems there are however differences in the level of threats generated
by attacking fabric controls and generation of notifications. These need
to be separately articulated IMO.=20

2. It is not clear to me how t11FLockTable entries work in the case of a
non SNMP lock creation. How is a new row protected so that it will not
be manipulated by CLI while in SNMP creation and the other way? If there
are some assumptions about a common underCreation state, they need to be
clearly articulated.=20

3. I do not have the T11 reference at hand, but I wonder why objects
like t11FLockRejectReasonCodeExp have a SYNTAX of OCTET STRING. In any
case, I would suggest a DISPLAY-HINT clause for these.=20

4. In T11ZoningName, what does 'letter' mean - ASCII only or
internationalized as in SnmpAdminString?=20

Dan




> -----Original Message-----
> From: Black_David@emc.com [mailto:Black_David@emc.com]=20
> Sent: Saturday, August 26, 2006 3:26 AM
> To: imss@ietf.org
> Cc: Black_David@emc.com; Romascanu, Dan (Dan)
> Subject: imss WG Last Call: Fibre Channel RSCN, Fabric Config=20
> Svr, and Zone Svr MIBs
>=20
> This is to announce an imss WG Last Call on the following=20
> three MIB drafts:
>=20
>      Fibre Channel Registered State Change Notification (RSCN) MIB
>                    draft-ietf-imss-fc-rscn-mib-00.txt
>=20
>              Fibre-Channel Fabric Configuration Server MIB
>                    draft-ietf-imss-fc-fcs-mib-00.txt
>=20
>                      Fibre-Channel Zone Server MIB
>                     draft-ietf-imss-fc-zs-mib-00.txt
> =20
> This WG Last Call will run through 12 midnight Eastern Time=20
> on Sunday, September 17, 2006 (your WG chair hopes to deal=20
> with Last Call results during the week of September 18th).
>=20
> Technical comments *must* be sent to the imss mailing list.
> Editorial comments may be sent directly to the draft editor=20
> (but please cc: me) - all three drafts have the same editor:
>=20
> 		Keith McCloghrie [kzm@cisco.com]
>=20
> Thanks,
> --David (imss WG chair)
> ----------------------------------------------------
> David L. Black, Senior Technologist
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> black_david@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20

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



From imss-bounces@ietf.org Mon Sep 18 15:11:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPOWC-0004R4-Hj; Mon, 18 Sep 2006 15:11:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPOWA-0004QJ-G6
	for imss@ietf.org; Mon, 18 Sep 2006 15:10:58 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPOW7-0002Kp-Qy
	for imss@ietf.org; Mon, 18 Sep 2006 15:10:58 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 18 Sep 2006 12:10:55 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8IJAtkr022561; Mon, 18 Sep 2006 12:10:55 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k8IJAsQV009163;
	Mon, 18 Sep 2006 12:10:54 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id MAA25438;
	Mon, 18 Sep 2006 12:09:46 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609181909.MAA25438@cisco.com>
Subject: Re: [imss]
To: dromasca@avaya.com
Date: Mon, 18 Sep 2006 12:09:46 -0700 (PDT)
In-Reply-To: <no.id> from "Romascanu, Dan \(Dan\)" at Sep 17, 2006 08:20:31 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=8361; t=1158606655; x=1159470655;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss];
	X=v=3Dcisco.com=3B=20h=3DNv4KD+jbB7gOEwMz11rNHW3/RuA=3D;
	b=eZ5+AQ1wa5UF9l8dp0yXIS4wCnJEHdEXCJ2REZPtbpY6o8JAfvKjAhf+qGYDZojzZAALzz+c
	mXejEn7iXea/c8RjJc0r0r25fb35VnSIMXmKKXyg1S7LM8A5wXdQIvSo;
Authentication-Results: sj-dkim-3.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783
Cc: imss@ietf.org, Black_David@emc.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

Thanks for the comments.  My responses below.

Keith.
---------------------------------

> draft-ietf-imss-fc-rscn-mib-00.txt
> 
> 1. smilint complains about: 
> 
> mibs/T11-FC-RSCN-MIB:217: [1] {internal-other} parse error, unexpected
> LOWERCASE_IDENTIFIER, expecting '}' or ','
> mibs/T11-FC-RSCN-MIB:227: [5] {internal-flushing} warning: flushing
> recent incorrect declaration, see previous error(s)
> mibs/T11-FC-RSCN-MIB:170: [2] {type-unknown} unknown type
> `T11FcRscnStatsEntry'
> 
> All seem due to a missing comma in 
> 
> t11FcRscnSwRscnRejects             Counter32

Yes, we had already caught this.

>  2. 
>    Note that an interface's ifIndex value must be unique within an SNMP
>    context, irrespective of how many Fibre Channel management instances
>    (see below) and how many Fibre Channel switches are instrumented
>    within that SNMP context.
> 
> What do we exactly mean by 'SNMP context' ? I believe that the meaning
> is of a management domain modeled by SMIv2 MIBs or fiber channel
> management instance, not necessarily SNMP-related.

No, we mean exactly what is specified in RFC 3411, section 3.3.1.

> draft-ietf-imss-fc-fcs-mib-00.txt got it better, 'SNMP context' is only
> an example there. 
 
RSCN is missing a couple of common edits which were done for FCS & ZS,
i.e., both FCS & ZS have just the one reference to an SNMP context:

   "... for example within the same SNMP context ([RFC3411] section 3.3.1)."

In contrast, RSCN has two references to an SNMP context:

1. The same one as FCS & RSCN, except that it is missing the edit which
   inserted "for example".
2. The one in the paragraph you quote above.  This paragraph was written
   for a previous Fibre Channel MIB which IMPORT-ed ifIndex for use in
   INDEX clauses alongside index-ing objects for Fibre Channel
   management instances and Fibre Channel switches.  The intent of the
   paragraph is to clarify that an ifIndex value must be unique within
   an SNMP context even if that means it must be unique across multiple
   Fibre Channel management instances and across multiple Fibre Channel
   switches.  However, the paragraph is not needed in any of the FCS,
   RSCN or ZS MIBs because none of them have ifIndex in any INDEX
   clause.  This paragraph has already been deleted from the FCS & RSCN
   MIB documents.

So, there are two missing edits in the RSCN MIB document:
- insert "for example"
- deleted extraneous paragraph.

> 3. The Security Considerations section does not really provide an
> explanation about the hazards in intentionally or unintentionally
> misconfiguring the read-write objects (probably suppressing information,
> or flooding the network with undesired notifications) 
 
These notifications can't occur so often, and so I won't say "flooding".
But it's easy to add a sentence to say: 

   The object to enable/disable the notifications would, if
   misconfigured, either generate unwanted notifications or suppress
   wanted notifications.

While I think it's redundant, it doesn't do any harm.  So, I will add it.

> draft-ietf-imss-fc-fcs-mib-00.txt
> 
> 1. smilints returns 3 warnings: 
> 
> T11-FC-FABRIC-CONFIG-SERVER-MIB:773: [5] {index-element-not-accessible}
> warning: exactly one index element of row `t11FcsPortListEntry' must be
> accessible

This is a bug in smilint.  t11FcsPortListTable has only one columnar
object: t11FcsPortListIndex, and it is read-only.

> mibs/T11-FC-FABRIC-CONFIG-SERVER-MIB:80: [5] {type-without-format}
> warning: type `T11ListIndex' has no format specification
> mibs/T11-FC-FABRIC-CONFIG-SERVER-MIB:90: [5] {type-without-format}
> warning: type `T11ListIndexPointer' has no format specification

For both of these, RFC 2579 says:

   The DISPLAY-HINT clause, which need not be present, ...

and RFC 4181 says:

   The DISPLAY-HINT clause is used [...]  Its presence is optional.

> 2. Some of the read-write objects have no DEFVAL defined -
> t11FcsFabricDiscoveryRangeLow, t11FcsFabricDiscoveryRangeHigh,
> t11FcsFabricDiscoveryStart
 
RFC 2578 says:

   The DEFVAL clause, which need not be present, ...
 
The only change to this in RFC 4181 is a situation where DEFVAL MUST NOT
be used. 

>  draft-ietf-imss-fc-zs-mib-00.txt
> 
> 1. I was expecting the Security Considerations section of this document
> to include more details about the security issues related to the
> read-write objects in the MIB modules. While it is true that intentional
> or unintentional misconfiguration can lead to some kind of connectivity
> problems there are however differences in the level of threats generated
> by attacking fabric controls and generation of notifications. These need
> to be separately articulated IMO. 

So, how about I add:

 - the suppression of notifications (e.g., of unauthorized operations), and
 - the disruption of network operations due to the generation of unwanted
   notifications,

to the list of potential consequences ??

> 2. It is not clear to me how t11FLockTable entries work in the case of a
> non SNMP lock creation. How is a new row protected so that it will not
> be manipulated by CLI while in SNMP creation and the other way? If there
> are some assumptions about a common underCreation state, they need to be
> clearly articulated. 

FC-GS-5 specifies how locks are created on receipt of an SSB,
To avoid a conflict, the MIB needed to define how a lock can be
created via SNMP, such that SNMP-management could modify the Zone
Database without interference from the in-band management protocol,
and vice-versa.  While defining a mechanism for SNMP, it seemed like a
good idea to allow for locks by the CLI.

A row in the table for the CLI works in the same way as a row in the
table for the in-band management protocol, i.e., if a row in the
t11FLockTable is created by SNMP, its value of t11FLockInitiatorType =
'snmp'.  If a row has its value of t11FLockInitiatorType ='cli' or 'ssb',
then it cannot be deleted by SNMP.  So, there are no "assumptions about a
common underCreation state".

> 3. I do not have the T11 reference at hand, but I wonder why objects
> like t11FLockRejectReasonCodeExp have a SYNTAX of OCTET STRING. In any
> case, I would suggest a DISPLAY-HINT clause for these. 
 
t11FLockRejectReasonCodeExp is a 1-byte hexadecimal value, with an
ASCII string associated which each assigned value to indicate its meaning.
So, if the list were stable, this would be an enumerated INTEGER.
However, new reason codes get defined periodically, and it's unlikely
that this WG will get re-chartered frequently enough to keep the
enumerated values listed in the MIB uptodate.  Nor do we want to impose
a burden on IANA to assign new values, when new values are already being
assigned in T11 and documented in T11 specifications.  Instead, the
object has been defined an an "OCTET STRING (SIZE(1))" with a REFERENCE
clause which points to the most recent spec for assigned values.

So, I think that if anything is missing here, it's that there is no
explicit indication in this MIB that values which will not yet assigned
but will be assigned in future revisions of the Fibre Channel spec will
then be valid in this object.  Would you like me to append to the
REFERENCE clause, something like:

         ... or its successor"

In regard to a DISPLAY-HINT, there are two possible ways to display
a value of this object: either as a hex value, or as the relevant ASCII
string from the T11 spec.  My preference is for the ASCII string, but
there's no way to express that in a DISPLAY-HINT, and a DISPLAY-HINT
is optional.  Do you want me to add some text to the DESCRIPTION clause
to explain this ??

> 4. In T11ZoningName, what does 'letter' mean - ASCII only or
> internationalized as in SnmpAdminString? 
 
The REFERENCE clause points to section 6.4.8.1 of FC-GS-5, and
section 6.4.8.1.2 says:

   The Name Value field shall contain the ASCII characters that specify
   the name, not including any required fill bytes. Names shall adhere
   to the following rules:
    ...
    c) The first character of a given name shall be a letter. A letter
    is defined as either an upper case (A-Z) character or a lower case
    (a-z) character; and
    ...

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



From imss-bounces@ietf.org Mon Sep 18 16:01:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPPIv-0002N9-9G; Mon, 18 Sep 2006 16:01:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPPIt-0002M8-Sj
	for imss@ietf.org; Mon, 18 Sep 2006 16:01:19 -0400
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPPIs-0007eQ-HF
	for imss@ietf.org; Mon, 18 Sep 2006 16:01:19 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k8IJpGDE009659
	for <imss@ietf.org>; Mon, 18 Sep 2006 15:51:16 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [imss]
Date: Mon, 18 Sep 2006 23:01:11 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B4744C2@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [imss]
Thread-Index: AcbbVi+dtnITNxFNRw2WasBk50P4PQAA+AGg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Keith McCloghrie" <kzm@cisco.com>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: imss@ietf.org, Black_David@emc.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

Keith,

There is a lot of good stuff in your answer and proposals that are
acceptable for me.=20

I have only three comments in-line.=20

Dan



=20
=20

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]=20
> Sent: Monday, September 18, 2006 10:10 PM
> To: Romascanu, Dan (Dan)
> Cc: Black_David@emc.com; imss@ietf.org
> Subject: Re: [imss]
>=20
> Thanks for the comments.  My responses below.
>=20
> Keith.
> ---------------------------------
>=20
>
> >  draft-ietf-imss-fc-zs-mib-00.txt
> >=20

>=20
> > 2. It is not clear to me how t11FLockTable entries work in=20
> the case of=20
> > a non SNMP lock creation. How is a new row protected so=20
> that it will=20
> > not be manipulated by CLI while in SNMP creation and the=20
> other way? If=20
> > there are some assumptions about a common underCreation state, they=20
> > need to be clearly articulated.
>=20
> FC-GS-5 specifies how locks are created on receipt of an SSB,=20
> To avoid a conflict, the MIB needed to define how a lock can=20
> be created via SNMP, such that SNMP-management could modify=20
> the Zone Database without interference from the in-band=20
> management protocol, and vice-versa.  While defining a=20
> mechanism for SNMP, it seemed like a good idea to allow for=20
> locks by the CLI.
>=20
> A row in the table for the CLI works in the same way as a row=20
> in the table for the in-band management protocol, i.e., if a=20
> row in the t11FLockTable is created by SNMP, its value of=20
> t11FLockInitiatorType =3D 'snmp'.  If a row has its value of=20
> t11FLockInitiatorType =3D'cli' or 'ssb', then it cannot be=20
> deleted by SNMP.  So, there are no "assumptions about a=20
> common underCreation state".

OK, I understand this better now, although it's not easy reading for
somebody not familiar with T11. Two questions though:

- is it that 'it cannot be deleted by SNMP' or 'it cannot be deleted or
modified by SNMP'?=20
- what happens if a write operation is attempted on t11FLockRowStatus
while  t11FLockInitiatorType =3D'cli' or 'ssb'?



>=20
> > 3. I do not have the T11 reference at hand, but I wonder=20
> why objects=20
> > like t11FLockRejectReasonCodeExp have a SYNTAX of OCTET=20
> STRING. In any=20
> > case, I would suggest a DISPLAY-HINT clause for these.
> =20
> t11FLockRejectReasonCodeExp is a 1-byte hexadecimal value,=20
> with an ASCII string associated which each assigned value to=20
> indicate its meaning.
> So, if the list were stable, this would be an enumerated INTEGER.
> However, new reason codes get defined periodically, and it's=20
> unlikely that this WG will get re-chartered frequently enough=20
> to keep the enumerated values listed in the MIB uptodate. =20
> Nor do we want to impose a burden on IANA to assign new=20
> values, when new values are already being assigned in T11 and=20
> documented in T11 specifications.  Instead, the object has=20
> been defined an an "OCTET STRING (SIZE(1))" with a REFERENCE=20
> clause which points to the most recent spec for assigned values.
>=20
> So, I think that if anything is missing here, it's that there=20
> is no explicit indication in this MIB that values which will=20
> not yet assigned but will be assigned in future revisions of=20
> the Fibre Channel spec will then be valid in this object. =20
> Would you like me to append to the REFERENCE clause, something like:
>=20
>          ... or its successor"

Obviously there is a slight interoperability problem here, and I am not
sure that the IESG would like such a solution. Where does someone need
to look to see what is the more recent successor? Would not the overhead
of an IANA maintained TC be justified for such a case?=20

>=20
> In regard to a DISPLAY-HINT, there are two possible ways to=20
> display a value of this object: either as a hex value, or as=20
> the relevant ASCII string from the T11 spec.  My preference=20
> is for the ASCII string, but there's no way to express that=20
> in a DISPLAY-HINT, and a DISPLAY-HINT is optional.  Do you=20
> want me to add some text to the DESCRIPTION clause to explain this ??

One more reason to use a TC.=20


>=20
> > 4. In T11ZoningName, what does 'letter' mean - ASCII only or=20
> > internationalized as in SnmpAdminString?
> =20
> The REFERENCE clause points to section 6.4.8.1 of FC-GS-5,=20
> and section 6.4.8.1.2 says:
>=20
>    The Name Value field shall contain the ASCII characters=20
> that specify
>    the name, not including any required fill bytes. Names shall adhere
>    to the following rules:
>     ...
>     c) The first character of a given name shall be a letter. A letter
>     is defined as either an upper case (A-Z) character or a lower case
>     (a-z) character; and
>     ...
>=20

Can we copy this text here? I believe that it's better to be redundant
then use such a common noun as 'letter' and assume that the writer of a
future application will read the reference.=20

Dan


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



From imss-bounces@ietf.org Mon Sep 18 22:00:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPUud-0003na-Kd; Mon, 18 Sep 2006 22:00:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPUuc-0003mc-Vi
	for imss@ietf.org; Mon, 18 Sep 2006 22:00:38 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPUub-0001Ia-BO
	for imss@ietf.org; Mon, 18 Sep 2006 22:00:38 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 18 Sep 2006 19:00:36 -0700
X-IronPort-AV: i="4.09,183,1157353200"; 
	d="scan'208"; a="322619916:sNHT37216384"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8J20aTw019003; Mon, 18 Sep 2006 19:00:36 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k8J20aw7029593;
	Mon, 18 Sep 2006 19:00:36 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id SAA28294;
	Mon, 18 Sep 2006 18:59:28 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609190159.SAA28294@cisco.com>
Subject: Re: [imss]
To: dromasca@avaya.com
Date: Mon, 18 Sep 2006 18:59:28 -0700 (PDT)
In-Reply-To: <no.id> from "Romascanu, Dan \(Dan\)" at Sep 18, 2006 11:01:11 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=6032; t=1158631236; x=1159495236;
	c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:Re=3A=20[imss];
	X=v=3Dcisco.com=3B=20h=3DNv4KD+jbB7gOEwMz11rNHW3/RuA=3D;
	b=GB2brp3Tib0bXtz0p9NCecCXx1Q+0B1baqzqHDIx81Tpm5DH6J4Ol2m42NyWzCSkZDT5uuZn
	74hJWePiLVLOEwF+37sylR0o/Dkw0xFXFd4ZctKAkCyhD9JJz13jijWr;
Authentication-Results: sj-dkim-5.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: imss@ietf.org, Keith McCloghrie <kzm@cisco.com>, Black_David@emc.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

Dan,

> > >  draft-ietf-imss-fc-zs-mib-00.txt
> > > 
> > > 2. It is not clear to me how t11FLockTable entries work in 
> > the case of 
> > > a non SNMP lock creation. How is a new row protected so 
> > that it will 
> > > not be manipulated by CLI while in SNMP creation and the 
> > other way? If 
> > > there are some assumptions about a common underCreation state, they 
> > > need to be clearly articulated.
> > 
> > FC-GS-5 specifies how locks are created on receipt of an SSB, 
> > To avoid a conflict, the MIB needed to define how a lock can 
> > be created via SNMP, such that SNMP-management could modify 
> > the Zone Database without interference from the in-band 
> > management protocol, and vice-versa.  While defining a 
> > mechanism for SNMP, it seemed like a good idea to allow for 
> > locks by the CLI.
> > 
> > A row in the table for the CLI works in the same way as a row 
> > in the table for the in-band management protocol, i.e., if a 
> > row in the t11FLockTable is created by SNMP, its value of 
> > t11FLockInitiatorType = 'snmp'.  If a row has its value of 
> > t11FLockInitiatorType ='cli' or 'ssb', then it cannot be 
> > deleted by SNMP.  So, there are no "assumptions about a 
> > common underCreation state".
> 
> OK, I understand this better now, although it's not easy reading for
> somebody not familiar with T11.  Two questions though:
> 
> - is it that 'it cannot be deleted by SNMP' or 'it cannot be deleted or
> modified by SNMP'? 

You're right -- I should change the words in t11FLockRowStatus's
DESCRIPTION to say "modified or deleted".

> - what happens if a write operation is attempted on t11FLockRowStatus
> while t11FLockInitiatorType ='cli' or 'ssb'?

An instance of t11FLockRowStatus *can* be deleted/modified under other
circumstances, but not while the value of t11FLockInitiatorType in the
same row has the value 'cli' or 'ssb'.

So, it would be more precise for the DESCRIPTION to say:

           A row of this table can be modified or deleted via this
           object only when the row's value of t11FLockInitiatorType
           is 'snmp'."

> > > 3. I do not have the T11 reference at hand, but I wonder 
> > why objects 
> > > like t11FLockRejectReasonCodeExp have a SYNTAX of OCTET 
> > STRING. In any 
> > > case, I would suggest a DISPLAY-HINT clause for these.
> >  
> > t11FLockRejectReasonCodeExp is a 1-byte hexadecimal value, 
> > with an ASCII string associated which each assigned value to 
> > indicate its meaning.
> > So, if the list were stable, this would be an enumerated INTEGER.
> > However, new reason codes get defined periodically, and it's 
> > unlikely that this WG will get re-chartered frequently enough 
> > to keep the enumerated values listed in the MIB uptodate.  
> > Nor do we want to impose a burden on IANA to assign new 
> > values, when new values are already being assigned in T11 and 
> > documented in T11 specifications.  Instead, the object has 
> > been defined an an "OCTET STRING (SIZE(1))" with a REFERENCE 
> > clause which points to the most recent spec for assigned values.
> > 
> > So, I think that if anything is missing here, it's that there 
> > is no explicit indication in this MIB that values which will 
> > not yet assigned but will be assigned in future revisions of 
> > the Fibre Channel spec will then be valid in this object.  
> > Would you like me to append to the REFERENCE clause, something like:
> > 
> >          ... or its successor"
> 
> Obviously there is a slight interoperability problem here, and I am not
> sure that the IESG would like such a solution. Where does someone need
> to look to see what is the more recent successor? Would not the overhead
> of an IANA maintained TC be justified for such a case? 

No, I don't believe so.  A user who can't find the latest T11 spec, is
not going to know what a new reason code means anyway.  This is the
equivalent of an Internet user who can't find the latest RFC.  With the
current definition, IANA is not involved.  Getting IANA involved is not
only extra overhead, but it also increases the need for coordination,
and consequently, it increases the chance of a screw-up in the
coordination of changes between multiple organizations.

The way that it is defined at present is simple, and that's good :-).

> > In regard to a DISPLAY-HINT, there are two possible ways to 
> > display a value of this object: either as a hex value, or as 
> > the relevant ASCII string from the T11 spec.  My preference 
> > is for the ASCII string, but there's no way to express that 
> > in a DISPLAY-HINT, and a DISPLAY-HINT is optional.  Do you 
> > want me to add some text to the DESCRIPTION clause to explain this ??
> 
> One more reason to use a TC. 

I see the opposite, i.e., the fact that a DISPLAY-HINT is not rich
enough to express the desired hint is one more reason not to use a TC.

> > > 4. In T11ZoningName, what does 'letter' mean - ASCII only or 
> > > internationalized as in SnmpAdminString?
> >  
> > The REFERENCE clause points to section 6.4.8.1 of FC-GS-5, 
> > and section 6.4.8.1.2 says:
> > 
> >    The Name Value field shall contain the ASCII characters 
> > that specify
> >    the name, not including any required fill bytes. Names shall adhere
> >    to the following rules:
> >     ...
> >     c) The first character of a given name shall be a letter. A letter
> >     is defined as either an upper case (A-Z) character or a lower case
> >     (a-z) character; and
> >     ...
> 
> Can we copy this text here? I believe that it's better to be redundant
> then use such a common noun as 'letter' and assume that the writer of a
> future application will read the reference. 

The only information in the text I quoted, that's not already in the
DESCRIPTION is the fact that it is an ASCII letter.  So, yes, I'll
change "letter" to "ASCII letter" and then it will no longer be a
common noun.

Keith.

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



From imss-bounces@ietf.org Tue Sep 19 01:33:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GPYEU-0000hr-6M; Tue, 19 Sep 2006 01:33:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GPYES-0000hg-8n
	for imss@ietf.org; Tue, 19 Sep 2006 01:33:20 -0400
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPYEQ-0002aS-Ln
	for imss@ietf.org; Tue, 19 Sep 2006 01:33:20 -0400
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id k8J5PbrC005620
	for <imss@ietf.org>; Tue, 19 Sep 2006 01:25:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [imss]
Date: Tue, 19 Sep 2006 08:33:11 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0B47459F@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [imss]
Thread-Index: Acbbj4azYhC6dXuxTRq6HR+3fOO4AgAHMf9g
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Keith McCloghrie" <kzm@cisco.com>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: imss@ietf.org, Black_David@emc.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

Keith,

OK with me by now. The only issue I am not 100% comfortable yet is the
syntax of the reason code objects, but I would say that we discussed
this enough for this stage. Later reviews with the MIB doctors and IESG
will prove if the current proposal holds water from the point of view of
operability and extensibility.=20

Dan

=20
=20

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]=20
> Sent: Tuesday, September 19, 2006 4:59 AM
> To: Romascanu, Dan (Dan)
> Cc: Keith McCloghrie; Black_David@emc.com; imss@ietf.org
> Subject: Re: [imss]
>=20
> Dan,
>=20
> > > >  draft-ietf-imss-fc-zs-mib-00.txt
> > > >=20
> > > > 2. It is not clear to me how t11FLockTable entries work in
> > > the case of
> > > > a non SNMP lock creation. How is a new row protected so
> > > that it will
> > > > not be manipulated by CLI while in SNMP creation and the
> > > other way? If
> > > > there are some assumptions about a common underCreation state,=20
> > > > they need to be clearly articulated.
> > >=20
> > > FC-GS-5 specifies how locks are created on receipt of an SSB, To=20
> > > avoid a conflict, the MIB needed to define how a lock can=20
> be created=20
> > > via SNMP, such that SNMP-management could modify the Zone=20
> Database=20
> > > without interference from the in-band management protocol, and=20
> > > vice-versa.  While defining a mechanism for SNMP, it=20
> seemed like a=20
> > > good idea to allow for locks by the CLI.
> > >=20
> > > A row in the table for the CLI works in the same way as a=20
> row in the=20
> > > table for the in-band management protocol, i.e., if a row in the=20
> > > t11FLockTable is created by SNMP, its value of=20
> t11FLockInitiatorType=20
> > > =3D 'snmp'.  If a row has its value of=20
> t11FLockInitiatorType =3D'cli' or=20
> > > 'ssb', then it cannot be deleted by SNMP.  So, there are no=20
> > > "assumptions about a common underCreation state".
> >=20
> > OK, I understand this better now, although it's not easy=20
> reading for=20
> > somebody not familiar with T11.  Two questions though:
> >=20
> > - is it that 'it cannot be deleted by SNMP' or 'it cannot=20
> be deleted=20
> > or modified by SNMP'?
>=20
> You're right -- I should change the words in=20
> t11FLockRowStatus's DESCRIPTION to say "modified or deleted".
>=20
> > - what happens if a write operation is attempted on=20
> t11FLockRowStatus=20
> > while t11FLockInitiatorType =3D'cli' or 'ssb'?
>=20
> An instance of t11FLockRowStatus *can* be deleted/modified=20
> under other circumstances, but not while the value of=20
> t11FLockInitiatorType in the same row has the value 'cli' or 'ssb'.
>=20
> So, it would be more precise for the DESCRIPTION to say:
>=20
>            A row of this table can be modified or deleted via this
>            object only when the row's value of t11FLockInitiatorType
>            is 'snmp'."
>=20
> > > > 3. I do not have the T11 reference at hand, but I wonder
> > > why objects
> > > > like t11FLockRejectReasonCodeExp have a SYNTAX of OCTET
> > > STRING. In any
> > > > case, I would suggest a DISPLAY-HINT clause for these.
> > > =20
> > > t11FLockRejectReasonCodeExp is a 1-byte hexadecimal=20
> value, with an=20
> > > ASCII string associated which each assigned value to indicate its=20
> > > meaning.
> > > So, if the list were stable, this would be an enumerated INTEGER.
> > > However, new reason codes get defined periodically, and it's=20
> > > unlikely that this WG will get re-chartered frequently enough to=20
> > > keep the enumerated values listed in the MIB uptodate.
> > > Nor do we want to impose a burden on IANA to assign new=20
> values, when=20
> > > new values are already being assigned in T11 and=20
> documented in T11=20
> > > specifications.  Instead, the object has been defined an=20
> an "OCTET=20
> > > STRING (SIZE(1))" with a REFERENCE clause which points to=20
> the most=20
> > > recent spec for assigned values.
> > >=20
> > > So, I think that if anything is missing here, it's that=20
> there is no=20
> > > explicit indication in this MIB that values which will not yet=20
> > > assigned but will be assigned in future revisions of the Fibre=20
> > > Channel spec will then be valid in this object.
> > > Would you like me to append to the REFERENCE clause,=20
> something like:
> > >=20
> > >          ... or its successor"
> >=20
> > Obviously there is a slight interoperability problem here, and I am=20
> > not sure that the IESG would like such a solution. Where=20
> does someone=20
> > need to look to see what is the more recent successor?=20
> Would not the=20
> > overhead of an IANA maintained TC be justified for such a case?
>=20
> No, I don't believe so.  A user who can't find the latest T11=20
> spec, is not going to know what a new reason code means=20
> anyway.  This is the equivalent of an Internet user who can't=20
> find the latest RFC.  With the current definition, IANA is=20
> not involved.  Getting IANA involved is not only extra=20
> overhead, but it also increases the need for coordination,=20
> and consequently, it increases the chance of a screw-up in=20
> the coordination of changes between multiple organizations.
>=20
> The way that it is defined at present is simple, and that's good :-).
>=20
> > > In regard to a DISPLAY-HINT, there are two possible ways=20
> to display=20
> > > a value of this object: either as a hex value, or as the relevant=20
> > > ASCII string from the T11 spec.  My preference is for the ASCII=20
> > > string, but there's no way to express that in a=20
> DISPLAY-HINT, and a=20
> > > DISPLAY-HINT is optional.  Do you want me to add some text to the=20
> > > DESCRIPTION clause to explain this ??
> >=20
> > One more reason to use a TC.=20
>=20
> I see the opposite, i.e., the fact that a DISPLAY-HINT is not=20
> rich enough to express the desired hint is one more reason=20
> not to use a TC.
>=20
> > > > 4. In T11ZoningName, what does 'letter' mean - ASCII only or=20
> > > > internationalized as in SnmpAdminString?
> > > =20
> > > The REFERENCE clause points to section 6.4.8.1 of FC-GS-5, and=20
> > > section 6.4.8.1.2 says:
> > >=20
> > >    The Name Value field shall contain the ASCII characters that=20
> > > specify
> > >    the name, not including any required fill bytes. Names=20
> shall adhere
> > >    to the following rules:
> > >     ...
> > >     c) The first character of a given name shall be a=20
> letter. A letter
> > >     is defined as either an upper case (A-Z) character or=20
> a lower case
> > >     (a-z) character; and
> > >     ...
> >=20
> > Can we copy this text here? I believe that it's better to=20
> be redundant=20
> > then use such a common noun as 'letter' and assume that the=20
> writer of=20
> > a future application will read the reference.
>=20
> The only information in the text I quoted, that's not already=20
> in the DESCRIPTION is the fact that it is an ASCII letter. =20
> So, yes, I'll change "letter" to "ASCII letter" and then it=20
> will no longer be a common noun.
>=20
> Keith.
>=20

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



From imss-bounces@ietf.org Tue Sep 26 14:14:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSHRV-0001G0-U8; Tue, 26 Sep 2006 14:14:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSHRU-0001Fu-KU
	for imss@ietf.org; Tue, 26 Sep 2006 14:14:04 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSHRT-0006ZO-68
	for imss@ietf.org; Tue, 26 Sep 2006 14:14:04 -0400
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-5.cisco.com with ESMTP; 26 Sep 2006 11:14:02 -0700
X-IronPort-AV: i="4.09,221,1157353200"; 
	d="scan'208"; a="325515912:sNHT37320362"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8QIE29G027125; Tue, 26 Sep 2006 11:14:02 -0700
Received: from cisco.com (pita.cisco.com [171.71.177.199])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k8QIDoid011043;
	Tue, 26 Sep 2006 11:13:54 -0700 (PDT)
Received: (from kzm@localhost)
	by cisco.com (8.8.8-Cisco List Logging/8.8.8) id LAA20415;
	Tue, 26 Sep 2006 11:12:36 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200609261812.LAA20415@cisco.com>
To: bwijnen@lucent.com
Date: Tue, 26 Sep 2006 11:12:36 -0700 (PDT)
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Sep 06, 2006 02:51:38 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=4390; t=1159294442; x=1160158442;
	c=relaxed/relaxed; s=sjdkim8002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kzm@cisco.com;
	z=From:Keith=20McCloghrie=20<kzm@cisco.com>
	|Subject:A=20couple=20of=20loose=20ends;
	X=v=3Dcisco.com=3B=20h=3D7eLSnJFqNd1g+cggcsXn9NgTasA=3D;
	b=iyShgpFnTW71TiXVgLxaXK5PwXAjEX62peid0RItCum9E1Ynp2NCfv7t6P3ZAEG+JpltSzEj
	s8XjU90WzykWTG9QtzmjX5ptCGpnoyUQBQQXr7M1pg9YWYRzM5CF384o;
Authentication-Results: sj-dkim-8.cisco.com; header.From=kzm@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: imss@ietf.org, Keith McCloghrie <kzm@cisco.com>
Subject: [imss] A couple of loose ends
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

Bert,

In order to make further progress in updating the text of the I-D's,
there are two loose ends that I would like to resolve.

One is:

> From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> To: Keith McCloghrie <kzm@cisco.com>
> Cc: imss@ietf.org
> Subject: RE: [imss] WG Last Call: draft-ietf-imss-fc-fcs-mib-00.txt
> Date: Wed, 6 Sep 2006 14:51:38 +0200 
> 
> ...
>
> > >   t11FcsMgmtAddr  OBJECT-TYPE
> > >     SYNTAX       SnmpAdminString
> > >     MAX-ACCESS   read-only
> > >     STATUS       current
> > >     DESCRIPTION
> > >             "The management address of this entry.
> > >             The format of this object may be based on the
> > >             format of the Uniform Resource Locator (URL).
> > >             For example, for SNMP, see RFC 4088."
> > > 
> > >   So it syas "the format MAY be based on..." (my emphasis on MAY).
> > >   So, does that mean it may also be based on something else?
> > >   How do I determine what the actual format is?
> >  
> > On re-reading FC-GS-5, I see that it's required to be a URL, and
> > it's the use of 4088 which is not required.  So, I'll change it to:
> > 
> >             The format of this object is a Uniform Resource Locator
> >             (URL), e.g., for SNMP, see RFC 4088."
> 
> But is a URL normally represented by UTF-8?
> I doubt it?
> 
> I know that (RFC 2788) has:
> 
>   -- Uniform Resource Locators are stored in URLStrings.
> 
>   URLString ::= TEXTUAL-CONVENTION
>       DISPLAY-HINT "255a"
>       STATUS current
>       DESCRIPTION
>           "A Uniform Resource Locator represented in accordance
>            with RFCs 1738 and 2368, presented in the NVT ASCII
>            charset defined in RFC 854."
>       SYNTAX OCTET STRING (SIZE (0..255))
> 
> Would that not be more appropriate?

Yes, I am changing t11FcsMgmtAddr's syntax to be URLString.

The other loose end is:

> From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> To: Black_David@emc.com, imss@ietf.org
> Date: Thu, 7 Sep 2006 17:50:44 +0200
> Cc: dromasca@avaya.com
> Subject: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
>       draft-ietf-imss-fc-zs-mib-00.txt
>
> ...
>
> - Reading:
>
>    t11FLockRowStatus OBJECT-TYPE
>       SYNTAX        RowStatus
>       MAX-ACCESS    read-create
>       STATUS        current
>       DESCRIPTION
>            "The status of this conceptual row.
>
>            A row for which the value of t11FLockInitiatorType is
>            not 'snmp' cannot be deleted via this object."
>
>   I wonder:
>   - can a row be set to notReady or notInservice for rows that
>     were not created by 'snmp'? I guess not, but one could get
>     the impression that such is possible based on this one
>     sentence
>   - What is the persistence behaviour of a row created via snmp?
>     Probably nonVolatile? But would be good to say something
>     about it.
>
> - SO I see:
>
>     t11FLockStatus OBJECT-TYPE
>         SYNTAX        INTEGER {
>                       active(1),
>                       settingUp(2),
>                       rejectFailure(3),
>                       otherFailure(4)
>                   }
>
>   and wonder what will happen if the lock gets released?
>   not sure I understand how such happens, but I would assume a lock does
>   not stay forever once it has become active, does it?
>   Does the entry disappear in that case?

I think the issue is that the current text in the MIB is not explicit
enough in explaining when rows exist in the table.  In reviewing your
comments and determining how to update the text to address them, I'm
now planning to provide a more explicit explanation by adding this text
to the DESCRIPTION of the t11FLockTable:

           Each entry in this table represents either:

           1) a current fabric lock,
           2) an in-progress attempt, requested via SNMP, to setup
              a lock, or
           3) a failed attempt, requested via SNMP, to setup a lock.

           If an entry is created via t11FLockRowStatus but the
           attempt to obtain the lock fails, then the entry continues
           to exist until it is deleted via t11FLockRowStatus, or
           it is overwritten by the lock being established via
           a means other than SNMP, but note that rows created via
           SNMP are not retained over restarts."

A purist might argue that this design has a single table for two functions:
1) for current locks, and 2) SNMP attenpts to setup a lock, which should
be kept in separate tables, so that the "overwritten by the lock being
established via a means other than SNMP" could not happen, but I don't
think the "overwritten" is a large enough issue to warrant the extra
complication of two tables.  D'you agree ?

So, I see the addition of the above text as a clarification, not as a change.

Keith.

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



From imss-bounces@ietf.org Tue Sep 26 20:18:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSN84-0000q3-Ot; Tue, 26 Sep 2006 20:18:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSN84-0000py-8N
	for imss@ietf.org; Tue, 26 Sep 2006 20:18:24 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSN82-0004d8-SF
	for imss@ietf.org; Tue, 26 Sep 2006 20:18:24 -0400
Received: from mailhub.lss.emc.com (nirah.lss.emc.com [10.254.144.13])
	by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	k8R0IKvQ013914
	for <imss@ietf.org>; Tue, 26 Sep 2006 20:18:20 -0400 (EDT)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com
	[10.254.64.53])
	by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k8R0II29023310
	for <imss@ietf.org>; Tue, 26 Sep 2006 20:18:18 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by
	corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.0); 
	Tue, 26 Sep 2006 20:18:18 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Sep 2006 20:18:13 -0400
Message-ID: <F222151D3323874393F83102D614E05502B6741A@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MIB Last Call Results and Fabric Config Server MIB Design Issue
Thread-Index: Acbhymu1V+8N2FYhTXiYQzr+OQJPcg==
To: <imss@ietf.org>
X-OriginalArrivalTime: 27 Sep 2006 00:18:18.0202 (UTC)
	FILETIME=[6E9C53A0:01C6E1CA]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935,
	Antispam-Data: 2006.9.26.165443
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2,
	NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTE 0,
	__CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0,
	__IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0,
	__SANE_MSGID 0'
X-Spam-Score: 0.2 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: Black_David@emc.com
Subject: [imss] MIB Last Call Results and Fabric Config Server MIB Design
	Issue
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

The imss WG last call on the Fibre Channel RSCN, Fabric
Config Server, and Zone Server MIBs has certainly been
interesting, and I want to thank Bert Wijnen and Dan Romascanu
for spending time on these MIBs at this juncture - it should
help significantly in dealing with these MIBs after they
leave the WG.

For now, these MIBs are here in the imss WG.  While I saw a
lot of Last Call issues on MIB syntax, I only saw one significant
technical issue on the table structure in the Fabric Config Server
MIB (see below).  That technical issue appears sufficiently
contained (it's about MIB table structure, and does not affect
function) that I don't believe a second WG Last Call will be
needed once a resolution is determined.  So, all three MIBs
are through WG Last call, but new versions of all three MIB
drafts will be needed to check that the significant number of
issues found by Dan and Bert have been addressed.  Those will
probably show up after the T11 meetings next week because ...

We(I) also have some things to address with T11.  The good
news is that not only is FC-GS-5 now a stable reference, but
also based on my discussions with the responsible T11 people,
the "Ugly" issue 3) should be resolved by formal T11 action
next week that should produce an archive document containing
the required FC-SW-5 allocation (which can then be cited in
a REFERENCE clause).  That issue was:

	T11 does not have an IANA equivalent, and
	hence we will need to come up with something to
	formalize the allocation and record it in some-
	thing reference-able prior to FC-SW-5 putting in
	an appearance.

The remaining T11 issue is the status/stability of FC-LS,
and I will report back to the WG on that after the T11
meetings next week.

That leaves one technical issue that needs attention here:

----------------
> Bert Wijnen
Keith McCloghrie

> - SMICng gave a warning about the indexing of
>=20
>   t11FcsPortListEntry  OBJECT-TYPE
>     SYNTAX       T11FcsPortListEntry
>     MAX-ACCESS   not-accessible
>     STATUS       current
>     DESCRIPTION
>             "An entry which identifies that the port which has the
>             port name, t11FcsPortName, is in a particular list of
>             ports, which is known to a switch (identified by
>             fcmInstanceIndex and fcmSwitchIndex)."
>     INDEX   { fcmInstanceIndex,  fcmSwitchIndex,
>               t11FcsPortListIndex, t11FcsPortName }
>     ::=3D { t11FcsPortListTable 1 }
>=20
>   I read Keiths explanation, which seemed fine. But now that I am
>   reviewing the MIB module in details and try to understand things,
>   now I am no so sure this is goodness.
>=20
>   So, that t11FcsPortname is a value (embedded in the index) that
>   should help me find more detailed info, right?
>   So how do I find that info? I think I need to go to the
>   t11FcsPortTable, which is indexed by:
>=20
>     INDEX   { fcmInstanceIndex, fcmSwitchIndex,
>               t11FcsFabricIndex, t11FcsPortName }
>=20
>   So assuming that the index values for fcmInstanceIndex,
fcmSwitchIndex,
>   are the same in both tables, I can see that I can pick up 3 index
>   values from the list of t11FcsPortsList in the t11FcsPortsListTable.
>   But I am missing the 3rd index of the t11FcsPortnameTable, namely
>   t11FcsFabricIndex. So how am I going to wuickly pick that up?
>   Or how exactly are the tables connected/linked?
>=20
>   Maybe I need to study it deeper... but I'd prefer an explanation of
>   the people who created these tables with the current indexing
schemes.
=20
To generate an answer to your question, I needed to re-review the
structure of the tables, and in doing so, I now think that the current
structure is more open-ended/flexible than it needs to be -- having a
less open-ended structure would make the MIB simpler.  Specifically,
the MIB currently has a table whose only purpose is to identify a list
of (not necessarily related) ports.  However,

- each IE is either a virtual IE attached to one virtual Fabric, or
  (if virtual Fabrics are not in use) it's a physical IE.
- each port is either a virtual port attached to one virtual Fabric, or
  (if virtual Fabrics are not in use) it's a physical port.
- GS-5 mentions that an IE has a "port list" and has a dotted line from
the
  "Interconnect Element Object" to the "Port Object" in its "Figure 7 --
  Interconnect Element and Port attributes".
- However, all ports in an IE's port list will be attached to the same=20
  Fabric as that IE is attached to.  In other words, the relationship
  between IEs and ports is hierarchical.
- Thus, it would be simpler to:

  - delete the t11FcsPortListTable,
  - delete the t11FcsIePortListIndex object, and
  - insert t11FcsIeName into the INDEX of the t11FcsPortTable, i.e.,
    change the INDEX-ing of the t11FcsPortTable to be:

      INDEX   { fcmInstanceIndex, fcmSwitchIndex, t11FcsFabricIndex,
                t11FcsIeName, t11FcsPortName }

Increasing the INDEX clause from four to five objects makes it a little
more cumbersome, but the length is still far short of the maximum
length.

With these changes, while there will no longer be any explicit mention
of a "port list" in the MIB, the list of ports on an IE will be all
the rows in t11FcsPortTable which have the same values for the first
four index objects, i.e., the value of t11FcsPortName will be the only
index value for which they differ.  So, a "port list" is (implicitly)
a set of adjacent rows in the t11FcsPortTable.

-----------------

This looks like a desirable simplification to me (taking out one
table), but the purpose of this email is to solicit comments from
others on this mailing list.  Please comment within the next week.

Thanks,
--David (imss WG chair)
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

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



From imss-bounces@ietf.org Thu Sep 28 06:18:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSsyV-0002jX-Pe; Thu, 28 Sep 2006 06:18:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSsyU-0002jS-2T
	for imss@ietf.org; Thu, 28 Sep 2006 06:18:38 -0400
Received: from ihemail3.lucent.com ([135.245.0.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSsyS-0000pc-Nl
	for imss@ietf.org; Thu, 28 Sep 2006 06:18:38 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail3.lucent.com (8.13.6/IER-o) with ESMTP id k8SAIUSv006243;
	Thu, 28 Sep 2006 05:18:31 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <R9BL21V1>; Thu, 28 Sep 2006 12:18:29 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550AC49564@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Keith McCloghrie <kzm@cisco.com>
Date: Thu, 28 Sep 2006 12:18:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: imss@ietf.org
Subject: [imss] RE: A couple of loose ends
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

These suggested resolutions seem fine to me.
My main objective of my comments was to get things
clear enough so that other people (and also I myself)
can understand how things are supposed to work.

Bert

> -----Original Message-----
> From: Keith McCloghrie [mailto:kzm@cisco.com]
> Sent: Tuesday, September 26, 2006 19:13
> To: bwijnen@lucent.com
> Cc: kzm@cisco.com; imss@ietf.org
> Subject: A couple of loose ends
> 
> 
> Bert,
> 
> In order to make further progress in updating the text of the I-D's,
> there are two loose ends that I would like to resolve.
> 
> One is:
> 
> > From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> > To: Keith McCloghrie <kzm@cisco.com>
> > Cc: imss@ietf.org
> > Subject: RE: [imss] WG Last Call: draft-ietf-imss-fc-fcs-mib-00.txt
> > Date: Wed, 6 Sep 2006 14:51:38 +0200 
> > 
> > ...
> >
> > > >   t11FcsMgmtAddr  OBJECT-TYPE
> > > >     SYNTAX       SnmpAdminString
> > > >     MAX-ACCESS   read-only
> > > >     STATUS       current
> > > >     DESCRIPTION
> > > >             "The management address of this entry.
> > > >             The format of this object may be based on the
> > > >             format of the Uniform Resource Locator (URL).
> > > >             For example, for SNMP, see RFC 4088."
> > > > 
> > > >   So it syas "the format MAY be based on..." (my 
> emphasis on MAY).
> > > >   So, does that mean it may also be based on something else?
> > > >   How do I determine what the actual format is?
> > >  
> > > On re-reading FC-GS-5, I see that it's required to be a URL, and
> > > it's the use of 4088 which is not required.  So, I'll 
> change it to:
> > > 
> > >             The format of this object is a Uniform 
> Resource Locator
> > >             (URL), e.g., for SNMP, see RFC 4088."
> > 
> > But is a URL normally represented by UTF-8?
> > I doubt it?
> > 
> > I know that (RFC 2788) has:
> > 
> >   -- Uniform Resource Locators are stored in URLStrings.
> > 
> >   URLString ::= TEXTUAL-CONVENTION
> >       DISPLAY-HINT "255a"
> >       STATUS current
> >       DESCRIPTION
> >           "A Uniform Resource Locator represented in accordance
> >            with RFCs 1738 and 2368, presented in the NVT ASCII
> >            charset defined in RFC 854."
> >       SYNTAX OCTET STRING (SIZE (0..255))
> > 
> > Would that not be more appropriate?
> 
> Yes, I am changing t11FcsMgmtAddr's syntax to be URLString.
> 
> The other loose end is:
> 
> > From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> > To: Black_David@emc.com, imss@ietf.org
> > Date: Thu, 7 Sep 2006 17:50:44 +0200
> > Cc: dromasca@avaya.com
> > Subject: [imss] WG last call review: T11-FC-FABRIC-LOCK-MIB in
> >       draft-ietf-imss-fc-zs-mib-00.txt
> >
> > ...
> >
> > - Reading:
> >
> >    t11FLockRowStatus OBJECT-TYPE
> >       SYNTAX        RowStatus
> >       MAX-ACCESS    read-create
> >       STATUS        current
> >       DESCRIPTION
> >            "The status of this conceptual row.
> >
> >            A row for which the value of t11FLockInitiatorType is
> >            not 'snmp' cannot be deleted via this object."
> >
> >   I wonder:
> >   - can a row be set to notReady or notInservice for rows that
> >     were not created by 'snmp'? I guess not, but one could get
> >     the impression that such is possible based on this one
> >     sentence
> >   - What is the persistence behaviour of a row created via snmp?
> >     Probably nonVolatile? But would be good to say something
> >     about it.
> >
> > - SO I see:
> >
> >     t11FLockStatus OBJECT-TYPE
> >         SYNTAX        INTEGER {
> >                       active(1),
> >                       settingUp(2),
> >                       rejectFailure(3),
> >                       otherFailure(4)
> >                   }
> >
> >   and wonder what will happen if the lock gets released?
> >   not sure I understand how such happens, but I would 
> assume a lock does
> >   not stay forever once it has become active, does it?
> >   Does the entry disappear in that case?
> 
> I think the issue is that the current text in the MIB is not explicit
> enough in explaining when rows exist in the table.  In reviewing your
> comments and determining how to update the text to address them, I'm
> now planning to provide a more explicit explanation by adding 
> this text
> to the DESCRIPTION of the t11FLockTable:
> 
>            Each entry in this table represents either:
> 
>            1) a current fabric lock,
>            2) an in-progress attempt, requested via SNMP, to setup
>               a lock, or
>            3) a failed attempt, requested via SNMP, to setup a lock.
> 
>            If an entry is created via t11FLockRowStatus but the
>            attempt to obtain the lock fails, then the entry continues
>            to exist until it is deleted via t11FLockRowStatus, or
>            it is overwritten by the lock being established via
>            a means other than SNMP, but note that rows created via
>            SNMP are not retained over restarts."
> 
> A purist might argue that this design has a single table for 
> two functions:
> 1) for current locks, and 2) SNMP attenpts to setup a lock, 
> which should
> be kept in separate tables, so that the "overwritten by the lock being
> established via a means other than SNMP" could not happen, but I don't
> think the "overwritten" is a large enough issue to warrant the extra
> complication of two tables.  D'you agree ?
> 
> So, I see the addition of the above text as a clarification, 
> not as a change.
> 
> Keith.
> 

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



