Skip to content

Add IETF 126 feature comparison feedback notes - #46

Closed
lllyfeng wants to merge 10 commits into
mainfrom
claude/yangkit-feature-support-analysis-9izbbp
Closed

Add IETF 126 feature comparison feedback notes#46
lllyfeng wants to merge 10 commits into
mainfrom
claude/yangkit-feature-support-analysis-9izbbp

Conversation

@lllyfeng

Copy link
Copy Markdown
Contributor

Record feedback points for the YANG Libraries Feature Comparison
presentation (IETF 126 NETMOD WG). Key point: the anydata validation
"Partially Supported" rating is debatable — yangkit's explicit schema
registration requirement aligns with RFC 7950 Section 7.10 semantics,
while treating unschema'd anydata as opaque data (libyang's approach)
is preservation, not validation.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday

claude added 10 commits July 21, 2026 07:39
Record feedback points for the YANG Libraries Feature Comparison
presentation (IETF 126 NETMOD WG). Key point: the anydata validation
"Partially Supported" rating is debatable — yangkit's explicit schema
registration requirement aligns with RFC 7950 Section 7.10 semantics,
while treating unschema'd anydata as opaque data (libyang's approach)
is preservation, not validation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
YANG XPath (when/must/leafref/instance-identifier) operates on the
data tree by definition, skipping choice/case schema-only nodes.
Using XPath to query schema nodes (libyang's lys_find_xpath) is an
extra convenience, not a YANG spec requirement. yangkit-xpath fully
implements RFC 7950 XPath semantics.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
yangkit-model supports dynamic add/remove/modify of schema nodes at
design time (model editing/compilation). yangkit-data requires an
immutable schema for validation, which is correct — mutating schema
during validation is unacceptable. The test conflates model editing
(design phase) with data validation (runtime phase).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
Yangkit supports updating data nodes via setValue() followed by
validate(). Decoupling mutation from validation is a design choice
that enables efficient batch updates. The slides' own annotation
"can easily be changed in code source" contradicts the Not Supported
rating.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
yang-comparator performs schema-tree-level semantic comparison, not
text-level diff. It was the reason yangkit was chosen by Swisscom and
the author joined the YANG Module Versioning Design Team. Rating it
as "Implementable" misrepresents an already mature, production-proven
capability.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
Draft email to the presenters (INSA Lyon) with CC to netmod@ietf.org,
raising constructive feedback on 5 of 6 yangkit evaluation ratings.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
Key findings added:
- updateValueTest uses addChild() instead of setValue() (API misuse)
- Multiple anydata tests have unresolved TODOs from testers themselves
- XPath "failure" is only anydata payload traversal (same schema issue)
- Testers wrote their own schema comparator using yangkit APIs but rated
  the capability as "Implementable"

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
…less of schema

RFC 7950 Section 7.10 defines anydata as an indivisible node with no
addressable children. XPath cannot traverse into anydata internals
whether or not a schema is registered — this is the data model's
design, not an implementation gap.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
…aboration

Remove references to testers' uncertainties and personal credentials.
Reframe as capability clarification + proposal for community test spec.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UzakZ2mfgufYyjbfwBCday
@lllyfeng lllyfeng closed this Jul 23, 2026
@lllyfeng
lllyfeng deleted the claude/yangkit-feature-support-analysis-9izbbp branch July 23, 2026 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants