Re: draft-ietf-ipoib-subnet-manager-mib-00.txt

Hal,

Sorry for the late reply.  Thank you so much for the valuable input.  
Here are my comments:

Cheng Yang


Hal Rosenstock wrote:

>Hi Cheng,
>
>Looks good. I have some comments on this MIB:
>
>Here are some general comments and questions:
>
>It is not just a subnet manager but also subnet administration MIB. Should
>it be noted that it includes support for SA as well as SM in the overview
>(section 4) ?
>  
>
Ok, that can be added.  We include some "essential" SA management 
features in this MIB.

>Should Reversible be included in (both) the path and multipath request ?
>  
>
It should behave the same as SA operations.  So reversible path should 
be there.

>It appears that service associations are creatable and deletable via SNMP
>management. Isn't this at odds with IB ?
>  
>
As we understand, service associations creation and deletion are being 
managed by out-of-band
applications instead of IB nodes itself.  The IB spec never specified 
how service assication records are
being created.  So it's up to the SM/SA to set this thing up to restrict 
the use of ServiceRecord.
see page 795 of the IB spec v1.1.

>Should the ability to create/delete multicast groups/members be supported by
>management (proxy) ?
>  
>
IB spec here never specified how MC groups are being created.  We'll 
keep this thing open for discussion for now.

>An inform info information group to see what nodes are subscribed to what
>traps/notices might be useful.
>  
>
Do you have an application which can utilize this information?  We are 
not trying to include all management
elements of SM/SA in the MIB, because it's simply too much.  If you can 
find an application that "requires"
this information, we can consider adding it.  Otherwise, we hate to 
design/implement something that no one's going
to use.

>Should there be a LEDInfo information group ?
>
>  
>
Same as above. 

>Despite the current lack of interest, shouldn't the CA SL to VL map table,
>Switch SL to VL map table and VL arbitration table be included so this MIB
>won't need to be rev'd in the future when these become of interest ?
>  
>
Same as above.

>Here are some nits:
>
>Should ibSmPortInfoCapMask (p.16,17) isConnectionManagerSupported be named
>IsCommunicationManagementSupported ?
>
>  
>
Corrected in next version.

>Should ibSmPortInfoOperVL (p. 23) have a 0 (no change) value ?
>  
>
Could you please educate me why this is a fix 0 value?  Maybe I'm 
missing something in the spec.

>Should valid values for ibSmSwitchInfoLinearFdbCap and
>ibSmSwitchInfoRandomFdbCap (p. 28) be 0...49151 rather than 0..65535 ?
>Similarly for ibSmSwitchInfoLinearFdbTop (p. 29)
>
>  
>
Corrected in next version.

>Should valid values for ibSmSwitchInfoMcastFdbCap (p.29) be 0...16383 rather
>than 0...65535 ?
>
>  
>
Corrected.

>typo comparion should be comparison in ibSmPartitionLastChange (p. 33)
>  
>
Corrected.

>Should the description of ibSmPathReqTable (p. 45) say
>"A table used to list all the path entries that satisfy the path request"
>rather than
>"A table used to list all the path entries that satisfy the multi path
>request"
>
>  
>
Corrected.

>-- Hal
>
>----- Original Message -----
>From: "Cheng Yang" <[email protected]>
>To: <[email protected]>; <[email protected]>
>Cc: "Edwin Tsang" <[email protected]>; "Carl Yang" <[email protected]>; "Bill
>Strahm" <[email protected]>
>Sent: Friday, March 05, 2004 1:15 PM
>Subject: [Ipoverib] draft-ietf-ipoib-subnet-manager-mib-00.txt
>
>
>  
>
>>Dear Internet-Drafts Administrator,
>>
>>Attached is draft-ietf-ipoib-subnet-manager-mib-00.txt as an
>>IP over IB workgroup submission.
>>
>>Please publish it.
>>
>>Thank you,
>>
>>Cheng Yang
>>Edwin Tsang
>>Carl Yang
>>
>>
>>    
>>
>
>
>_______________________________________________
>IPoverIB mailing list
>[email protected]
>https://www1.ietf.org/mailman/listinfo/ipoverib
>  
>