Done. See -11 posted. Dino
> On Apr 22, 2025, at 7:20 AM, James Guichard <[email protected]> > wrote: > > Hi Dino, > Thank you for this easy-to-read document. Very few comments: > idnits 2.17.1 draft-ietf-lisp-geo-10.txt: > General comments from nits: > ** The abstract seems to contain references ([RFC8060]), which it > shouldn't. Please replace those with straight textual mentions of the > documents in question. > == The document seems to lack the recommended RFC 2119 boilerplate, even if > it appears to use RFC 2119 keywords -- however, there's a paragraph with > a matching beginning. Boilerplate error? > == Missing Reference: 'Section 7' is mentioned on line 404, but not defined > ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232) > > -------------------------------------------------------------------------------- > 19 This document updates [RFC8060]. > Jim> s/[RFC8060]/RFC8060 > 107 Identifier (AFI) [RFC1700]. > Jim> RFC1700 obsoleted by RFC3232. Please update reference. > 122 records. See [RFC9301] for what LISP messages contain EID-records > Jim> s/what/which > 133 3. Definition of Terms > 135 Geo-Point is a Geo-Coordinate according to [GEO] that defines a > 136 point from parameters Latitude, Longitude, and Altitude. > 138 Geo-Prefix forms a circle of a geographic area made up of a Geo- > 139 Point and a Radius. A Geo-Point is known to be "more-specific" > 140 than a Geo-Prefix when its physical location is within the > 141 geographic circle. > Jim> Update both the above to remove whitespace. For example /Geo-Point > /Geo-point: > Jim _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
