1 / 10

NETCONF WG 67 th IETF San Diego, CA, USA November 6, 2006

NETCONF WG 67 th IETF San Diego, CA, USA November 6, 2006. NETCONF WG Details. Mailing List Discussion: netconf@ops.ietf.org Subscribe: netconf-request@ops.ietf.org ‘subscribe’ in the message body Archive: http://ops.ietf.org/lists/netconf/ WG Chairs Simon Leinen <simon@switch.ch>

carlotta
Download Presentation

NETCONF WG 67 th IETF San Diego, CA, USA November 6, 2006

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 WG67th IETFSan Diego, CA, USANovember 6, 2006

  2. NETCONF WG Details • Mailing List • Discussion: netconf@ops.ietf.org • Subscribe: netconf-request@ops.ietf.org • ‘subscribe’ in the message body • Archive: http://ops.ietf.org/lists/netconf/ • WG Chairs • Simon Leinen <simon@switch.ch> • Andy Bierman <ietf@andybierman.com> • WG Charter Page • http://www.ietf.org/html.charters/netconf-charter.html • WG Home Page • http://www.ops.ietf.org/netconf/

  3. Administrativia • Volunteers • Note takers for the minutes • Jabber scribe (please announce slide numbers) • Jabber proxy • Please use the microphones when asking questions • and don't forget to state your name

  4. Upcoming RFCs • Four drafts are in “Authors 48 hours” • RFC numbers have been assigned • 4741 – NETCONF base protocol • 4742 – NETCONF over SSH • 4743 – NETCONF over SOAP • 4744 – NETCONF over BEEP • Expect publication this month

  5. Active Drafts • WG Draft: • NETCONF Event Notificationsdraft-ietf-netconf-notification-04.txt • Individual Submissions: • Netconf System Architecturedraft-atarashi-netconfmodel-architecture-03.txt • Experience of implementing NETCONF over SOAPdraft-iijima-netconf-soap-implementation-01.txt • Generic Action RPC for Netconfdraft-lengyel-action-rpc-00.txt • Netconf Master-agent Sub-agent Communication Protoc'ldraft-kulkarni-netconf-subagent-prot-00.txt

  6. Agenda • Agenda bashing and other administrativia (5') • NETCONF notifications (as long as it takes) • Experiences with NETCONF over SOAP (5', if time permits)

  7. notification-04 issues • Meta-issue: apparent lack of thrust • 4th meeting on this doc (including interim) • little review, slow convergence • would like to WGLC before next meeting • Suggested approach • Reduce to include only essential mechanisms

  8. notification-04 issue: datamodel • I-D includes extensive (read-mostly) data model • Application of “eat or own dog food” • Introduces (as done here) a normative reference on datamodel draft • Do we need to query subscriptions? • Do we need to query event streams?

  9. notification-04 issue: filtering • Several ways of selecting notifications: • event streams • one or 1–n per subscription? (StreamsList) • filters • XPath and subtree • specified ad-hoc or by reference to named profile

  10. notification-04 issue: replay • Retrieval of saved notifications possible • could use normal <get>? • No combined replay/real-time (“tail -f”) • replay followed by real-time notifications • “temporal ordering” problem • Balasz suggests to address this by deferring live notifications on a session during replay • Client can specify start- but not end-time

More Related