1. abierman-netconf-mar07 1 NETCONF WG 68 th IETF Prague, CZ March 19, 2007

2. abierman-netconf-mar07 2 NETCONF WG Details l 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/http://ops.ietf.org/lists/netconf/ l WG Chairs »Simon Leinen »Andy Bierman l WG Charter Page »http://www.ietf.org/html.charters/netconf-charter.htmlhttp://www.ietf.org/html.charters/netconf-charter.html l WG Home Page »http://www.ops.ietf.org/netconf/

3. abierman-netconf-mar07 3 Agenda l WG Draft: »NETCONF Event Notifications draft-ietf-netconf-notification-06.txt Agenda »NETCONF Notifications: Final WG Review –discuss WGLC mailing list comments –identify any remaining unresolved issues –discuss and resolve as many identified issues as possible

4. abierman-netconf-mar07 4 Notification Draft Status l 3 week WGLC completed March 16 l Several comments made (thanks) l Only minor issues remain l Expect next draft to be the final version submitted to IESG

5. abierman-netconf-mar07 5 Notification Manager Interface l Stream Discovery: » of /ncn:eventStreams (namespace is TBD) l Start: » –start receiving notification with or without replay –NETCONF stream used if none specified –specify optional filter or profile (i.e., stored filter) l Stop: » (from a different session) »drop transport connection (from same session) l Receive Notification: » –‘replay complete’ is the only notification content defined

6. abierman-netconf-mar07 6 Namespace and Data Organization Issues l urn:ietf:params:xml:ns:netmod:event:1.0 » element » » (contains ref to ) l urn:ietf:params:xml:ns:netconf:notification:1.0 » l urn:ietf:params:xml:ns:netconf:replayNotification:1.0 » l Seems to be WG consensus to have 1 XSD and NS »which target namespace? l Seems to be WG consensus for ‘foo-bar’ naming style instead of ‘fooBar’ style

7. abierman-netconf-mar07 7 Event Class Issues l Do we need to add this field to the Replay Complete notification? l This kind of field is a registry entry »registration type is OBJECT IDENTIFIER in SMIv2 »registration type is QName in XML »currently using string which allows naming collisions between vendors »same issue applies to in l Don’t really want to start this registry and populat it, as part of the Notification (protocol) work l Propose leaving event class out of the Replay Complete notification

8. abierman-netconf-mar07 8 Create Subscription Issues l RPC method »type: rpc method type extension (no issues) »content: stream, optional filter or profile (no issues) »error response: –new error codes not needed, use existing error-tag values –Is an with a special warning about start and stop times that produce no output really needed? »documentation: –list RPC parameter names and data types here –should replay section text related to this RPC method be moved? Currently have partial documentation because of start-time and stop-time. »namespace URI: (ncn) –want 1 new namespace for all NETCONF Notification XML definitions

9. abierman-netconf-mar07 9 Notification Structure Issues l »currently defined with a mandatory container like an »should this work like the container instead? –NotificationType, like RpcOperationType, is the abstract base for notifications –Each notification defines its own FooNotificationType as an extension to NotificationType –Only the ‘notification type’ element is required to be present, like the ‘RPC method node’ element –Common ‘header’ fields that are approved later by the NETMOD WG (e.g., event-class and timestamps) can be added as attributes to the element in the future

10. abierman-netconf-mar07 10 Replay Issues l »change name to ? »change contents from (timestamp + counter) to empty? »send as first notification if all parameters well-formed, but no notifications selected? l What if valid start/stop times are in the future? l What if the time changes (e.g., daylight savings time)? »several boundary conditions to document l What if a timezone is specified but the agent does not have one set, or it is set differently?

11. abierman-netconf-mar07 11 Replay Complete Notification Issues CURRENT: informational 2007-03-19T18:42:00.000-01:00 7482 PROPOSED: (‘ncn’ only because in the same XSD)

12. abierman-netconf-mar07 12 Documentation Issues l Examples »Move examples section to a non-normative appendix »Fix examples and align naming style with NETCONF »Check XSD and examples with XSD validator »Add examples for in that section l IANA Considerations section »namespace URI for NETCONF Notifications 1.0 »any other registry requests for IANA? l XSD Issues »Fix bugs, remove unused imports »Combine all 3 XSDs into 1 XSD »Use named, reusable instead of unnamed within an decl