> On 19 Jan 2017, at 14:21, Juergen Schoenwaelder > <[email protected]> wrote: > > On Thu, Jan 19, 2017 at 03:23:48AM -0800, Benoit Claise wrote: >> 4. >> >> leaf-list router-id { >> type inet:ip-address; >> description >> "Router-id for the node"; >> } >> >> We don't want to wait for >> https://tools.ietf.org/html/draft-ietf-rtgwg-routing-types-00 (btw, we >> should expedite this publication), but any good reason why >> this is aligned with its definition? >> typedef router-id { >> type yang:dotted-quad; >> description >> "A 32-bit number in the dotted quad format assigned to each >> router. This number uniquely identifies the router within an >> Autonomous System."; >> } > > For the sake of completeness, RFC 8022 has: > > leaf router-id { > type yang:dotted-quad; > description > "A 32-bit number in the form of a dotted quad that is used by > some routing protocols identifying a router."; > reference > "RFC 2328: OSPF Version 2."; > } > > Using yang:dotted-quad seems appropriate here.
Right, inet:ip-address value may also contain a zone index, which is clearly undesirable in router-id. Lada > > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
