headers
owner-disman | 9 Oct 2002 02:33
Picon

(unknown)

Comments on draft-ietf-disman-conditionmib-04.txt
Sender: owner-disman <at> dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

1. The MIB requires some patches to make it compile-
     a. IMPORT mib-2
     b. terminate the IMPORTS clause with a ';'
     c. in arcTable DESCRIPTION (line 343)
         s/"/'/
     d. line 394
        s/IANAItuProbableCause/IANAItuProbableCauseOrZero/
     e. in the COMPLIANCES section there are some irrelevant
        lines
        delete 560-570
     f. We may want to add arcStorageType to the arcSettingGroup

2. Other nits.
     s/MAC-ACCESS/MAX-ACCESS/g

Randy Presuhn wrote:
> Hi -
> 
> We're halfway through the disman WG last calls on the two
> alarm-related documents.  I have seen no comments yet, and
> have not even received any indication that anyone has read
> either of the drafts.  This does not bode well.
> 
> If you do not want to see this work unceremoniously dumped
> for lack of interest / progress, I strongly suggest reading
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randy Presuhn | 9 Oct 2002 03:16
Picon

Glenn's ARC comments

Hi -

Glenn's message was stuck in our majordomo plumbing since
September 14.  I don't know why Majordomo wouldn't pass
through the headers, which read:

| Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
|         by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id XAA03118
|         for <disman <at> dorothy.bmc.com>; Fri, 13 Sep 2002 23:59:22 -0700 (PDT)
| Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
|         by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g8E719k10785
|         for <disman <at> dorothy.bmc.com>; Sat, 14 Sep 2002 02:01:10 -0500 (CDT)
| Received: from geto.cysol.co.jp (geto.cysol.co.jp [210.169.247.73])
|         by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 1E6DE1FF015
|         for <disman <at> dorothy.bmc.com>; Sat, 14 Sep 2002 02:00:48 -0500 (CDT)
| Received: from cysols.com (niseko.cysol.co.jp [210.169.247.75])
|         by geto.cysol.co.jp (8.11.3/3.7W) with ESMTP id g8E70JS16123;
|         Sat, 14 Sep 2002 16:00:19 +0900 (JST)
| Message-ID: <3D82DE81.3080701 <at> cysols.com>
| Date: Sat, 14 Sep 2002 16:00:17 +0900
| From: Glenn Mansfield Keeni <glenn <at> cysols.com>
| Organization: Cyber Solutions Inc.
| User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0) Gecko/200
| 20530
| X-Accept-Language: en, ja
| MIME-Version: 1.0
| To: disman <at> dorothy.bmc.com
| Subject: Re: disman wg last calls update
| References: <200209140009.RAA02329 <at> dorothy.bmc.com>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lam, Hing-Kam (Kam | 10 Oct 2002 19:52
Picon
Favicon

RE: Glenn's ARC comments

Hi all,

Please see inline below.

Regards,
Kam Lam

> 
> Anyway, to the content of Glenn's comments:
> 
> > 1. The MIB requires some patches to make it compile-
> >      a. IMPORT mib-2
> 
> agreed

Agree. Will do.

> 
> >      b. terminate the IMPORTS clause with a ';'
> 
> agreed

Agree. Will do.

> 
> >      c. in arcTable DESCRIPTION (line 343)
> >          s/"/'/
> 
> it looks like this is already fixed in -05-
(Continue reading)

Permalink | Reply | 1 comment |
headers
Randy Presuhn | 10 Oct 2002 20:21
Picon

RE: Glenn's ARC comments

Hi -

> Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE00BE9C7 <at> nj7460exch004u.ho.lucent.com>
> From: "Lam, Hing-Kam (Kam)" <hklam <at> lucent.com>
> To: "'Randy Presuhn'" <rpresuhn <at> dorothy.bmc.com>, disman <at> dorothy.bmc.com
> Subject: RE: Glenn's ARC comments
> Date: Thu, 10 Oct 2002 13:52:17 -0400
...
> In M.3100 Amd3, Time-Inhibit and Count-Down are two separate 
> optional features of the ARC function. In the ARC MIB, the 
> arcTIGroup and arcQICDGroup GROUPs model these two 
> optional feature and thus are made optional in the conformance statement.

WG chair says:
That it's optional in M.3100 does not mean that we have to retain
that optionality.  Keep in mind these provisions of RFC 2026, the
internet standards process:

|  The requirement for at least two independent and interoperable
|  implementations applies to all of the options and features of the
|  specification.  In cases in which one or more options or features
|  have not been demonstrated in at least two interoperable
|  implementations, the specification may advance to the Draft Standard
|  level only if those options or features are removed.

> I hope the following addition and changes in the DESCRIPTION clauses 
> will help explain the rationale.
> 
> --Addition:
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Glenn Mansfield Keeni | 11 Oct 2002 02:34
Favicon

Re: Glenn's ARC comments

Hi,
Lam, Hing-Kam (Kam) wrote:
> Hi all,
> 
> Please see inline below.
> 
> Regards,
> Kam Lam
> 
> 
>>Anyway, to the content of Glenn's comments:
>>
[snip]
>>>     e. in the COMPLIANCES section there are some irrelevant
>>>        lines
>>>        delete 560-570
>>
>>I don't think so.  What am I missing?
> 
> 
> Concur with Randy.
My mistake. I misread that part. Ignore that comment.

[snip]

Glenn
Permalink | Reply | 0 comments |
headers
Lam, Hing-Kam (Kam | 11 Oct 2002 14:26
Picon
Favicon

RE: Glenn's ARC comments

Hi,

The DESCRIPTION clauses will be changed to:

         GROUP  arcTIGroup
         DESCRIPTION
           "This group is REQUIRED for ARC settings
            that provide the Time Inhibit (TI) function."

         GROUP  arcQICDGroup
         DESCRIPTION
           "This group is REQUIRED for ARC settings
            that provide the Quality Inhibit (QI) Count Down (CD)
            function."

Regards,
Kam Lam 

> -----Original Message-----
> From: Randy Presuhn [mailto:rpresuhn <at> dorothy.bmc.com]
> Sent: Thursday, October 10, 2002 2:21 PM
> To: disman <at> dorothy.bmc.com
> Subject: RE: Glenn's ARC comments
> 
> 
> Hi -
> 
> > Message-ID: 
> <E4BB443436F22D4AB9E84B06AB7C4CE00BE9C7 <at> nj7460exch004u.ho.lucent.com>
> > From: "Lam, Hing-Kam (Kam)" <hklam <at> lucent.com>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Randy Presuhn | 18 Oct 2002 18:06
Picon

Re: FW: ARC MIB Compilation

Hi -

> Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE00BEA07 <at> nj7460exch004u.ho.lucent.com>
> From: "Lam, Hing-Kam (Kam)" <hklam <at> lucent.com>
> To: "'Randy Presuhn'" <rpresuhn <at> dorothy.bmc.com>
> Cc: "Wijnen, Bert (Bert)" <bwijnen <at> lucent.com>,
>         "Castro, Eunice Mary Esther (Mary)" <emclark <at> lucent.com>
> Subject: FW: ARC MIB Compilation
> Date: Fri, 18 Oct 2002 11:46:55 -0400
> 
> 
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> 
> ------_=_NextPart_000_01C276BD.956BDEAA
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> 
> Randy,
> 
> We did a strict compilation on the ARC mib and got the following result. (I also attached is the mib module
that was used.)
> 
> For 
> > > E: f(arc.mi2), (148,1) Row "arcEntry" may not have columns 
> > with MAX-ACCESS 
> > > of read-write if any column is read-create
> I will change the MAX-ACCESS of arcNalmTimeRemaining from read-write to read-create and it should
resolve the error.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lam, Hing-Kam (Kam | 18 Oct 2002 19:18
Picon
Favicon

RE: FW: ARC MIB Compilation

Hi,

Thanks for the advice. I think making the syntax of 
IANAItuProbableCuasesOrZero to INTEGER (0..2147483647) is indeed a 
good idea. It will satisfy the compiler and also be consistent 
with the syntax of IANAItuProbableCauses that is INTEGER. 
(Note that however, in the Alarm MIB, there is no explicit 
restriction on IANAItuProbableCauses to non-negative values though.)

No changes to the mib will be made for the other warnings.

Here is a summary of changes that will be reflected in version -06- :
(1) import mib-2
(2) add ; at the end of imported list
(3) change the syntax of IANAItuProbableCuasesOrZero to INTEGER (0..2147483647)
(4) change the MAX-ACCESS of arcNalmTimeRemaining from read-write to read-create
(5) add
         GROUP  arcTIGroup
         DESCRIPTION
           "This group is REQUIRED for ARC settings
            that provide the Time Inhibit (TI) function."

         GROUP  arcQICDGroup
         DESCRIPTION
           "This group is REQUIRED for ARC settings
            that provide the Quality Inhibit (QI) Count Down (CD)
            function." 

(6) add arcStorageType to arcSettingGroup
(7) clarify the arcSettingGroup and arcTIGroup in the DESCRIPTION clauses.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Wijnen, Bert (Bert | 18 Oct 2002 19:39
Picon
Favicon

RE: FW: ARC MIB Compilation

> > What is your advice on  E: f(arc.mi2), (155,22) regarding 
> arcAlarmType?
> > The syntax of arcAlarmType is IANAItuProbableCausesOrZero, 
> whose underlying syntax is Unsigned32.
> > Do I need to explicitly specify the range of the 
> IANAItuProbableCausesOrZero TC, i.e., Unsigned32 (0..4294967295)?
> > Also note that the description of the 
> IANAItuProbableCausesOrZero TC states that this TC takes any value of
> > IANAItuProbableCauses or 0. IANAItuProbableCauses  is 
> defined in the Alarm MIB with syntax INTEGER.
> 
> I'd suggest that syntax of IANAItuProbableCuasesOrZero should be
> INTEGER (0..2147483647) to resolve this, unless we really want to
> define negative probable causes in the future.
>
So maybe we should add the the IANAItuProbableCuases TC a sentence
in the DESCRIPTION clause to state that negative values should never
be assigned because the TC is sometimes used for Index objects 

Bert
Permalink | Reply | 0 comments |
headers
Randy Presuhn | 18 Oct 2002 19:56
Picon

RE: FW: ARC MIB Compilation

Hi -

> Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0F29F432 <at> nl0006exch003u.nl.lucent.com>
> From: "Wijnen, Bert (Bert)" <bwijnen <at> lucent.com>
> To: Randy Presuhn <rpresuhn <at> dorothy.bmc.com>, hklam <at> lucent.com
> Cc: bwijnen <at> lucent.com, disman <at> dorothy.bmc.com, emclark <at> lucent.com
> Subject: RE: FW: ARC MIB Compilation
> Date: Fri, 18 Oct 2002 19:39:39 +0200
> 
> > > What is your advice on  E: f(arc.mi2), (155,22) regarding 
> > arcAlarmType?
> > > The syntax of arcAlarmType is IANAItuProbableCausesOrZero, 
> > whose underlying syntax is Unsigned32.
> > > Do I need to explicitly specify the range of the 
> > IANAItuProbableCausesOrZero TC, i.e., Unsigned32 (0..4294967295)?
> > > Also note that the description of the 
> > IANAItuProbableCausesOrZero TC states that this TC takes any value of
> > > IANAItuProbableCauses or 0. IANAItuProbableCauses  is 
> > defined in the Alarm MIB with syntax INTEGER.
> > 
> > I'd suggest that syntax of IANAItuProbableCuasesOrZero should be
> > INTEGER (0..2147483647) to resolve this, unless we really want to
> > define negative probable causes in the future.
> >
> So maybe we should add the the IANAItuProbableCuases TC a sentence
> in the DESCRIPTION clause to state that negative values should never
> be assigned because the TC is sometimes used for Index objects 
...

Ok with me.
(Continue reading)

Permalink | Reply | 3 comments |

Gmane