> Somewhat related, when JNPR implemented RTR the architecture was > planned so that the RTR implementation itself isn't tightly coupled to > RPKI validity. It was planned day1 that customers could have multiple > RTR setups feeding prefixes and the NOS side could use these for other > purposes too.
back in the day, the developing RP-rtr spec assumed multiple sources, RPKI, IRR, ... there was also an open-ended operator defined Color 0 8 16 24 31 .-------------------------------------------. | Protocol | PDU | | | Version | Type | Color | | 0 | 4 | | +-------------------------------------------+ | | | Length=20 | | | +-------------------------------------------+ | | Prefix | Max | Data | | Flags | Length | Length | Source | | | 0..32 | 0..32 | RPKI/IRR | +-------------------------------------------+ | | | IPv4 prefix | | | +-------------------------------------------+ | | | Autonomous System Number | | | `-------------------------------------------' until, at ietf maastricht (2010), the unfortunate actions of a bully who wanted more and more caused us to walk away, give up, and fall back to the simpler basic we have today. 0 8 16 24 31 .-------------------------------------------. | Protocol | PDU | | | Version | Type | reserved = zero | | 0 | 4 | | +-------------------------------------------+ | | | Length=20 | | | +-------------------------------------------+ | | Prefix | Max | | | Flags | Length | Length | zero | | | 0..32 | 0..32 | | +-------------------------------------------+ | | | IPv4 Prefix | | | +-------------------------------------------+ | | | Autonomous System Number | | | `-------------------------------------------' randy
