[NETCONF-1018] NetconfNotification confuses its namespace Created: 05/May/23  Updated: 06/May/23  Resolved: 06/May/23

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: 2.0.17, 3.0.9
Fix Version/s: 6.0.0, 4.0.7, 5.0.7

Type: Bug Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: day-0-bug, pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to CONTROLLER-1112 Implement notification support in net... Resolved
relates to NETCONF-1019 Create NamespaceURN constant holder Resolved

 Description   

This is a day-0 bug in NETCONF server implementation: at least the event time, and most likely the entire NetconfNotification document, mishandles its namespace.

The problem is with NetconfNotification.NOTIFICATION_NAMESPACE, introduced here: https://git.opendaylight.org/gerrit/c/controller/+/14921/5/opendaylight/netconf/netconf-notifications-api/src/main/java/org/opendaylight/controller/netconf/notifications/NetconfNotification.java#24

The namespace points to the Notification CAPABILITY URN:

urn:ietf:params:netconf:capability:notification:1.0

not to the Notification XML Namespace URN:

urn:ietf:params:xml:ns:netconf:notification:1.0

The latter needs to be used, as exemplified in https://datatracker.ietf.org/doc/html/rfc5277#page-27
Generated at Wed Feb 07 20:16:28 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.