Re: Re: CLEI Code URN draft

At 04:53 PM 12/14/2004, Randy Presuhn wrote:
>Hi -
>
> > From: "Kaj Tesink" <[email protected]>
> > To: "Randy Presuhn" <[email protected]>
> > Cc: <[email protected]>
> > 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
>[email protected]
>https://www1.ietf.org/mailman/listinfo/entmib


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

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
Email: [email protected]
Tel: (732) 699-6068
Fax: (732) 336-2336

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