Re: Proposed text for xyzValidIntervals/xyzInvalidIntervals

Gary Hanson <gary@kentrox.com> Fri, 12 June 1998 21:10 UTC

Delivery-Date: Fri, 12 Jun 1998 17:11:00 -0400
Return-Path: gary@kentrox.com
Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA25825 for <ietf-archive@ietf.org>; Fri, 12 Jun 1998 17:10:59 -0400 (EDT)
Received: from stbernard.cisco.com (stbernard.cisco.com [171.69.219.46]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA26658 for <ietf-archive@cnri.reston.va.us>; Fri, 12 Jun 1998 17:13:22 -0400 (EDT)
Received: from hubbub.cisco.com (mailgate-sj-1.cisco.com [198.92.30.31]) by stbernard.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id OAA08054 for <extdom.trunk-mib@aliashost.cisco.com>; Fri, 12 Jun 1998 14:02:15 -0700 (PDT)
Received: from proxy2.cisco.com (proxy2.cisco.com [192.31.7.89]) by hubbub.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id OAA25529 for <trunk-mib@external.cisco.com>; Fri, 12 Jun 1998 14:02:13 -0700 (PDT)
Received: (from smap@localhost) by proxy2.cisco.com (8.8.7/8.8.5) id OAA00036 for <trunk-mib@external.cisco.com>; Fri, 12 Jun 1998 14:02:12 -0700 (PDT)
Received: from kentrox.kentrox.com(192.228.59.2) by proxy2.cisco.com via smap (V2.0) id xma000023; Fri, 12 Jun 98 21:02:07 GMT
X-SMAP-Received-From: outside
Received: from kentrox.com ([146.71.112.126]) by kentrox.kentrox.com (8.9.0/8.9.0) with SMTP id NAA24675; Fri, 12 Jun 1998 13:58:21 -0700 (PDT)
Received: from localhost by kentrox.com (4.1/SMI-4.1_KTX1.1) id AA07520; Fri, 12 Jun 98 13:58:13 PDT
Date: Fri, 12 Jun 1998 13:58:13 -0700
From: Gary Hanson <gary@kentrox.com>
X-Sender: gary@skeeter
To: "C. M. Heard/VVNET, Inc." <heard@vvnet.com>
Cc: atommib@thumper.bellcore.com, trunk-mib@external.cisco.com
Subject: Re: Proposed text for xyzValidIntervals/xyzInvalidIntervals
In-Reply-To: <Pine.BSF.3.96.980612105306.11307D-100000@shell16.ba.best.com>
Message-Id: <Pine.SUN.3.96.980612135006.5494B-100000@skeeter>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"

Hi Mike,

On Fri, 12 Jun 1998, C. M. Heard/VVNET, Inc. wrote:

> In other words, we cannot change the definitions of the various
> xyzValidIntervals and xyzInvalidIntervals without breaking
> fielded implementations.  Actually, SMI rules wouldn't let us
> change the definitions anyway -- we'd need to deprecate these
> objects and replace them with new objects.  We are, however,
> allowed to make editorial changes to the description clauses
> to clarify the definitions.  That's what I have tried to do,
> and corrections are invited if someone feels that I have
> done something else.

Note that xyzValidIntervals up through RFC 1406, RFC 1407, and RFC
1595 have never described proxy cases.  If the new text added in the
current drafts reflects fielded implementations, then it would still
be possible to change the definitions once more provided:
- (a) you can convince the implementors of existing fielded
      implementations to agree to the change (if you can identify
      who these implementors are)
- (b) you can convince the IESG and WG chairmen to allow the
      changes, in the best interests of future network management

If the new text only reflects SOME of the fielded implementations,
and if others match your modified interpretation, you have a better
case still (albeit one that would likely be considered late in
coming :-).

As you know, the xyzInvalidIntervals are likely to be less ingrained
in fielded implementations, since they are new in the current
drafts.  For those objects, at least, there would not be any issue
with having to deprecate them, since they don't "officially" exist
yet until the RFC is published (at least based on my interpretation
of how these things evolve).

> [...]
> 
> Mike
> --
> C. M. Heard/VVNET, Inc.
> heard@vvnet.com

Gary

 ______
| ///  |       TM   Gary Hanson                gary@kentrox.com
|   ADC|Kentrox     14375 NW Science Park Dr.  503-641-3321 (FAX)
|______|            Portland, Oregon  97229    800-733-5511 x6333