Netconf WG IETF 66 and Montreal Interim Meeting Agenda (draft)

[Andy Bierman <ietf@andybierman.com>]

Hi,

Here is the first draft of the interim agenda for comment:
[resend]

---------------

The NETCONF WG will meet at IETF #66, and the Montreal interim meeting
following, to work on NETCONF Notifications work item.

- Interim Meeting Location
  IETF Headquarter Hotel: Delta Centre-Ville
  777 University Street
  Montreal, Quebec, Canada, H3C 3Z7
  Hotel WEB site:
  http://www.deltahotels.com/hotels/hotels.php?hotelId=35

- Interim Meeting Times
  Friday, July 14, 2006 (1:30 PM - 6:00 PM)
  Saturday, July 15, 2006 (9:00 AM - 6:00 PM)

- Required Reading
  NETCONF Event Notifications

http://www.ietf.org/internet-drafts/draft-ietf-netconf-notification-01.txt


The following is a proposed issues list.  The discussion sequence at the
meetings will generally follow this list, but issues that are inter-related
may affect the order.  The official WG meeting on July 14, 9:00 - 11:30 AM
will be used to discuss and prioritize functional requirements.


- Functional Requirements
  - determine WG consensus on need and priority of Juergen's list
    http://www.eecs.iu-bremen.de/wiki/index.php/Netconf_notifications

- Architecture

  - role of notifications within netconf
  - relationship to syslog and snmp notifications
  - scaling issues
  - security issues (session vs. signed msg, etc.)
  - standard RPC methods vs. new RPC methods
  - agent resource vs. NMS resource issues

- Use within Sessions

  - endless RPC
  - mixed-mode (rpc operations and notifications)
  - single vs. multiple subscriptions within a single session


- Transport Specific Support

  - use of channels (ssh, beep, what about soap?)
  - callhome support for agent initiated sessions

- Agent Notification Configuration and Control Mechanism

  - config-data vs. subscription-data
  - RPCs used to configure and control agent notification generation

- Notification Event Classes

  - WG consensus on specific list
  - Guidelines for selecting classifications

- Notification Filtering

  - Configuration mechanism(s)
  - Agent processing model

- Notification Header Content

  - Syntax and semantics of data included in all notifications

- Standard Notification Content

  - WG consensus on 0 or more fully-specified standard notifications
  - Full syntax and semantics of each standard notification

- Read-only (monitoring) data for agent notification activity

- Access Control Issues

- Data Model and XSD Issues

  - Data model design
  - XSD correctness
  - Need for 'min-access' and 'max-access'

- Documentation Issues

  - Terminology
  - Inclusion of non-normative text
  - Document section order
  - Document clarity
  - Choice of examples
  - Example correctness (need to validate against the XSD)





--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>