[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Hi Gerhard,

On Fri, 08 May 2009 11:28:45 +0200
Gerhard Muenz <muenz at net.in.tum.de> wrote:

> You propose to split ipfixExportMemberType from -06 into two objects
> ipfixExportGroupType and ipfixExportMemberType with several
> interdependencies specified in the description clauses.
> At first sight, this does not seem to be easier to understand than the
> table structure in -06.

Yes.

Section 5.4 mentions tuple (ipfixExportIndex, ipfixMeteringProcessCacheId,
ipfixTemplateObservationDomainId) indicates transport session group, but
section 7 MIB structure does not seem to indicate what transport session
group is.

Although DESCRIPTION in ipfixExportTable mentions that "Thanks to the
ipfixExportIndex the exports can group one or more Transport Sessions to
achieve a special functionality like failover management, load-balancing
etc.", actual table structure does not seem to group transport sessions
by ipfixExportIndex. 

When I would like to look for which transport sessions belong to some
specified transport session group, I have to see all of export table.

For example, all of transport sessions belonging to the following
transport session group (9:ipfixMeteringProcessCacheId,
3:ipfixTemplateObservationDomainId, 7:ipfixExportIndex)
may be scattered in the export table. It does not allow us to utilize
indexes of MIB structure.

    ipfixExportTable (5)
    |
    +- ipfixExportEntry (1)
       |
       +- index (9) (ipfixMeteringProcessCacheId)
          +- index (3) (ipfixTemplateObservationDomainId)
             +- index (257) (ipfixTemplateId)
             |  +- index (5) (ipfixTransportSessionIndex)
             |     +- index (7) (ipfixExportIndex)
             |        +- ipfixExportIndex (1) = 7
             |        +- ipfixExportMemberType (2) = 1 (primary)
             |
             +- index (257) (ipfixTemplateId)
             |  +- index (6) (ipfixTransportSessionIndex)
             |     +- index (9) (ipfixExportIndex)
             |        +- ipfixExportIndex (1) = 9
             |        +- ipfixExportMemberType (2) = 1 (primary)
             |
             +- index (264) (ipfixTemplateId)
             |  +- index (5) (ipfixTransportSessionIndex)
             |     +- index (8) (ipfixExportIndex)
             |        +- ipfixExportIndex (1) = 8
             |        +- ipfixExportMemberType (2) = 2 (secondary)
             |
             +- index (273) (ipfixTemplateId)
             |  +- index (11) (ipfixTransportSessionIndex)
             |     +- index (7) (ipfixExportIndex)
             |        +- ipfixExportIndex (1) = 7
             |        +- ipfixExportMemberType (2) = 2 (secondary)
             |
             +- index (289) (ipfixTemplateId)
                +- index (11) (ipfixTransportSessionIndex)
                   +- index (8) (ipfixExportIndex)
                      +- ipfixExportIndex (1) = 8
                      +- ipfixExportMemberType (2) = 1 (primary)

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