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

Re: Status of Schema advertisement drafts WAS: FW: Status of netconf-schema-query



Hello Okita,
How will your solution support people that do not use SOAP or SSH?

I feel it does not. I think saying that if you want to query the schemas you MUST support SOAP is not something I would like.

Martin's solution does not require any new NETCONF infrastructure.
regards Balazs

OKITA Hideki wrote:
Martin,


Thank you for your comment.


I would prefer a generic transport agnostic method for this problem.

How about to use each transport for each mapping?

I can aggree with you if we limit the usecase into post-deployment phase
which has active NETCONF sessions. However, in pre-deployment phase like
NMS development, all development environment does not have ability to
talk NETCONF sessions. Most of environment that we presume support HTTP to
take service advertisement information written in WSDL.

IMO, transport selection is not a main issue.
The main issue is how to describe/summarize schema information.


I proposed one solution in
http://ops.ietf.org/lists/netconf/netconf.2007/msg00698.html.

In this mail you proposed "a mechanism to retrieve the actual schema over NETCONF." I prefer this approach. WSDL approach also realizes this. It can contain actual schema definitions in <wsdl:types> element.

Example WSDL structure:

<wsdl:definitions
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
  xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

  <wsdl:types>
    <xsd:schema>
      (Schema Definitions)
    </xsd:schema>
  </wsdl:types>

  ...
</wsdl:definitions>

IMO, Using WSDL to describe/summarize schema information is a transport agnostic and well standardized method.
It works for any transport.


Regards,

Hideki Okita




From: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: Status of Schema advertisement drafts WAS: FW: Status of netconf-schema-query
Date: Wed, 20 Feb 2008 21:11:29 +0100 (CET)

Hi,

AFAICT, the method defined in draft-okita-netconf-advertisement-00.txt
works for NETCONF over SOAP, but not for the other transports (SSH and
BEEP).  The methods listed in draft-scott-netconf-schema-query-00
works for any transport.  I would prefer a generic transport agnostic
method for this problem.

I proposed one solution in
http://ops.ietf.org/lists/netconf/netconf.2007/msg00698.html.  I would
be happy to work with Mark Scott on a schema discovery document.

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

--
Balazs Lengyel                       Ericsson Hungary Ltd.
TSP System Manager
ECN: 831 7320                        Fax: +36 1 4377792
Tel: +36-1-437-7320     email: Balazs.Lengyel@ericsson.com

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