IETF Logo Mail Archive

Re: [secdir] secdir review of draft-ietf-lisp-mib

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 21 June 2013 15:00 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E0121E812E; Fri, 21 Jun 2013 08:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 BIW7lr6omrme; Fri, 21 Jun 2013 08:00:47 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id A6ECC11E81A1; Fri, 21 Jun 2013 08:00:46 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5LF0T8v004107; Fri, 21 Jun 2013 16:00:29 +0100
Received: from 950129200 (customer18280.100.kt.cust.t-mobile.co.uk [178.100.71.103] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5LF0HHZ003782 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Jun 2013 16:00:21 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Uri Blumenthal' <uri@mit.edu>, "'Gregg Schudel (gschudel)'" <gschudel@cisco.com>
References: <090501ce6e01$4779cb70$d66d6250$@olddog.co.uk> <ED495B2B0CBE86418E03429D7AC236C40FD8362A@xmb-rcd-x09.cisco.com> <D0EC773D-1CBC-4D5F-BFCA-875426246E59@mit.edu>
In-Reply-To: <D0EC773D-1CBC-4D5F-BFCA-875426246E59@mit.edu>
Date: Fri, 21 Jun 2013 16:00:09 +0100
Message-ID: <09d701ce6e90$0fa99100$2efcb300$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQNJ2fjLzezWjeq+76qJDYf+9ym7jQHtuqxnAfEkD7CWKnSq8A==
Content-Language: en-gb
Cc: iesg@ietf.org, draft-ietf-lisp-mib.all@tools.ietf.org, secdir@ietf.org
Subject: Re: [secdir] secdir review of draft-ietf-lisp-mib
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 15:00:52 -0000

Writable MIB objects are very out of fashion these days. But the Ops guys should
comment more.

My gripe was only that this Group says they are writable when the object
definitions say they are not.

Adrian

> So what's the problem making these writable under SNMPv3 protection (and
> stating this requirement)?
> 
> On Jun 20, 2013, at 18:35, "Gregg Schudel (gschudel)" <gschudel@cisco.com>
> wrote:
> 
> >
> > On Jun 20, 2013, at 2:58 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> >
> >> although...
> >>
> >>     lispMIBTuningParametersGroup OBJECT-GROUP
> >>         OBJECTS { lispFeaturesMapCacheLimit,
> >>                   lispFeaturesEtrMapCacheTtl
> >>                 }
> >>         STATUS  current
> >>         DESCRIPTION
> >>                 "A collection of writeable objects used to
> >>                  configure LISP behavior and to tune performance."
> >>         ::= { lispGroups 10 }
> >>
> >> ...might lead one to think that something here is writeable.
> >
> > i'll re-word this in the final - it shouldnt have said that.
> > (about writable objects)
> >
> > thanks for pointing it out
> > (it's amazing how carefully these have been read and yet small
> > details slip through. ;(

v2.23.0 | Report a Bug | By Email