https://github.com/anewton1998/draft-regext-rdap-extensions/issues/49
>> Section 2.2, paragraph 3 >> RDAP extensions MUST NOT define an extension identifier that when prepended >> to an underscore character may collide with an existing extension >> identifier. For example, if there were a pre-existing identifier of >> "foo_bar", another extension could not define the identifier "foo". >> Likewise, if there were a pre-existing identifier of "foo_bar", another >> extension could not define the identifier "foo_bar_buzz". However, an >> extension could define "foo" if there were a pre-existing definition of >> "foobar", and vice versa. > The normative part needs to be revised. The second example would not match > the given MUST NOT. "foo_bar_buzz" prepended to an underscore would render > "foo_bar_buzz_" which does not stay in conflict with "foo_bar" in an obvious > way. So it needs to be also forbidden for an extension identifier to collide > with any existing extension identifier suffixed with an underscore. The term > "collide" is also undefined. In my interpretation it means that it is a > substring match in the beginning of a string, correct? [JS] Yes, this should help clarify further.
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
