Re: Re: [Entmib] CLEI Code URN draft

"Randy Presuhn" <randy_presuhn@mindspring.com> Tue, 14 December 2004 22:05 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26810 for <entmib-archive@lists.ietf.org>; Tue, 14 Dec 2004 17:05:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeKhx-00049K-VW; Tue, 14 Dec 2004 16:59:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeKbP-0002fb-MZ for entmib@megatron.ietf.org; Tue, 14 Dec 2004 16:53:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25596 for <entmib@ietf.org>; Tue, 14 Dec 2004 16:53:01 -0500 (EST)
Received: from pop-a065d23.pas.sa.earthlink.net ([207.217.121.254]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeKjU-0008Tq-Li for entmib@ietf.org; Tue, 14 Dec 2004 17:01:26 -0500
Received: from h-66-167-121-241.snvacaid.dynamic.covad.net ([66.167.121.241] helo=oemcomputer) by pop-a065d23.pas.sa.earthlink.net with smtp (Exim 3.33 #1) id 1CeKbK-0004lx-00 for entmib@ietf.org; Tue, 14 Dec 2004 13:52:58 -0800
Message-ID: <00e601c4e227$4eb36c80$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <6.1.2.0.2.20041213171740.01de1df8@128.96.81.11><002501c4e185$24357680$7f1afea9@oemcomputer> <6.1.2.0.2.20041214150730.01d67ec0@128.96.81.11>
Subject: Re: Re: [Entmib] CLEI Code URN draft
Date: Tue, 14 Dec 2004 13:53:12 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
Sender: entmib-bounces@ietf.org
Errors-To: entmib-bounces@ietf.org

Hi -

> From: "Kaj Tesink" <kaj@research.telcordia.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <entmib@ietf.org>
> Sent: Tuesday, December 14, 2004 12:10 PM
> Subject: Re: Re: [Entmib] CLEI Code URN draft
...
> >Wouldn't it be simpler to say that CLEI codes MUST be upper case?
>
>
> maybe so, but as i understand it T1.213 is case-insensitive,
> so restricting the URN name space to upper case seems inappropriate.
...

My concerns are mailnly with regard to the future if these things prove useful.
    1) consider what it would take to describe the behaviour of read-write
        objects that used these (after a write, would the value read be bit-for-bit
        identical, or merely fit the matching rules?)
    2) if they were used for indexing...

If their definition is already case insensitive, then I think we'd really be better
off deciding what their "canonical" representation should be for our purposes.
However, I freely admit this is a theoretical concern, and that if we don't imagine
these being used in other MIB object definitions, there's less need to worry
about it.

Randy



_______________________________________________
Entmib mailing list
Entmib@ietf.org
https://www1.ietf.org/mailman/listinfo/entmib