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.

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

Jump to bottom

Netconf framing #50

Closed
SCadilhac opened this issue Oct 27, 2018 · 2 comments
Closed

Netconf framing #50

SCadilhac opened this issue Oct 27, 2018 · 2 comments
Assignees
@s-bauer
Labels
feature request

Comments

@SCadilhac
Copy link
Contributor

As discussed in #39, and as described in RFC6242, section 4, Netconf defines two framing modes. Clixon only support the legacy one (based on ]]>]]> sequence). It would be great to support equally the new one (and thus have the base:1.1 capability).
@olofhagsand olofhagsand mentioned this issue Jul 24, 2020
Closed
@s-bauer
Copy link
Contributor

s-bauer commented Jun 21, 2021 •
edited
Loading

Implementation ongoing in #217

@olofhagsand olofhagsand mentioned this issue Mar 15, 2022
Closed
olofhagsand added a commit that referenced this issue Mar 28, 2022
@olofhagsand
* Implementation of "chunked framing" according to RFC6242 for Netcon…
c038c9a 
…f 1.1.

  * First hello is 1.0 EOM framing, then successing rpc is chunked framing
  * See
    * [Netconf framing](#50), and
    * [Clixon does not switch to chunked framing after NETCONF 1.1 is negotiated](#314)
* C:
  * Moved netconf framing code from netconf application to clixon lib
* Test:
  * New expecteof_netconf and adjusted other expect scripts to handle NETCONF 1.1 framing
@olofhagsand
Copy link
Member

This should now be implemented by this commit: c038c9a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s-bauer s-bauer

Labels
feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@olofhagsand @SCadilhac @s-bauer