Document: draft-ietf-lisp-geo
Title: LISP Geo-Coordinates
Reviewer: Tim Wicinski
Review result: Ready
Reviewer: Tim Wicinski
Review Result: Ready
I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the IESG. These
comments were written with the intent of improving the operational aspects of
the
IETF drafts. Comments that are not addressed in last call may be included in AD
reviews
during the IESG review. Document editors and WG chairs should treat these
comments
just like any other last call comments.
Document: draft-ietf-lisp-geo-12
Reviewer: Tim Wicinski
Intended Status: Experimental
In the IANA Considerations, the second paragrapgh in this section should be
moved
after the table. For example:
Following the guidelines of [RFC8126], IANA is asked to assign a
value (17 is suggested) for the Geo-Coordinates LCAF from the "LISP
Canonical Address Format (LCAF) Types" registry (defined in [RFC8060]
as follows:
+=========+=====================+============================+
| Value # | LISP LCAF Type Name | Reference |
+=========+=====================+============================+
| 17 | Geo-Location | [This Document], Section 5 |
+---------+---------------------+----------------------------+
Table 1: Geo-Location LCAF Type Assignment
This document updates the format of LCAF Type value 5 in
[RFC8060], IANA is asked to mark type value 5 as "Deprecated".
--
RFC8060 doesn't really mention how to deal with deprecated entries to the
registry, I suggest some slight changes to the text here.
_______________________________________________
lisp mailing list -- [email protected]
To unsubscribe send an email to [email protected]
