Skip to content

Add support for yang-data+xml and yang-data+json#56

Open
mjethanandani wants to merge 3 commits into
v16from
issue-55
Open

Add support for yang-data+xml and yang-data+json#56
mjethanandani wants to merge 3 commits into
v16from
issue-55

Conversation

@mjethanandani

Copy link
Copy Markdown
Contributor

No description provided.

@mjethanandani mjethanandani requested review from avtobiff and kwatsen May 11, 2026 07:41
@mjethanandani mjethanandani self-assigned this May 11, 2026
@mjethanandani mjethanandani linked an issue May 11, 2026 that may be closed by this pull request
@kwatsen

kwatsen commented May 11, 2026

Copy link
Copy Markdown
Contributor

I sent a message to the list asking for a clarification on the correctness of using "yang-data"

@kwatsen

kwatsen commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

I did send a message to the list, and Alex replied, effectively, that the current PR is okay. That said, he also wrote;

That said, if the authors really do want to add HTTPS-Notif support for legacy (RFC5277), then the way I would do it is adding a new Section after Section 4, stating that this spec can also be used with legacy notifications as defined in RFC5277. In this section, I would add a paragraph stating how this mechanism is used (using application/xml as media type when sending Notifications, and how are the capabilities advertised in a RFC5277 environment).

Which I think should be done.

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.

Support for draft-ietf-netconf-notif-cbor draft.

2 participants