[OSPF] inconsistency in draft-ietf-ospf-mib-update-11.txt?

Lou Berger <lberger@labn.net> Thu, 16 November 2006 19:10 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gkmcu-0003A1-9k; Thu, 16 Nov 2006 14:10:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gkmct-00039r-Dg for ospf@ietf.org; Thu, 16 Nov 2006 14:10:19 -0500
Received: from [216.246.62.14] (helo=esc91.midphase.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gkmcp-0007Au-Sk for ospf@ietf.org; Thu, 16 Nov 2006 14:10:19 -0500
Received: from [216.246.62.14] (helo=LC1.labn.net) by esc91.midphase.com with esmtpa (Exim 4.52) id 1GkmcX-0002fo-Fj; Thu, 16 Nov 2006 14:09:57 -0500
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 16 Nov 2006 14:06:39 -0500
To: djoyal@nortel.com, pgalecki@airvana.com, spencer.giacalone@csfb.com
From: Lou Berger <lberger@labn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc91.midphase.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ospf@ietf.org
Subject: [OSPF] inconsistency in draft-ietf-ospf-mib-update-11.txt?
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org
Message-Id: <E1Gkmcu-0003A1-9k@megatron.ietf.org>

Hi,

So, the following is taken from your draft:
    ospfOpaqueLsaSupport  OBJECT-TYPE
          SYNTAX       TruthValue
          MAX-ACCESS   read-only
          STATUS       current
          DESCRIPTION
             "The router's support for Opaque LSA types.

              This object is persistent and when written
              the entity SHOULD save the change to non-volatile
              storage."
          REFERENCE
             "The OSPF Opaque LSA Option"
          ::= { ospfGeneralGroup 16 }

The access and description seem inconsistent.  The description 
implies that acess should be "read-write".  Am I missing something?

Lou


_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf