Isn't it preferable to use positive requirements instead of negative ones? For example: Instead of " The protocol's loop avoidance mechanisms SHOULD NOT use identifiers tied to network topology." Why not " The protocol's loop avoidance mechanisms SHOULD be able to use identifiers that change over time. "?
I'd propose rewording it to:
The protocol's loop avoidance mechanisms MUST be able to use identifiers that change over time and are not tied to network topology
Ulrich suggests:
I'd propose rewording it to: