netconf-monitoring_schema.txt
[CONTROLLER-1272] netconf-monitoring model - parsing too strict in ODL Created: 22/Apr/15 Updated: 25/Jul/23 Resolved: 27/Apr/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Manjunath Patil | Assignee: | Tomas Cere |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
netconf-monitoring_schema.txt
|
| External issue ID: | 3045 |
| Description |
|
schema ietf-netconf-monitoring 2010-10-04 ncm:yang { identifier ietf-netconf-monitoring version 2010-10-04 format ncm:yang namespace urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring location NETCONF conformance true module-type module } |
| Comments |
| Comment by Manjunath Patil [ 22/Apr/15 ] |
|
Attachment netconf-monitoring_schema.txt has been added with description: attached file has the schema we use |
| Comment by Tomas Cere [ 22/Apr/15 ] |
| Comment by RichardHill [ 23/Apr/15 ] |
|
How does strict parsing cause a problem with the netconf-monitoring model? |
| Comment by Tomas Cere [ 23/Apr/15 ] |
|
If the remote device's netconf monitoring schema has augments for example that we don't have schema yet while parsing the hello message, parsing would fail on unknown nodes, if you make it less strict just for the hello message all unknown nodes are ignored. |