1 / 4

NETCONF Protocol

NETCONF Protocol. IETF 61 – Washington, DC Rob Enns (rpe@juniper.net). NETCONF Protocol Draft. Current is draft-ietf-netconf-prot-04 Agenda draft-04 changes. draft-04 changes. Add detailed description of subtree filtering (issue 14.1.2) Add type attribute on filter element (issue 14.1)

kyna
Download Presentation

NETCONF Protocol

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. NETCONF Protocol IETF 61 – Washington, DC Rob Enns (rpe@juniper.net)

  2. NETCONF Protocol Draft • Current is draft-ietf-netconf-prot-04 • Agenda • draft-04 changes

  3. draft-04 changes • Add detailed description of subtree filtering (issue 14.1.2) • Add type attribute on filter element (issue 14.1) • Add #xpath capability (issue 14.1) • Update security considerations (action from IETF 60) • Add default-operation parameter to <edit-config> (action from IETF 60) • <target> is now a mandatory parameter for <lock> and <unlock>. There is no default target (action from IETF 60) • <rpc-reply> for <get-config> returns <data> element, not <config> element (issue 14.1) • Remove XML schema for NETCONF state data (action from IETF 60)

  4. draft-04 changes • Correct namespace handling a number of examples. The fix is to put the device's configuration under a top level tag called <top> which is in the device's namespace • Remove XML usage guidelines. Add a section on XML considerations covering the NETCONF namespace and no DTD restriction (action from IETF 60). • Update and reformat protocol XSD • Fix <edit-config> examples in Appendix D • Use message-id 101 everywhere • Typo: change confirmed-timeout -> confirm-timeout in XSD • Typo: correct misnaming of test-option parameter in text for the validate capability

More Related