----- Original Message ----- From: "Susan Hares" <shares@xxxxxxxx> Sent: Friday, February 23, 2018 7:11 PM > Tom: > > Before I dig deeper into this point, let me ask a question - have you read > the rib Info model? If you have, what would like moved from the RIB info > model to the Data model? If you have not, please review it. Susan Why should I review the Info model? It is only a Informational Reference so I do not need it to understand the data model. I have looked at it and see no useful information about how to interpret this uint32. It may be that this is too early in the process to specify the hard codes but if that is the case, then I think that the mechanics for specifying them should be. Tom Petch > The authors of the Data model aligned it with the RIB info model. > Comments from WG at the time were - just say error code. > > Cheerily, Susan Hares > > -----Original Message----- > From: tom p. [mailto:daedulus@xxxxxxxxxxxxx] > Sent: Friday, February 23, 2018 12:23 PM > To: ietf > Cc: i2rs@xxxxxxxx; draft-ietf-i2rs-rib-data-model@xxxxxxxx; > i2rs-chairs@xxxxxxxx; shares@xxxxxxxx; Alia Atlas > Subject: Re: [i2rs] Last Call: <draft-ietf-i2rs-rib-data-model-10.txt> (A > YANG Data Model for Routing Information Base (RIB)) to Proposed Standard > > This model has a > leaf error-code { > type uint32; > description > "The error code that reflects the failure reason."; > > I work with error codes and know that understanding what they are telling me > is key to resolving problems promptly but I can see no list of possible > error codes and what they mean, just a statement that the code is a uint32. > The text part of the I-D contains no mention of error-code - outside the > appearance in the tree diagram - AFAICT. > > Tom Petch > > ----- Original Message ----- > From: "The IESG" <iesg-secretary@xxxxxxxx> > To: "IETF-Announce" <ietf-announce@xxxxxxxx> > Cc: <i2rs@xxxxxxxx>; <draft-ietf-i2rs-rib-data-model@xxxxxxxx>; > <i2rs-chairs@xxxxxxxx>; <shares@xxxxxxxx>; <akatlas@xxxxxxxxx> > Sent: Tuesday, February 20, 2018 5:40 PM > Subject: [i2rs] Last Call: <draft-ietf-i2rs-rib-data-model-10.txt> (A YANG > Data Model for Routing Information Base (RIB)) to Proposed Standard > > > > > > The IESG has received a request from the Interface to the Routing > System WG > > (i2rs) to consider the following document: - 'A YANG Data Model for > Routing > > Information Base (RIB)' > > <draft-ietf-i2rs-rib-data-model-10.txt> as Proposed Standard > > > > The IESG plans to make a decision in the next few weeks, and solicits > final > > comments on this action. Please send substantive comments to the > > ietf@xxxxxxxx mailing lists by 2018-03-06. Exceptionally, comments may > be > > sent to iesg@xxxxxxxx instead. In either case, please retain the > beginning of > > the Subject line to allow automated sorting. > > > > Abstract > > > > > > This document defines a YANG data model for Routing Information > Base > > (RIB) that aligns with the I2RS RIB information model. > > > > > > The file can be obtained via > > https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ > > > > IESG discussion can be tracked via > > > https://datatracker.ietf.org/doc/draft-ietf-i2rs-rib-data-model/ballot/ > > > > > > No IPR declarations have been submitted directly on this I-D. > > > > > >
