[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D ACTION:draft-weijing-netconf-interface-00.txt

Hi All,

I have a few comments on draft-weijing-netconf-interface-00.txt.

The documents relating to this discussion are:

    draft-enns-xmlconf-spec-00.txt          (xmlconf-spec)
    draft-goddard-netconfsoap-00.txt        (netconfsoap)
    draft-weijing-netconf-interface-00.txt  (netconf-interface)

In terms of scope, netconf-interface addresses a subset of what is
addressed in xmlconf-spec.  Both netconfsoap and netconf-interface
exhibit SOAP-based techniques for device management, but netconfsoap
extends xmlconf-spec while netconf-interface requires new
management operations.

If netconf-interface is taken as a response to xmlconf-spec, the
interpretation could be that the xmlconf-spec semantics (such as
for manipulating configurations) are seen to be not generic enough;
yet all of the examples in netconf-interface  easily fit into the
xmlconf-spec model.  If there are use cases that break xmlconf-spec,
they should be presented; otherwise, it may be that xmlconf-spec is
already generic enough.

The Abstract of netconf-interface posits that multiple transports
(such as SOAP and SSH) should be supported.  By itself this is
reasonable, but it does not provide justification for making the
operations themselves more generic, as this comes at the expense of
interoperability.

1.

It is implied that WSDL is generic enough to describe
the SSH and BEEP bindings as well as the SOAP binding.  This
may be reasonable in the future, but neither BEEP nor SSH are
currently included in the WSDL specification, and neither BEEP
nor SSH is currently supported by WSDL tools.  BEEP and SSH are
useful transports, but they are not easily captured by WSDL
today.

2.1.1

By placing the "operation" as an attribute on the <perform-request>,
there is reduced opportunity for schema validation on the operation.
In contrast, this is an important form of type-checking in xmlconf-spec.

Why are "get-readwrite" and "get-readonly" special types of actions?
Perhaps the elements in the data model should have read/write attributes
and the value of this attribute should be specified in the query?

2.3

A rich data model for capabilities is appealing, but using such
fine-grained control could greatly increase application complexity.

Regards,
Ted Goddard.




On Friday, June 27, 2003, at 01:33 PM, Chen, Weijing wrote:
Forwarding the following announcement from IETF announcement list.





A New Internet-Draft is available from the on-line Internet-Drafts
directories.





Title : XML Network Management Interface

Author(s) : W. Chen, K. Allen

Filename : draft-weijing-netconf-interface-00.txt

Pages : 23

Date : 2003-6-26



This document describes XML network management interface between

network managed system and network managing system. The XML network

management interface is intended for use in diverse network

environment where transport and data model requirements vary

greatly. It is unlikely that a single transport and data model

specification will meet the needs of all anticipated service

operators. Therefore, the XML network management interface is

partitioned into the layered components.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-weijing-netconf-interface- 00.t
xt
<http://www.ietf.org/internet-drafts/draft-weijing-netconf-interface- 00.
txt>



To remove yourself from the IETF Announcement list, send a message to

ietf-announce-request with the word unsubscribe in the body of the
message.



Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then

"get draft-weijing-netconf-interface-00.txt".



A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html <http://www.ietf.org/shadow.html>

or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
<ftp://ftp.ietf.org/ietf/1shadow-sites.txt>











--

Weijing Chen




--
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/>