IPv6 MIB Revision Issues

IDStateSummary
dario_accornero-01 open Section 4 Page 7 ipv6InterfaceEffectiveMtu: I assume the MTU is
dario_accornero-02 open Section 4 Page 9 ipv6InterfaceIdentifierLength: The reason for the
dario_accornero-03 open Section 4 Page 16 ipAddressPrefixEntry: The purpose of this object
dario_accornero-04 open Section 4 Page 17 ipAddressPrefixOrigin: Besides DHCP and router
dario_accornero-05 open Section 4 Page 20 ipAddressType: The lack of a multicast type should
dario_accornero-06 open Section 4 Page 20 ipAddressOrigin: The lack of an origin identifier
dario_accornero-07 open Section 4 Page 22 inetNetToMediaTable: I would like to make sure
dario_accornero-08 open Section 4 Page 4 inetCidrRouteEntry: It is unclear why there is no
fenner-01 open ScopeIdentifier TC
fenner-02 open ReasmReqds, ReasmOKs, ReasmFails
ip-forward-mib-01 open Trash this completely and start from scratch with a new MIB?
ip-forward-mib-02 open How to tell what a given instance means?
ip-forward-mib-03 open Any other objects from RFC 2465's ipv6RouteTable?
ip-forward-mib-04 open Better wording for ipForwardCompliance2?
ip-forward-mib-05 open Is there a better type (e.g. TimeTicks?) for inetCidrRouteAge?
ip-mib-01 open Move current conformance info to before deprecated objects
ip-mib-02 open Write up to date conformance statements
ip-mib-03 open Any other objects from ipv6IfTable that we need? How about getting rid of some?
ip-mib-04 open the ipv6IfTable could have one ipv6InterfaceIndex per address
ip-mib-05 open ipIfStatsTable:
ip-mib-06 resolved inetNetToMediaState:
ip-mib-07 open How to describe what stats are required, especially in the ICMP Msg table?
ip-mib-08 resolved Should the ipv6 scope table have a scope name string like
ip-mib-09 open General question: what about per-interface vs. system-wide counters?
ip-mib-10 open Do we need an ipv6ReasmTimeout too? I think not;
juergen-01 open Connection start times
macfadden-01 open 1. This MIB module has read-write objects,
macfadden-02 open 2. There is no support for multi-stack/same Address Family
macfadden-03 open 3. I suggest liberal use of REFERENCE clause
macfadden-04 resolved 4. ipv6Forwarding: The DESCRIPTION is not appropriate.
macfadden-05 resolved 5. "what about SIIT object saying whether an IPv4 address?
macfadden-06 open 6. Please define an explicit object(s) to express capability of an
macfadden-07 open 7. I like the ipv4IfTable as it makes more sense to organize
macfadden-08 open 8. General request: Please add *LastChange and *Number objects
macfadden-09 open 9. ipv6InterfaceTable -
macfadden-10 open 10. ipIfStatsTable -
macfadden-11 open 11. ipIfStatsTable counters -
macfadden-12 open 12. Since ipIfStatsInTooBigErrors is only valid for IPv6,
macfadden-13 open 13. I started to wonder if ipIfStatsTable will need
macfadden-14 open 14. ipIfStatsTable counters - refresh rate
macfadden-15 open 15. Internet Address Prefix table -
macfadden-16 open 16. I can't see how ipAddressPrefixTable is useful for IPv4.
macfadden-17 resolved 17. ipAddressIfIndex description should
macfadden-18 resolved 18. ipAddressType, maybe reiterate that broadcast
macfadden-19 open 19. ipAddressPrefix value "0.0" is good.
macfadden-20 open 20. ipAddressOrigin should be a TC (see item 15)
macfadden-21 open 21. There should be an object ipAddressOriginCreationTime
macfadden-22 open 22. ipAddressStatus should be a TC if it needs to exist at all.
macfadden-23 open 23. If ipAddressStatus survives the next edit,
macfadden-24 open 24. inetNetToMediaTable -
macfadden-25 open 25. inetNetToMediaType -
macfadden-26 open 26. "inetNetToMediaState - why no value for incomplete?"
macfadden-27 resolved 27. "inetNetToMediaState - what values for !ipv6? noNUD(7) or unknown(6)?"
macfadden-28 resolved 28. ScopeIdentifier - remove reference to rfc2233 in description.
macfadden-29 open 29. "Should there be associated objects to provide a scope description,
macfadden-30 open 30. inetIcmpTable - Use of value 0 is not recommended. see
macfadden-31 open 31. The summary counters might not be all that useful in the
macfadden-32 open 32. inetIcmpTable should reference underlying spec for counters.
macfadden-33 open 33. inetIcmpMsgTable - same indexing problems as #30
macfadden-34 open 34. inetIcmpMsgTable - special value 256.
macfadden-35 open 35. inetIcmpMsgTable - it may be that operators only want
macfadden-36 open 36. inetIcmpMsgType - should be a TC and include a reference
more-01 open split new inet mib
tcp-mib-01 open Are the current per-connection byte/segment counters appropriate?
tcp-mib-02 open More HC counters?
tcp-mib-03 open Seperate listening vs. established connections?
tcp-mib-04 open IPV6_V6ONLY / ??? : does the tcpConnectionTable need something?
thaler-01 resolved ipRoutingDiscards and ipReasmTimeout are deprecated, and I don't
thaler-02 open DESCRIPTION of many objects in the ipIfStatsTable
thaler-03 open UDP/TCP stats
thaler-04 open InNoRoutes / OutNoRoutes
thaler-05 open ASCII art of "Case Diagram for the IP Group"?
udp-mib-01 open [optional] connection table to more fully specify sockets?
udp-mib-02 open Per-connection/listener datagram / octet count objects in an optional
udp-mib-03 open IPV6_V6ONLY?