
|
Transport Subsystem Issue#2 Cache contents - do we define this? USM defines its cache, but it uses only SNMP-specific parameters, not parameters for another layer Algorithm agility requires supporting whatever the secure transport can or will support; we don’t know what parameters will need to be cached. Implementations may be based on different libraries, and we don’t know what will need to be cached. Proposal: “Since the contents of a cache are meaningful only within an implementation, and not on-the-wire, the format of the cache and the LCD are implementation-specific.” |