draft-dickinson-dnsop- nameserver-control-01 Stephen Morris - - PowerPoint PPT Presentation

draft dickinson dnsop nameserver control 01
SMART_READER_LITE
LIVE PREVIEW

draft-dickinson-dnsop- nameserver-control-01 Stephen Morris - - PowerPoint PPT Presentation

draft-dickinson-dnsop- nameserver-control-01 Stephen Morris stephen@isc.org 1 NSCP Function Breakdown Commands - start, stop, halt etc. Zone manipulation add/remove zone, ACL creation, etc. Parameters - control nameserver


slide-1
SLIDE 1

draft-dickinson-dnsop- nameserver-control-01

Stephen Morris stephen@isc.org

1

slide-2
SLIDE 2

Function Breakdown

  • Commands - start, stop, halt etc.
  • Zone manipulation – add/remove zone,

ACL creation, etc.

  • Parameters - control nameserver

behaviour

  • Statistics - obtain information from

nameserver

  • Zone data - manipulation of small

amounts of zone data?

2

NSCP

slide-3
SLIDE 3

Object Model

3

NSCP

Server Peers Peer

1 *

Panorama ACL Zone View

1 * 1 * 1 *

DNSSEC Policy Statistics

slide-4
SLIDE 4

Transport Mechanism

  • NETCONF (RFC 4741)

– Designed for controlling network devices – Persistent connections – Basic protocol superstructure – Commands to manipulate configuration

  • <get-config>, <edit-config>, <lock>, etc

– Able to transport any XML data over it – Extensible

4

NSCP

slide-5
SLIDE 5

NSCP

  • Breaks basic functionality into several

capabilities:

– Base – understands basic data model – Basic Control - stop/reload/restart – Start Control - start

  • Additional functionality by defining

additional capabilities

5

slide-6
SLIDE 6

Comparison to Requirements (1)

  • Expected Deployment Scenarios

– Nothing restricts size of zone deployed. – Nothing restricts configuration data volatility. – Supplies a common data model.

  • Nameserver Types

– No constraint on type of server that can be managed.

6

slide-7
SLIDE 7

Comparison to Requirements (2)

  • Control Requirements

– Supplies basic start/stop/reload – Asynchronous notification supported by NETCONF [RFC5277]

  • Configuration Requirements

– Can add/delete/modify zones – Potentially add zone data – Able to handle DNSSEC configuration – Able to limit access to zones/functions

7

slide-8
SLIDE 8

Comparison to Requirements (3)

  • Monitoring Requirements

– Statistics part of base data model

  • Alarm and Event Requirements

– Built on asynchronous notification

8

slide-9
SLIDE 9

Comparison to Requirements (4)

  • Security Requirements

– Provided mainly through NETCONF transport layer

  • Other Requirements

– Extensible via NETCONF capabilities

9