Skip to content

editorial and nits #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ahuangfeng wants to merge 1 commit into
base: main
Choose a base branch
from
Open

editorial and nits #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions draft-aelhassany-anydata-validation-00.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,25 +81,25 @@ Table of Contents
IETF models, e.g., [RFC7895], [RFC8526], [RFC9144], [RFC8639],
[RFC8641], and [RFC8040], use "anydata" in their definitions.
Current YANG implementations accept syntactically valid YANG data
nodes as children of an "anydata" node but do not check the semantics
of these data nodes against a YANG schema. This creates a real
nodes as children of an "anydata" node but do not check the data
types of these data nodes against a YANG schema. This creates a real
problem for any consumer of these models when validating all leaves
of the YANG data tree.

YANG Schema Mount [RFC8528] allows mounting complete data models at
implementation and run time. While powerful, schema mount cannot
address use cases where the user selects an arbitrary subset of an
instantiated data tree, such as YANG PUSH [RFC8641]. A current
instantiated data tree, such as YANG-Push [RFC8641]. A current
proposed approach, YANG Full Include YANG Full Include
[I-D.jouqui-netmod-yang-full-include], complements YANG Schema Mount
and applies at design time, yet cannot address dynamic filtering of
an instantiated YANG data tree.

In this document we propese using YANG Library [RFC7895] to define
the context in which anydata trees are validated. This would require
the YANG tooling to implement an optional flag that enables a a flag
for validating "anydata" subtrees in the context of a YANG library.

In this document we propose using the YANG Library [RFC7895] to
define the context in which anydata trees are validated. This would
require the YANG tooling to implement an optional flag that enables a
flag for validating "anydata" subtrees in the context of a YANG
library.



Expand Down
8 changes: 4 additions & 4 deletions draft-aelhassany-anydata-validation-00.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,24 +66,24 @@
target="RFC8639"/>, <xref target="RFC8641"/>, and <xref
target="RFC8040"/>, use "anydata" in their definitions. Current YANG
implementations accept syntactically valid YANG data nodes as children
of an "anydata" node but do not check the semantics of these data nodes
of an "anydata" node but do not check the data types of these data nodes
against a YANG schema. This creates a real problem for any consumer of
these models when validating all leaves of the YANG data tree.</t>

<t><xref target="RFC8528">YANG Schema Mount</xref> allows mounting
complete data models at implementation and run time. While powerful,
schema mount cannot address use cases where the user selects an
arbitrary subset of an instantiated data tree, such as <xref
target="RFC8641">YANG PUSH</xref>. A current proposed approach, YANG
target="RFC8641">YANG-Push</xref>. A current proposed approach, YANG
Full Include <xref target="I-D.jouqui-netmod-yang-full-include">YANG
Full Include</xref>, complements YANG Schema Mount and applies at design
time, yet cannot address dynamic filtering of an instantiated YANG data
tree.</t>

<t>In this document we propese using <xref target="RFC7895">YANG
<t>In this document we propose using the <xref target="RFC7895">YANG
Library</xref> to define the context in which anydata trees are
validated. This would require the YANG tooling to implement an optional
flag that enables a a flag for validating "anydata" subtrees in the
flag that enables a flag for validating "anydata" subtrees in the
context of a YANG library.</t>

<section>
Expand Down