[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 7.1: Mandatory-to-implement criteria
>>>>> Andy Bierman writes:
Andy> I would like the WG to comment on this issue, state your
Andy> preferred solution and why:
Andy> a - pick SSH as the mandatory mapping
Andy> b - pick BEEP as the mandatory mapping
Andy> c - pick SOAP/HTTP as the mandatory mapping
Andy> d - accept the 7.1 proposal
Andy> e - accept the 7.1 proposal, but consider deployment
Andy> issues, not just implementation issues
Andy> f - create a requirements list and evaluate all
Andy> 3 drafts against this list
I vote for option a) since this is what operators have and what script
writes enjoy. The ideas behind BEEP are cool but BEEP (like SCTP) is
at the moment just not used widely used and readily available
everywhere. If you are a real soap/web-services fan, you either want
real web services or you have to wrap netconf with web services
anyway. In fact, I believe that web-services play a role above the
element manager, not necessarily as an interface to the device itself.
Approaches which require to compile a requirements list and to
evaluate the approaches will a) take a long time to complete and b)
not work very well since we basically know the strong/weak points of
the mappings so everybody will make sure the requirements document
looks good from his perspective and so this is not going to be fun and
end any time soon. Collecting requirements is good when you start and
you need to better understand the problem, but now we are already in
the middle the development of the product.
This is my opinion - nobody is expected to agree (so don't hit reply
;-)
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
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/>