Re: text encoded in oid values - documentation?
- From: steve <quintile@xxxxxxxxx>
- Date: Wed, 21 Jan 2009 15:19:51 -0800 (PST)
On Jan 21, 11:06 am, Praki <visitprakashin...@xxxxxxxxx> wrote:
On Jan 21, 1:43 am, steve <quint...@xxxxxxxxx> wrote:
The tail of some OIDs are encoded as ascii strings.
the only documentation I can find is from Microsoft:
http://support.microsoft.com/kb/318464
Anyone know of an RFC or some other authoritative source?
I am planning to translate these on the fly, I have seen instances of
two levels of hierarchy - two text strings each prefixed with its
length.
Can I assume that if a length followed by printable ascii characters
(or are they utf-8 ?) then I have a name, provided the sequence of
names
continues to exactly the end of the OID.
Thanks for any ideas.
-Steve
Hi Steve
have took of this documenthttp://www.rane.com/note161.html
it might help
Thanks,
Prakash
Thanks, however this doesn't seem to explain the problem I described.
I may not have been clear. I understand things like BER octstr and ASN.
1 DisplayString.
What I what is a standards doecument (RFC or otherwise) which
describes the use of OIDs sequences
to encode the name of the OID in ASCII, taking the microsoft example I
quoted:
the OID 1.3.6.1.4.1.311.1.13.1.5.97.116.97.112.105 represents
which is 1.3.6.1.4.1.311.1.13.1 followed by a length 5 string "ATAPI"
anyone know where this might be documented?
-Steve
.
- Follow-Ups:
- Re: text encoded in oid values - documentation?
- From: Mark Ellison
- Re: text encoded in oid values - documentation?
- References:
- text encoded in oid values - documentation?
- From: steve
- Re: text encoded in oid values - documentation?
- From: Praki
- text encoded in oid values - documentation?
- Prev by Date: Re: SNMP V3 Engine ID Discovery.
- Next by Date: Re: text encoded in oid values - documentation?
- Previous by thread: Re: text encoded in oid values - documentation?
- Next by thread: Re: text encoded in oid values - documentation?
- Index(es):
Relevant Pages
|