Re: [imss] imss WG Last Call: Fibre Channel RSCN, Fabric Config S

[Keith McCloghrie <[e-mail]>]

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
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/imss
> 

_______________________________________________
imss mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/imss