1 / 14

Netconf Event Notifications IETF 66 Overview

This document outlines key features, architecture, requirements, issues, and bugs related to Netconf event notifications as discussed at IETF 66 by Sharon Chisholm and Hector Trevino. Key features include clean subscription management, event classes for filtering, and support for Netconf content. The architecture shows the interaction between network elements, Netconf stack, clients, and other protocols. The message flow and format are detailed, along with requirements, issues, and bugs.

mauricedarby
Download Presentation

Netconf Event Notifications IETF 66 Overview

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 Event Notifications IETF 66 Sharon Chisholm schishol@nortel.com Hector Trevino htrevino@cisco.com

  2. Outline • Key Features • Architecture • Requirements • Issues • Bugs

  3. Key Features • Clean subscribe/unsubscribe to notifications of interest • Modification of subscription without loss of notifications • Event Classes to enable ‘big bucket’ filtering • Ability to carry Netconf-content

  4. Netconf Layers Layer Example +-------------+ +----------------------------------------+ | Content | | Configuration data | +-------------+ +----------------------------------------+ | | +-------------+ +-------------------------------------------+ | Operations | | <get-config>, <edit-config> <notification>| +-------------+ +-------------------------------------------+ | | | +-------------+ +-----------------------------+ | | RPC | | <rpc>, <rpc-reply> | | +-------------+ +-----------------------------+ | | | | +-------------+ +------------------------------------------+ | Application | | BEEP, SSH, SSL, console | | Protocol | | | +-------------+ +------------------------------------------+

  5. An Architecture .... ---------------------------------------------- | Network Element | | ------------ | | | Alarm | | | | Management | -------------- | -------------- | ------------ |--->|Netconf Stack |<---------->| Netconf | | | | | | | | | | | | -------------- | --->| Client | | V | | | -------------- | ------------ | | | | | Event |--->| ------------------ | | | | Management | | |Other Protocols | | | | ------------ |--->| | | | | ------------------ | | |--------------------------------------------- | | ---------------------------------------------- | | Network Element | | | ------------ | | | | Alarm | | | | | Management | -------------- | | | ------------ |--->|Netconf Stack |<-------| | | | | | | | | | -------------- | | V | | | ------------ | | | | Event |--->| ------------------ | | | Management | | |Other Protocols | | | ------------ |--->| | | | ------------------ | |--------------------------------------------

  6. Message Flow C S | | | capability exchange | |-------------------------->| |<------------------------->| | | | <create-subscription> | |-------------------------->| |<--------------------------| | | | <notification> | |<--------------------------| | | | <notification> | |<--------------------------| | | | <modify-subscription> | |-------------------------->| (buffered) | <notification> | |<--------------------------| | <rpc-reply> | |<--------------------------|

  7. Message Format ___________________________________________________________________ || Notification Header || Data | ||__________________________________________________________||______| || subscriptionId| eventClasses| sequenceNumber| dateAndTime|| | ||_______________|_____________|_______________|____________||______|

  8. Requirements

  9. Requirements

  10. Requirements

  11. Requirements

  12. Issues - Big • Endless RPC versus Notifications • Syslog Tunnelling versus Notification Framework

  13. Issues – Less Big • Best way to have initial set up event classes while allowing extensibility • Create separate Event Class document? • More details of callHomeNotifications

  14. Bugs • Missing ‘data’ element from Notification XSD definition

More Related