> On Aug 29, 2018, at 10:28 AM, heasley <[email protected]> wrote: > > Wed, Aug 29, 2018 at 01:17:48AM -0400, Jared Mauch: >> Yes, I’m always reminding folks that router-id may be well known to be the >> same integer representation of your IP address in the protocol encoding, but >> often it’s not a requirement. > > its not; the reverse actually. it is just a 32 bit integer, though many > platforms take the value from the loopback address and/or can be configured > from an ipv4 address formatted integer. So, there is nothing to be changed > in the protocol.
We’re saying the same thing, it’s just if you’re doing inet_ntoa/inet_addr for your presentation or configuration layer. - Jared _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
