RE: Gen-ART review of draft-ietf-bfd-mib-17

"Adrian Farrel" <> Thu, 17 April 2014 21:55 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 86D601A01D6; Thu, 17 Apr 2014 14:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cESKme936dPR; Thu, 17 Apr 2014 14:55:30 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4B72C1A01CE; Thu, 17 Apr 2014 14:55:30 -0700 (PDT)
Received: from (localhost.localdomain []) by (8.13.8/8.13.8) with ESMTP id s3HLtKmr011886; Thu, 17 Apr 2014 22:55:20 +0100
Received: from 950129200 ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id s3HLtJQ1011877 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Apr 2014 22:55:19 +0100
From: "Adrian Farrel" <>
To: "'Black, David'" <>, <>, <>, <>, "'General Area Review Team'" <>
References: <>
In-Reply-To: <>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Date: Thu, 17 Apr 2014 22:55:18 +0100
Message-ID: <051b01cf5a87$b92a84d0$2b7f8e70$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHXstybkl3Rj5QCVQi0ErrtVmSSApsFo67A
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--7.041-10.0-31-10
X-imss-scan-details: No--7.041-10.0-31-10
X-TMASE-MatchedRID: QfHZjzml1E+nykMun0J1wpmug812qIbzC/ExpXrHizxXopZjyO6CZaem Jq66qqv9A72lF8jbwSm+h2+kRiP1Xo4a2rhHAtuZoMfp2vHck9WHxi2fvkKUM8izgKND8Lm5VZ8 xQvqztISd5Vi9MggDmL1DgIPIkgsZSWKSZniod93ThGbP9qB93B9fNWA7SFWqWltirZ/iPP4Duw Qv5f82WF/nw1MAso95JvN5sPGL1gQqCxvBy34zX2gws6g0ewz2moKXVHfiMM8gcyGevtftJ6PFj JEFr+olqYB+kyCYtxRcLc3sLtjOt+TCMddcL/gjOwBXM346/+zID5XcD4FtapcOFu+rNPoeDEFa KkIPel+133QqrH6lMVsi4ALUpd8T
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 17 Apr 2014 21:55:32 -0000

Hi David,

Thanks for the review.

To pick out one of your points:

> This MIB contains many writable objects, so the authors should
> take note of the IESG statement on writable MIB modules:
> I did not see this mentioned in the shepherd writeup.  If the OPS Area
> has not been consulted, I strongly suggest doing so during IETF Last
> Call, e.g., starting with Benoit Claise (AD).

The OPS Directorate and the MIB Doctors will have been alerted to this document
by the last call and we can expect their comments.

But this question was discussed between the AD and the authors, and the AD was
unlikely to agree to sponsor the document if he felt it went against the IESG
statement. Our discussion resulted in some reduction of writeable objects.

I think there are several points to consider:
1. This document had already been completed and publication requested (i.e.
shepherd write-up written) at the time of the IESG statement. It would be
unreasonable to make the statement retrospective.
2. There are already various implementations in equipment (not just management
stations) of proprietary modules approximating to this document and these
support write-access.
3. This is a low-level component protocol of the sort that is used on dumber
devices and that is an area where write-access is more common.