Roman Danyliw has entered the following ballot position for
draft-ietf-lisp-name-encoding-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to 
https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lisp-name-encoding/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Jouni Korhonen for the GENART review.

** Section 3
   When Distinguished Names are encoded for EIDs, the EID-Prefix length
   of the EIDs as they appear in EID-Records for all LISP control
   messages [RFC9301] is the length of the string in bits (including the
   null 0 octet).

Is “EID-Prefix length” described here the same as “EID mask-len” described in
RFC9301?  “EID-Prefix length” is not a string found in FC9301.

** Section 3
   The string of characters are encoded in the ASCII character-set
   definition [RFC0020].

To confirm, any RFC20 ASCII string is a valid EID?  For example, “0x01 0x02
0x03 0x04” would be valid?  How would a non-terminating 0x00 be handled – is
that invalid?

I concur with the SECDIR reviewer (Rich Salz) that it would be helpful to
explain this design choice.

** Section 5.
   An RLOC that describes an Ingress or Egress
   Tunnel Router (xTR) behind a NAT device can be identified by its
   router name, as in [I-D.farinacci-lisp-lispers-net-nat]

Per [I-D.farinacci-lisp-lispers-net-nat]
(draft-farinacci-lisp-lispers-net-nat): Given that the IESG conflict review on
this document came back as “Request not to publish”
(https://datatracker.ietf.org/doc/conflict-review-farinacci-lisp-lispers-net-nat/),
is the WG confident that it makes sense to mention this document here?



_______________________________________________
lisp mailing list -- lisp@ietf.org
To unsubscribe send an email to lisp-le...@ietf.org

Reply via email to