Re: Re: [Entmib] CLEI Code URN draft

Kaj Tesink <kaj@research.telcordia.com> Thu, 16 December 2004 20:27 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 PAA05302 for <entmib-archive@lists.ietf.org>; Thu, 16 Dec 2004 15:27:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cf25k-0007eF-Kt; Thu, 16 Dec 2004 15:19:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cf1xV-00033X-Q4 for entmib@megatron.ietf.org; Thu, 16 Dec 2004 15:10:45 -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 PAA02715 for <entmib@ietf.org>; Thu, 16 Dec 2004 15:10:43 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cf25z-0006RF-G8 for entmib@ietf.org; Thu, 16 Dec 2004 15:19:32 -0500
Received: from shannon.research.telcordia.com (shannon [128.96.81.11]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id iBGKA1jR007584; Thu, 16 Dec 2004 15:10:01 -0500 (EST)
Received: from KAJ-2.research.telcordia.com (KAJ-2.cc.telcordia.com [128.96.171.169]) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id PAA21548; Thu, 16 Dec 2004 15:09:53 -0500 (EST)
Message-Id: <6.1.2.0.2.20041216145009.03d7e0c0@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Thu, 16 Dec 2004 15:09:49 -0500
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: Re: [Entmib] CLEI Code URN draft
In-Reply-To: <00e601c4e227$4eb36c80$7f1afea9@oemcomputer>
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> <00e601c4e227$4eb36c80$7f1afea9@oemcomputer>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: entmib@ietf.org
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

At 04:53 PM 12/14/2004, Randy Presuhn wrote:
>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,

i agree that at this stage your point is theoretical but at the same
time we dont want to go in a direction that we may regret later on.
i checked a bit more with the CLEI folks, and the following transpired:
- T1.213 is case-insensitive
- the maintenance agent in practice only assigns codes using uppercase
    representation; the records are kept uppercase
- the maintenance agent can load records in
    lower case and their system will convert it to uppercase
- common representation is usually in uppercase

so in  practice we seem to have two choices for the URN space:
1.sticking with case-insensitive, i.e., be strictly compatible
     with T1.213, or
2.going for uppercase only, which would be compatible with practical use
     but narrow the application of T1.213

any further thoughts?

kaj




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


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
Email: kaj@research.telcordia.com
Tel: (732) 699-6068
Fax: (732) 336-2336

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


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