From: Hani Mustafa <hani.mustafa@gm...> - 2007-01-25 12:06:51
In the case of NAT'd endpoints, the GNU GK adds a
NonStandardIdentifier with a choice set to object identifier. However,
it does not specify an OID, so no OID is actually encoded.
I read abit into X.208/X.209, but I have not found anything yet that
says whether or not this is standards compliant. More on this when I
find out more, but I'm suspecting the standard was quite vague on
this. If someone already knows the answer to this question, please
But more importantly, it seems to me quite pointless to send a
non-standard object without an OID. What if you guys want to add
another feature, and need to put yet another non-standard object?
That's what the OID's are for. So why is it being done this way?
Get latest updates about Open Source Projects, Conferences and News.