Skip to content
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.

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

Do we need RESTCONF depth/fields filters? #15

Open
cabo opened this issue Mar 4, 2024 · 0 comments
Open

Do we need RESTCONF depth/fields filters? #15

cabo opened this issue Mar 4, 2024 · 0 comments

Comments

@cabo
Copy link
Member

cabo commented Mar 4, 2024

(Andy Bierman, https://mailarchive.ietf.org/arch/msg/core/XLv4ZusZubBrJPC5aW7UqqeHrxw)

The client must know all of the key values in advance
before being able to use the SID of a data node
in a FETCH request. It is difficult and expensive
to retrieve the entire datastore contents at once,
just to discover the key values in use for the YANG list
entries within the datastore.

RESTCONF has the 'depth' and 'fields' filter parameters
to address this issue. NETCONF has subtree and XPath filtering.
NETCONF servers can generally support selection of 1 value or all
values, for each key.

Perhaps CORECONF will need the 'depth' filter parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant