Hi Martin, I would prefer not using "reg" since it will always be an abbreviation for a machine language register to me. I'd favor using "registry" in the module name and the more cryptic "reg" in the module prefix. Thanks, Acee
On 7/20/18, 9:46 AM, "netmod on behalf of Martin Vigoureux" <[email protected] on behalf of [email protected]> wrote: Hello As part of a recent IESG review (of draft-bfd-yang) a point came up on the use of "iana" in yang modules' name/namespace/prefix. This is typically used in the case where the module refers to an IANA maintained registry. However, the point raised was that the name of the registry operator might not always be IANA, and that using that name might not put modules on the most stable deployment footing under all possible circumstances. On top of that, as far as I can tell, the use of "iana" is an undocumented convention. So, I wanted to collect views: on whether a convention should be documented, and, with regards to the point raised in IESG, on whether that keyword should be changed going forward. In that context, what about "reg" (for registry) or "regop" (for registry operator)? Other proposals are welcome. Thanks -m _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
