🚀 go-pugleaf

In article <1992Oct13.020901.3410@mel.dit.csiro.au>, brian@mel.dit.csiro.au (Brian May) writes:

  ... Stuff deleted 

|> 
|> OIDs and Class Tables
|> ---------------------
|> 
|> XOM holds a _static_ class table containing all the OIDs it knows about.
|> If you want to dynamically use/create a new object, it'll have to be 
|> re-compiled into XOM's class tables.
|> 
|> Class table structure is left up to the implementor.
|> 
|> Encode/Decode
|> -------------
|> 
|> These merely create the relevant structures for sending/receiving ASN.1
|> data relevant to the protocol stack in use.  (We use PEPSY for ISODE)
|> 

I think what said above is not enough.
The function om_encode must encode an OM object such that its peer can decode
it and its peer can use different stack. Thus, the encoding must be based on
ASN.1 syntax understood by both sides.

______________________________________________________________________________
Tai Nguyen				Email: ...!bae.bellcore.com!tain
Bell Communication Research 		Phone: (908) 699-7934
444 Hoes Lane Room RRC 1B210
Piscataway NJ, 08854