Hi Dino, First my apologies, this is long overdue. I’m trying to catch up with my shepherd’s review of draft-ietf-lisp-name-encoding and I have some comments/suggestions on the current draft.
* Sec 3: You describe that when a DN is used as an EID, an exact match is performed (which is correct). However, this is described in the format section of the document, shouldn’t this be discussed somewhere else (maybe on its own section)? I know this is a very short document, but having that behavior described in the format section seems odd to me. No strong opinion though. * Sec 4: You say it in the title of the section already, but it might be interesting that on the body of the section you mention that the listed use-cases are examples and more importantly that we explicitly say that that other use-cases not listed are possible as well. Typo: s/ascii/ASCII * Sec. 5: I think that this section should talk about unique Instance-IDs (IIDs), not VPNs, so that the text is more general while preserving the considerations about name collisions. We can point to the VPN draft to mention one example of how a particular use-case is registering DNs in unique IIDs, see also the next point on this. * Sec. 8: If we talk about IIDs in Section 5, there is no need to keep the VPN draft as a Normative Reference and could be moved to Informative, easing the RFC process. Thanks, Alberto
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
