Re: [Isis-wg] Final WG LC draft-ietf-isis-wg-mib-23.txt

"C. M. Heard" <heard@pobox.com> Wed, 12 October 2005 23:58 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPqUn-0007Fu-N2; Wed, 12 Oct 2005 19:58:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPqUm-0007FA-7t for isis-wg@megatron.ietf.org; Wed, 12 Oct 2005 19:58:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12869 for <isis-wg@ietf.org>; Wed, 12 Oct 2005 19:58:47 -0400 (EDT)
Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPqfB-0000fE-5m for isis-wg@ietf.org; Wed, 12 Oct 2005 20:09:37 -0400
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j9CNwZBT001721; Wed, 12 Oct 2005 16:58:35 -0700
Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j9CNwRph002782; Wed, 12 Oct 2005 16:58:27 -0700
Received: from localhost (heard@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id j9CNwQ1E002776; Wed, 12 Oct 2005 16:58:27 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Wed, 12 Oct 2005 16:58:26 -0700
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: Christian Hopps <chopps@rawdofmt.org>
Subject: Re: [Isis-wg] Final WG LC draft-ietf-isis-wg-mib-23.txt
In-Reply-To: <F2E002BC-9621-4AE8-B8A3-9B95F3CBCF34@rawdofmt.org>
Message-ID: <Pine.LNX.4.10.10510121637160.29516-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, ISIS WG <isis-wg@ietf.org>
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
Sender: isis-wg-bounces@ietf.org
Errors-To: isis-wg-bounces@ietf.org

On Wed, 12 Oct 2005, Christian Hopps wrote:
> Jeff,
> 
> I suggest that we make these changes if necessary (sounds like not)  
> as editorial in the RFC process. I *really* don't want to publish a  
> new draft and then go through *another* WG LC.
> 
> Thanks,
> Chris.

I am not sure that the proposed changes -- especially the relatively
important one shown below, deleting the inappropriate text from the
IsisSystemID DESCRIPTION clause -- would be allowed by the RFC
Editor without consultation with the IESG/cognizant ADs.  It's
possible to put this is in as an IESG note, but it's really better
to have the I-D that is sent to the RFC Editor be as close as
possible to what you want to publish.

In any case it does not seem like full 2-week WG last call should be
needed for these changes ... seems to me it should suffice to have a
short (e.g. 48-hour) "does anybody object to these changes" last
call.  The document will after all still be going through IETF last
call before it gets to the IESG.

//cmh

>      IsisSystemID ::= TEXTUAL-CONVENTION
>          STATUS current
>          DESCRIPTION
>              "The ID for an Intermediate System.  This should
>               be unique within a network, and is included
>               in all PDUs originated by an Intermediate System.
> 
> >            Some implementations may automatically assign
> >            values and not permit an SNMP write, while
> >            others may require the value to be set manually.
> >
>               The protocol does not place any meanings upon
>               the bits, other than using ordering to break
>               ties in electing a Designated IS on a LAN."
>          REFERENCE "{ISIS.aoi systemId (119)}"
>          SYNTAX OCTET STRING (SIZE(6))
> 
>  But the 3 lines marked with > seem not part of the TC.
>  It depends on where /how the TC is used. Some may use it
>  for a read-only object and then those 3 lines mean nothing
>  or may be confusing. The 3 lines belong in a DESCRIPTION clause
>  where the TC is used as a SYNTAX in an OBJECT-TYPE and whihc
>  has possibly a MAX-ACCESS of read-write or read-create.


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg