Hi Meir, Thanks for your review! Your concerns are addressed, please verify that it is cleared by the published document revision.
Details inlined below. On Mon, Mar 2, 2026 at 6:23 PM Meir Goldman <[email protected]> wrote: > > Hi, > > We reviewed draft-ietf-netmod-yang-module-filename (current text appears to > be -06, but preserving the Last Call subject prefix as requested). > > Issue (interop / operational): the ABNF and examples use '#' to separate the > semantic version in the YANG module filename (e.g., > "acme-router-module#2.0.3.yang", and ABNF includes ['#' ysv:version]). > > Impact: '#' is the URI fragment delimiter. In common distribution workflows > (IETF YANG module registry over HTTPS, web servers, package URLs, > documentation links), a literal '#' in the path will be interpreted as a > fragment and will not be sent in the HTTP request, so clients will request a > different resource unless they percent-encode it. This is a practical > deployment footgun and will break naive tooling and “copy/paste URL” usage. > > Proposed change (preferred): replace '#' with a delimiter that is safe in URI > path segments (unreserved) and not used by the version syntax, e.g., '~' > - Update ABNF accordingly: ... ['~' ysv:version] ... > - Update all examples and any related IANA instructions for the YANG module > registry. > > Alternative (if you keep '#'): explicitly specify that when represented in > any URI/URL context, '#' MUST be percent-encoded as %23, and clarify expected > behavior for registries and clients. (This is still error-prone compared to > changing the delimiter.) The document has been updated with Operational Considerations regarding using the "#" delimiter symbol in URI and URL contexts and also the expectations for registries and clients. -- Per > Thanks, > > > Meir Goldman > FAZON Foundation > [email protected] > https://fazon.org > _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
