Thanks for your comments Yingzhen. I have posted -12. See inline for responses.
> Minor Issues: > > A WiFi access-point RLOC can be selected to encapsulate > packets to because it will have better signal to the current EID > location. > This sentence doesn't parse well. I think there is an extra "to". > > So an ITR > could encapsulate to multiple RLOCs in the Geo-Prefix to try to > create connectivity to the vehicle while roaming. > Please expand "ITR". > > The new Geo-Location format is: > Please consider change this to "The Geo-Coordinates LCAF format is:", or > simply > remove the "new". Fixed the above per your suggestions. > R-bit: If the R-bit is set, it indicates the "Radius" field is used > and the encoding is a Geo-Prefix. If the R-bit is clear, it > indicates the "Radius" field is set to 0 and and the encoding is a > Geo-Point. > Question: Is this R-bit necessary? When the "Radius" is set to non-zero, it > means the encoding is Geo-Prefix, and when the "Radius" is set to 0, the > encoding is a Geo-Point. A radius of 0 is valid if the R-bit is set and the encoding is interpreted as a Geo-Prefix. So a Geo-Point at the precise location of the Geo-Prefix "is inside the Geo-Prefix". Dino _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
