Skip to main content

YANG Schema Mount
draft-ietf-netmod-schema-mount-12

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: ibagdona@gmail.com, netmod-chairs@ietf.org, netmod@ietf.org, The IESG <iesg@ietf.org>, joelja@gmail.com, draft-ietf-netmod-schema-mount@ietf.org, Kent Watsen <kwatsen@juniper.net>, Lou Berger <lberger@labn.net>, Joel Jaeggli <joelja@gmail.com>, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'YANG Schema Mount' to Proposed Standard (draft-ietf-netmod-schema-mount-12.txt)

The IESG has approved the following document:
- 'YANG Schema Mount'
  (draft-ietf-netmod-schema-mount-12.txt) as Proposed Standard

This document is the product of the Network Modeling Working Group.

The IESG contact persons are Warren Kumari and Ignas Bagdonas.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/


Ballot Text

Technical Summary

This document specifies a mechanism for merging in a (subset of) YANG module schema into a schema of another YANG module. The main use case is the scalability of schema definition for repeated fragments of YANG modules.


Working Group Summary

The schema mount document has been in active development around the timeframe when NMDA solution was being developed in parallel, and therefore the alignment between the two was not always present. This resulted in a major discussion in the WG, and eventually was resolved to a strong consensus.
 

Document Quality

There are active drafts that use this mechanism for defining a YANG model hierarchy for representing routing in partitioned network elements (the work of Routing YANG Design Team). There is an indication from the community that both closed and open source implementations are in the works. 


Personnel

Document Shepherd is Joel Jaeggli. Responsible AD is Ignas Bagdonas. 


IANA Note

This document adds entries to existing XML URI and YANG Module Names registries.

RFC Editor Note