Re: [MIB-DOCTORS] 'MIB Doctor' review of draft-ietf-pce-pcep-mib-06

[Jonathan Hardwick <[e-mail]>]

Juergen, many thanks for this.

PCEP MIB co-authors:

As per Juergen's advice, I have commented out the offending restriction, as follows.  This has resolved the warning.  Please let me know ASAP if you have any comments on this.

-- The following restriction is commented out because of a limitation
-- in SMIv2 which does not allow index objects to be restricted in
-- scope.  Nevertheless, this object is intended to be restricted in
-- scope, as follows.
--
--     OBJECT       pcePcepPeerAddrType
--     SYNTAX       InetAddressType { unknown(0), ipv4(1), ipv6(2) }
--     DESCRIPTION  "Only unknown(0), ipv4(1), and ipv6(2) support
--                   is required."

Thanks
Jon

-----Original Message-----
From: Juergen Schoenwaelder [mailto:[e-mail]] 
Sent: 17 December 2014 14:25
To: Daniel King
Cc: [e-mail]; [e-mail]; [e-mail]; [e-mail]; Jonathan Hardwick
Subject: Re: 'MIB Doctor' review of draft-ietf-pce-pcep-mib-06

On Tue, Dec 16, 2014 at 06:48:45PM +0000, Daniel King wrote:
> Copying in mib-doctors as well.
> 
> In summary, the object (pcePcepPeerAddrType) is an index so we cannot put it
> in a group, yet when we restrict the scope (in Compliance clause) the
> compiler complains it is not in a group. :-/
> 
> https://tools.ietf.org/html/draft-ietf-pce-pcep-mib-11
>

This is one of the odd things in SMIv2. Congratulation for hitting
it. ;-)

My recommendation is to write down the syntax variation and to
comment it out. This way, it clear for the human what was meant
and SMIv2 compilers will be happy as well.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
Fax:   [phone]         <http://www.jacobs-university.de/>