Re: Re: CLEI Code URN draft
"Randy Presuhn" <[email protected]> Tue, 14 Dec 2004 13:53:12 -0800
| Newsgroups | gmane.ietf.entmib |
|---|---|
| Message-ID | <00e601c4e227$4eb36c80$7f1afea9@oemcomputer> |
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