This is the index page to the individual issues reported for draft-ietf-behave-nat-mib. The initial set of issues is taken from Tracker tickets 15-19 and David Harrington's detailed review posted to the Behave list as http://www.ietf.org/mail-archive/web/behave/current/msg11296.html. The latter review is referred to more briefly as the "DBH review" in the detailed issue pages.
The detailed issue page is linked through the issue number. Status is either Open or Closed. Significance is Major or Minor.
Issue Num. | Short Description | Status | Significance |
---|---|---|---|
001 | Missing list of tables in Security Considerations | Closed | Minor |
002 | Security Considerations text non-conformant to boilerplate | Closed | Minor |
003 | Missing boilerplate reference to RFC 2119 | Closed | Minor |
004 | Inconsistency between natMappingPool syntax and natPoolId TC | Closed | Minor |
005 | No statement of whether IANA action is required | Closed | Minor |
006 | Separate document for deprecation of NAT MIB v1 | Closed | Minor |
007 | Update security considerations due to potential coexistence of old and new versions | Open | Major |
008 | Operational considerations needed re use of old and new versions | Open | Major |
009 | Review all names taking account of criteria in Tickets: #17, RFC 4181, and details of DBH review | Open | Minor |
010 | Review whether summary table natCountersTable needed | Open | Major |
011 | Review whether two-level hierarchy needed for natPoolObjects, natPoolRangeTable | Closed | Minor |
012 | natAddrPortBindLocalAddr redefined in new document | Closed | Minor |
013 | Review change of realm to SNMPAdminString in new version | Open | Major |
014 | Add REFERENCE clauses | Open | Minor |
015 | Improve descriptions within the MIB itself | Open | Minor |
016 | Add source RFCs to IMPORTS clauses | Open | Minor |
017 | Expand upon interaction between realms and SNMPv3 views in NAT MIB | Open | Minor |
018 | Simplify REFERENCE for NatPoolingType | Open | Minor |
019 | Review structure of SubscriberIdentifierType and ensure fully standardized | Open | Major |
020 | Review whether to track creations and removals or just active mappings | Open | Major |
021 | Describe which table natNotifMappings refers to and why it is provided | Open | Minor |
022 | Review whether table row reuse a concern when a mapping is removed | Open | Minor |
023 | More description for natPoolTable | Open | Minor |
024 | For natpoolRealm, provide REFERENCE for RFC text defining realm | Open | Minor |
025 | Review natNotifPoolWatermarkLow and WatermarkHigh and use of derived values | Open | Major |
026 | Verify what address types natPoolRangeType can support | Open | Minor |
027 | Correct description of natMappingTable | Open | Minor |
028 | natMappingxxxAddress need REFERENCE for undefined address | Open | Minor |
029 | Add REFERENCE and descriptions for natMappingxxxBehavior | Open | Minor |
030 | Redo subscriber identifier as sparse augments table | Open | Minor |
031 | Specify values for unused subscriber identifiers | Open | Minor |
032 | Clarify meaning of natSubscriberIntPrefixType | Open | Minor |
033 | Remove dependencies on calculated values | Open | Major |
034 | Remove comment on unknown address from description of natSubscriberIPEncapsIdType | Open | Minor |
035 | Improve description of natSubsInterfaceIdRowIndex | Open | Minor |
036 | Review number of compliance levels | Open | Major |
037 | Clarify discussion of host identities in Security Considerations | Open | Minor |
038 | Broaden former employees to outsiders in general in Security Considerations | Open | Minor |
039 | Describe scope of uniqueness for natpoolIndex | Open | Minor |
040 | Standardize high and low usage mode for pools? | Open | Major |
The content of this page was last updated on 2014-10-31. It was migrated from the old Trac wiki on 2023-01-24.