Causes the actual implementation destructor to be called.

Iterate through the hashtable and remove expired entries from it. RemoveIf() method in THashTable can be used for this purpose.

Creates a destination cache instance into heap.

Tries to find data with given address. Returns NULL, if the data was not found, or it was expired.

Old interface for source backwards compatibility. This one has flawed design, because it does not specify scope ID. One should use TInetAddr - version instead.

Checks whether the two addresses are mapped to the same destination cache entry. This takes the selected caching mode (per address or per network) into account.

Removes all entries from the destination cache.

Removes given entry from destination cache.

Modifies a single parameter of a cache entry, while maintaining the values of the other parameters. Leaves with error if the given cache entry is not found. The iStoreEntry is also updated to current time.

	dstcache->SetL(address, EPathMTU, 536);

Set the lifetime for cache entries in seconds.

Set maximum size of the destination cache in bytes. If there are more than this much non-expired cache entries, new hash items are not added.

Store a cache entry with given destination address and data. The space for data object is allocated from heap and the object is copied there. If there was an existing cache object with the same key, it is overwritten without further warnings. If the cache is full and no expired objects can be removed, leaves with an error.

Old interface for source backwards compatibility. This one has flawed design, because it does not specify scope ID. One should use TInetAddr - version instead.

The code could be something like following at the protocol SAP side

When opening a connection (This could be in the end of InitL() in TCP SAP):

MInterfaceManager *ifacer = Interfacer();
MDestinationCache *dstcache = IMPORT_API_L(ifacer, MDestinationCache);
TIp6Addr& addr = iFlowContext->RemoteAddr().Ip6Address();
TCacheInfo *cache = dstcache->Find(addr);
if (cache)
	{
	iSsthresh = cache->iMetrics[ESsThresh];
	iSRTT = cache->iMetrics[ESRtt];
	}

When closing a connection:

MDestinationCache *dstcache = ...IMPORT_API_L()...;
TIp6Addr& addr = iFlowContext->RemoteAddr().Ip6Address();
TCacheInfo cache;  // Should intialize to zero
cache.iMetrics[ESsThresh] = iSsthresh;
cache.iMetrics[ESRtt] = iSRTT;
dstcache->StoreL(addr, cache);

3) What kind of "safeguards" should there be when storing or applying values in cache? (probably rules something like "don't use ssthresh if it is <= 4" are needed)

4) Should there be some snapshots stored in the cache during lengthy TCP connections, or is it enough to store values only when closing TCP connection?