Re: [MIB-DOCTORS] [IPFIX] AD review of draft-ietf-ipfix-mib-05.txt(ipfixExportEntry)

[Atsushi Kobayashi <akoba at nttv6.net>]

Hi Randy, Gerhard, Thomas and all,

> > > > T16. ipfixExportEntry leads to a warning in the smicng compilation
> > > > 
> > > > W: f(ipfix.mi2), (676,12) Row "ipfixExportEntry" does not have a
> > > > consistent indexing scheme - index items from current table must come
> > > > after index items from other tables
> > > > 
> > > 
> > > Since I have only libsmi (which does not catch this) I did not realize it.
> > > Fixed.
> 
> This smicng warning can be misleading.  There is no SMI requirement, nor is
> there even a recommendation, for having "a consistent indexing scheme."
> The order of indexes should be determined by:
>   (1) the use cases for retrieving subsets of the table
>   (2) ease of access control policy formulation.
> 
> Making index order "consistent" can potentially defeat both of these
> objectives.
> 

Thank you for your comments.

From viewpoint of (1), my conclusion is to keep the order of 3 indexes
like that in -05 draft.
- ipfixExportIndex,
- ipfixMeteringProcessCacheId,
- ipfixTemplateObservationDomainId,

It is more suitable than my proposal.

Regards,

 Atsushi KOBAYASHI


--- 
Atsushi KOBAYASHI  <akoba at nttv6.net>
NTT Information Sharing Platform Lab.
tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637