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

"Daniel Joyal" <djoyal@nortel.com> Thu, 16 November 2006 19:48 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GknDq-0004su-IK; Thu, 16 Nov 2006 14:48:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GknDo-0004so-Lt for ospf@ietf.org; Thu, 16 Nov 2006 14:48:28 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GknDn-0008DN-Ew for ospf@ietf.org; Thu, 16 Nov 2006 14:48:28 -0500
Received: from zrtphxm1.corp.nortel.com (zrtphxm1.corp.nortel.com [47.140.202.50]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id kAGJmLs13649; Thu, 16 Nov 2006 14:48:21 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 16 Nov 2006 14:48:19 -0500
Message-ID: <4B7DAC3FEFD35D4A96BDD011699050140A42410C@zrtphxm1.corp.nortel.com>
In-reply-to: <200611161910.kAGJAF403992@zrtps0kk.us.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: inconsistency in draft-ietf-ospf-mib-update-11.txt?
Thread-Index: AccJstsEjrUFtc/8SL2+WYNnQ+OfBAABDHdw
From: Daniel Joyal <djoyal@nortel.com>
To: Lou Berger <lberger@labn.net>, pgalecki@airvana.com, spencer.giacalone@csfb.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: ospf@ietf.org
Subject: [OSPF] RE: 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

Lou,

It is inconsistent. Thanks for catching this.
I don't think there is a reason to make Opaque
LSA support configurable as it is a backwards
compatible extension to OSPF, so the verbiage
about persistence should be deleted.

Any objections?

-Dan 

> -----Original Message-----
> From: Lou Berger [mailto:lberger@labn.net] 
> Sent: Thursday, November 16, 2006 2:07 PM
> To: Joyal, Daniel (BL60:SF23); pgalecki@airvana.com; 
> spencer.giacalone@csfb.com
> Cc: ospf@ietf.org
> Subject: inconsistency in draft-ietf-ospf-mib-update-11.txt?
> 
> 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