[saag] Re: A simpler form of OID

Phillip Hallam-Baker <[email protected]>
Newsgroups gmane.ietf.saag
Message-ID <CAMm+LwgjQjO8P=3RNz37aM_8ZOjsD66TWgTmYDKDwTX-XVKFjA@mail.gmail.com>
Except that the whole point here is that there is no code except to check
for end of sequence in cases where there is no other length indicator. I
haven't needed to do that so far.

The identifier is defined as a sequence of opaque octets. Applications are
not entitled to assume any semantics whatsoever beyond 'identifier sequence
[x, y, z] means thing P'.

All the semantic constraints we have been discussing are part of the
registration process.


On Thu, Sep 18, 2025 at 6:00 PM Michael Richardson <[email protected]>
wrote:

>
> Viktor Dukhovni <[email protected]> wrote:
>     > This is a base-128 encoding, only the termination signal is in the
>     > low-order bit, so instead of non-final bytes having the high bit set,
>     > they have the low bit set.  This perhaps makes for smaller numbers in
>     > the encoding, that could be easier to remember.
>
> yes. Potato, Potaetoe.
> My point is that DER already has a way to encode such things, and I'd
> rather
> re-use debugged code than invent something new.
>
> --
> Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>
> _______________________________________________
> saag mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.