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

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Mon, 04 September 2006 11:02 UTC

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, 04 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