Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft. Document: raft-ietf-babel-information-model-11.txt Reviewer: Geoff Huston Review Date: date IETF LC End Date: 27 Oct 2020 Intended Status: Informational Summary: No issues found. This document is ready for publication. Comments: This document provides an information model for the Babel protocol. It uses a pseudo programming language like notation to enumerate a lisdt of objects that collectively comprise the information model. It appears that the primary purpose of this document is as a reference source for implementors of this protocol. This is not an easily readable document, but I believe that was never the intention. This is a list of objects and the hierarchical structure in which the objects are placed. The document does not attempt to justify why these objects are listed here, nor does it elaborate as to their intended role other than a brief functional desription of the information that is denoted by the object. Major Issues: None Minor Issues: None Nits: It seems anomalous to this reviewer that it goes to the bit lengths of some integer valued objects, yet leaves string objects undefined in terms of any maximum length. "centiseconds"? Really? "tenths of seconds" would be clearer to most readers! -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call