[BEHAVE] [behave] #15: DThaler comments on nat-mib-06

"behave issue tracker" <trac+behave@trac.tools.ietf.org> Sat, 22 June 2013 20:39 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: behave issue tracker <trac+behave@trac.tools.ietf.org>
Precedence: bulk
Auto-Submitted: auto-generated
To: draft-ietf-behave-nat-mib@tools.ietf.org, dthaler@microsoft.com
Date: Sat, 22 Jun 2013 20:39:09 -0000
Message-ID: <065.3afc93e0d2a3edd9af1ed12f11c3a4b7@trac.tools.ietf.org>
Resent-To: simon.perreault@viagenie.ca, ssenthil@cisco.com, tina.tsou.zouting@huawei.com
Resent-Message-Id: <20130622203916.8030721F9E2A@ietfa.amsl.com>
Resent-Date: Sat, 22 Jun 2013 13:39:16 -0700
Resent-From: trac+behave@trac.tools.ietf.org
Cc: behave@ietf.org
Subject: [BEHAVE] [behave] #15: DThaler comments on nat-mib-06
Reply-To: behave@ietf.org

#15: DThaler comments on nat-mib-06

 1) Section 5 of the current draft has
 " Some of the readable objects in this MIB module (i.e., objects with a
    MAX-ACCESS other than not-accessible) may be considered sensitive or
    vulnerable in some network environments.  It is thus important to
    control even GET and/or NOTIFY access to these objects and possibly
    to even encrypt the values of these objects when sending them over
    the network via SNMP."

 Per http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security
 that's supposed to be followed with
 " These are the tables and objects and their
    sensitivity/vulnerability:

     <list the tables and objects and state why they are sensitive>"

 Also the document has 2 paragraphs of text "There are a number of managed
 objects in this MIB that may contain ...
 versions of SNMP provide features for such a secure environment."
 which do not appear in the current MIB boilerplate at the link above.
 Should those 2 paragraphs be removed?

 2) Section 5 contains MUST, SHOULD, etc.   But the document is missing
 the boilerplate reference to RFC 2119.

 3) Section 6 does not say whether any additional actions for IANA are
 needed.  Suggest adding "No IANA actions are required by this document."

 4) The MIB compiler I used complained about this:
 > natMappingPool OBJECT-TYPE
 >     SYNTAX NatPoolId (0|1..4294967295)
 Because of
 > NatPoolId ::= TEXTUAL-CONVENTION
 >     SYNTAX Unsigned32 (1..4294967295)

 That is, NatPoolId does not allow 0, and so natMappingPool cannot add it
 and still use the NatPoolId syntax.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-behave-nat-
  dthaler@microsoft.com  |  mib@tools.ietf.org
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:
Component:  nat-mib      |    Version:  -06
 Severity:  In WG Last   |   Keywords:
  Call                   |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/behave/trac/ticket/15>
behave <http://tools.ietf.org/wg/behave/>

[BEHAVE] [behave] #15: DThaler comments on nat-mi… behave issue tracker
Re: [BEHAVE] [behave] #15: DThaler comments on na… Simon Perreault
Re: [BEHAVE] [behave] #15: DThaler comments on na… Dave Thaler