Netmod Netconf Data Modeling

1
NetmodNetconf Data Modeling

• Sharon Chisholm
• Nortel
• schishol_at_nortel.com

2
Outline

• Netmod Coordinates
• Netconf Layers
• Status
• Scope
• Netconf Family of Specifications
• Next Steps

3
Netmod Coordinates

• Website
• http//standards.nortelnetworks.com/netconf/
• Instructions on how to join mailing list,
  archive, documents of interest
• Mailing list
• separate list for data modeling specific
  discussions

4
Netconf Layers

• ------------- -------------------
  ----------
• (4) Content Configuration
  data
• ------------- -------------------
  ----------
• ------------- -------------------
  ----------
• (3) Operations ltget-configgt,
  ltedit-configgt
• ------------- -------------------
  ----------
• ------------- -------------------
  ----------
• (2) RPC ltrpcgt,
  ltrpc-replygt
• ------------- -------------------
  ----------
• ------------- -------------------
  ----------
• (1) Application BEEP, SSH, SSL,
  console
• Protocol
  
• ------------- -------------------
  ----------

Netmod
5
Status

• BOF at IETF 60
• Given guidance to reduce scope ...
• Several Internet Drafts
• Consolidated input into Framework for Netconf
  Data Models
• http//www.ietf.org/internet-drafts/draft-chisholm
  -netconf-model-01.txt

6
Scope

• Select a single existing data definition language
  for netconf content with emphasis placed on
  existing well-established solutions.
• Identify requirements and best practice for
  defining
• Access control
• Compliance
• Versioning backwards compatibility
• naming
• How to define relationships between elements
• Design pattern for defining status, statistics
  and configuration information
• Notifications
• Error Handling
• Element Descriptions
• Proof of concept data model definition

7
Netconf Family of Specifications
Netconf 1.0 (protocol, transports)
Netmod Framework
Netconf Protocol Extensions
IETF 62
8
Next Steps

• Netmod editing session today at 1pm, meeting at
  the bulletin board
• Because
• There doesnt appear sufficient work for two
  working groups.
• Some problems such as security (access controll,
  etc) and Notifications will span both protocol
  and data model specification
• Propose rather than creating a netmod working
  group, we add it to the netconf charter