NETCONF meeting at IETF62 - Andy Bierman's notes

BEEP draft (to do)

• need to add examples
• hello message not completely documented
• SASL/TLS combination needs some clarification
• application protocol (terminology edits)

XSD cannot be used to completely validate NETCONF messages because capabilities that are present on an agent will change the actual XML accepted by the agent. XSD cannot express multiple variants of valid XML instance documents based on these capabilities.

The WG needs to ask the XML Directorate to review the XML usage in NETCONF.

There was a request to provide a non-secure transport for NETCONF. Currently, security (e.g., encryption) is mandatory to implement but optional to deploy for the user. There will not be any changes to accommodate non-secure implementations of NETCONF.

SSH draft

SSH issue: what is the client is idle and holds a lock? Not an issue -- this has been discussed before by the WG; the kill-session operation can be used to break a lock.

PROT document issues

• need some examples in section 6 (filtering).
• need to validate the examples (again).
• need to clarify error code to return for lock operation
• LOCK_FAILED should be used instead of IN_USE

Presentation on NETMOD (see slides)

Discussion of NETCONF modeling and new features after official meeting

• notifications (async messages in general) have been requested by some people; still controversial; notion of non-notification async messages (e.g., send accounting records ala IPFIX) is even more controversial
• group decided individual I-Ds should be submitted which provide well-thought-out solution proposals for notifications