> This document describes the MRT format for routing information > export. This format was developed in concert with the Multi-threaded > Routing Toolkit (MRT) from whence the format takes it name. The > format can be used to export routing protocol messages, state > changes, and routing information base contents.
Similar to BMP, MRT uses 32 bit timestamps. Once again, the issue is a question of whether to take a pain hit now, while MRT still has a relatively small install base, or whether to take a much, much bigger pain hit when we reach 2038 when we have much wider deployment of MRT + a whole pile of archived records to deal with (as we're talking about an archive storage mechanism here). Personally, I'm not a fan of kicking cans down the road. The standard also lacks a version field in the headers. If the authors were to decide that changing the header might be in the protocol's long-term interest, then adding a version field would probably be a good idea. Nick [as with my previous comments on the BMP ID, apologies for jumping in with a fundamental change suggestion like this on a -15 draft.] _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
