Hi, Revising RFC8366 has been fraught with difficulties. At ANIMA@IETF119 in Brisbane we concluded with just merging all extensions into RFC8366bis.
Meanwhile RFC8520 (MUD) has a few extensions, the licensing one most recently, which does something completely different. I didn't realize it was doing it this way. To quote the document below. I started a document to make this mechanism more generic. Name: draft-richardson-netmod-atrest-extensions Title: Extending YANG modules at runtime URL: https://www.ietf.org/archive/id/draft-richardson-netmod-atrest-extensions-00.txt This is far from complete, but the basic idea is there. I would sure like to discuss this more, and I am to rotten tomatoes and all sorts of other vegetables, rotten or not. I would like to consider doing this for RFC8366bis. 3.9. extensions This optional leaf-list names MUD extensions that are used in the MUD file. Note that MUD extensions MUST NOT be used in a MUD file without the extensions being declared. Implementations MUST ignore any node in this file that they do not understand. Note that extensions can either extend the MUD file as described in the previous paragraph or reference other work. An extension example can be found in Appendix B. ... 2. At a finer grain, only extensions that would not incur additional risk to the Thing are permitted. Specifically, adding nodes to the mud container is permitted with the understanding that such additions will be ignored by unaware implementations. Any such extensions SHALL be standardized through the IETF process and MUST be named in the "extensions" list. MUD managers MUST ignore YANG nodes they do not understand and SHOULD create an exception to be resolved by an administrator, so as to avoid any policy inconsistencies. 17.8. Extensions Registry The IANA has established a registry of extensions as follows: Registry name: MUD Extensions Registry policy: Standards Action Reference: RFC 8520 Extension name: UTF-8-encoded string, not to exceed 40 characters. Each extension MUST follow the rules specified in this specification. As is usual, the IANA issues early allocations in accordance with [RFC7120].
signature.asc
Description: PGP signature
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
