Hi Dino,
Thanks for this document. I have a few comments (I have used idnits for v-07 to
help identify the relevant text).
Jim> Please fix these warnings from indits. Further comment on the first
warning below.
-- Possible downref: Non-RFC (?) normative reference: ref.
'IANA-ADDRESS-FAMILY-REGISTRY'
** Downref: Normative reference to an Informational RFC: RFC 3232
== Outdated reference: A later version (-08) exists of
draft-farinacci-lisp-lispers-net-nat-07
== Outdated reference: A later version (-07) exists of
draft-ietf-lisp-geo-06
14 Requirements Language
16 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
17 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
18 document are to be interpreted as described in [RFC2119].
Jim> Please update the requirements language section as per RFC8174.
98 1. Introduction
100 The LISP architecture and protocols [RFC9300] introduces two new
101 numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
102 (RLOCs) which are intended to replace most use of IP addresses on the
103 Internet. To provide flexibility for current and future
104 applications, these values can be encoded in LISP control messages
105 using a general syntax that includes Address Family Identifier (AFI)
106 [RFC3232].
Jim> I am confused by the reference to RFC3232. This RFC simply states that
RFC1700 is obsolete and replaced by an online database. The registry can be
found here
https://www.iana.org/assignments/address-family-numbers/address-family-numbers.xhtml#address-family-numbers-2.
Why do you not simply reference the registry?.
108 The length of the value field is implicit in the type of address that
Jim> The ‘value’ field for what? LISP control messages? Please be more explicit
in which value field you are referring too.
124 2. Definition of Terms
126 Address Family Identifier (AFI): a term used to describe an address
127 encoding in a packet. An address family currently defined for
128 IPv4 or IPv6 addresses. See [IANA-ADDRESS-FAMILY-REGISTRY] and
129 [RFC3232] for details on other types of information that can be
130 AFI encoded.
Jim> You have [IANA-ADDRESS-FAMILY-REGISTRY] as a normative reference - is it
really normative or just informative?
186 encoding. As well as identifying the router name (neither an EID or
187 an RLOC) in NAT Info-Request messages uses Distinguished Name
188 encodings.
Jim> Please correct the above sentence as it is unclear ‘what’ uses the
Distinguished Name - I am assuming the NAT Info-Request message but please
clarify that in the text.
194 IPv4 or IPv6 EIDs to the mapping system. See [RFC9301] for more
195 details. Also, the use-case documents specified in Section 5 provide
196 allocation recommendations for their specific uses.
Jim> do you mean section 5 of THIS document or RFC9301? Please clarify.
Thanks!
Jim
_______________________________________________
lisp mailing list -- [email protected]
To unsubscribe send an email to [email protected]
