Re: [BEHAVE] WGLC on draft-ietf-behave-nat-mib

Dave Thaler <dthaler@microsoft.com> Wed, 29 May 2013 21:43 UTC

Return-Path: <dthaler@microsoft.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7053B21F9763 for <behave@ietfa.amsl.com>; Wed, 29 May 2013 14:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.8
X-Spam-Level:
X-Spam-Status: No, score=-97.8 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2gsGi86t4T-Q for <behave@ietfa.amsl.com>; Wed, 29 May 2013 14:43:37 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 0269621F9766 for <behave@ietf.org>; Wed, 29 May 2013 14:43:36 -0700 (PDT)
Received: from BY2FFO11FD010.protection.gbl (10.1.15.203) by BY2FFO11HUB040.protection.gbl (10.1.14.161) with Microsoft SMTP Server (TLS) id 15.0.698.0; Wed, 29 May 2013 21:43:28 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD010.mail.protection.outlook.com (10.1.14.74) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Wed, 29 May 2013 21:43:28 +0000
Received: from CO9EHSOBE021.bigfish.com (157.54.51.112) by mail.microsoft.com (157.54.7.153) with Microsoft SMTP Server (TLS) id 14.3.136.1; Wed, 29 May 2013 21:43:17 +0000
Received: from mail103-co9-R.bigfish.com (10.236.132.234) by CO9EHSOBE021.bigfish.com (10.236.130.84) with Microsoft SMTP Server id 14.1.225.23; Wed, 29 May 2013 21:43:00 +0000
Received: from mail103-co9 (localhost [127.0.0.1]) by mail103-co9-R.bigfish.com (Postfix) with ESMTP id 6DDEA1C00AE for <behave@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Wed, 29 May 2013 21:43:00 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT002.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -19
X-BigFish: PS-19(zz9371I542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh17ej9a9j1155h)
Received-SPF: softfail (mail103-co9: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT002.namprd03.prod.outlook.com ; .outlook.com ;
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB271; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en;
Received: from mail103-co9 (localhost.localdomain [127.0.0.1]) by mail103-co9 (MessageSwitch) id 1369863779297663_19039; Wed, 29 May 2013 21:42:59 +0000 (UTC)
Received: from CO9EHSMHS028.bigfish.com (unknown [10.236.132.246]) by mail103-co9.bigfish.com (Postfix) with ESMTP id 453CC48005C; Wed, 29 May 2013 21:42:59 +0000 (UTC)
Received: from BL2PRD0310HT002.namprd03.prod.outlook.com (157.56.240.21) by CO9EHSMHS028.bigfish.com (10.236.130.38) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 29 May 2013 21:42:57 +0000
Received: from BY2PR03MB271.namprd03.prod.outlook.com (10.242.37.14) by BL2PRD0310HT002.namprd03.prod.outlook.com (10.255.97.37) with Microsoft SMTP Server (TLS) id 14.16.311.1; Wed, 29 May 2013 21:42:56 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB271.namprd03.prod.outlook.com (10.242.37.14) with Microsoft SMTP Server (TLS) id 15.0.698.13; Wed, 29 May 2013 21:42:54 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Wed, 29 May 2013 21:42:54 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "draft-ietf-behave-nat-mib@tools.ietf.org" <draft-ietf-behave-nat-mib@tools.ietf.org>
Thread-Topic: WGLC on draft-ietf-behave-nat-mib
Thread-Index: Ac5csUf0maP8QPpzSZGehDhIcO1HfwAAQW1Q
Date: Wed, 29 May 2013 21:42:54 +0000
Message-ID: <ba99d2de63904656992c45255161910a@BY2PR03MB269.namprd03.prod.outlook.com>
References: <7bc37af6cf764c2e965778b6b265a2d4@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <7bc37af6cf764c2e965778b6b265a2d4@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:1a:3:24d6:67ae:ed1b:a4be]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB271.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC101.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC101.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51704005)(377454002)(199002)(13464003)(189002)(47776003)(79102001)(74706001)(76576001)(50466002)(6806003)(80022001)(23726002)(65816001)(47446002)(54316002)(74502001)(54356001)(4396001)(47736001)(74876001)(49866001)(46102001)(77982001)(31966008)(56816002)(63696002)(53806001)(50986001)(33646001)(51856001)(20776003)(15202345002)(81342001)(46406003)(74366001)(47976001)(74316001)(81542001)(16676001)(69226001)(76482001)(76786001)(44976003)(59766001)(56776001)(76796001)(74662001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB040; H:TK5EX14HUBC101.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08617F610C
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] WGLC on draft-ietf-behave-nat-mib
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 21:43:42 -0000

Some initial items noticed by document shepherd (me):

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.

-Dave

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On Behalf
> Of Dave Thaler
> Sent: Wednesday, May 29, 2013 2:16 PM
> To: behave@ietf.org
> Subject: [BEHAVE] WGLC on draft-ietf-behave-nat-mib
> 
> We are starting a two-week working group last call for "Additional Managed
> Objects for Network Address Translators (NAT)", draft-ietf-behave-nat-mib-06,
> 
>   http://tools.ietf.org/html/draft-ietf-behave-nat-mib-06
> 
> Please send substantial comments to the list, and simple editorial nits to the
> authors.
> 
> WGLC for this document will end on Wednesday, June 12.
> 
> -Dave
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>