Re: Issue 7.1: Mandatory-to-implement criteria

[Margaret Wasserman <margaret@thingmagic.com>]

Hi All,

> I would like the WG to comment on this issue, state
> your preferred solution and why:
>
>   a - pick SSH as the mandatory mapping
>   b - pick BEEP as the mandatory mapping
>   c - pick SOAP/HTTP as the mandatory mapping
>   d - accept the 7.1 proposal
>   e - accept the 7.1 proposal, but consider deployment
>       issues, not just implementation issues
>   f - create a requirements list and evaluate all
>       3 drafts against this list

I have a preference for option (a) -- pick SSH as the mandatory
mapping.  However, I do think that most equipment vendors will
also choose to implement BEEP, because it will present a better
programmatic interface for developers of sophisticated management
applications.

I have several reasons for prefering SSH as the mandatory
mapping:

    1 - Operators have expressed a consistent preference
        for an SSH mapping, mostly based on that fact that
        they are already familiar with SSH and have deployed
        infrastructure to support its use for device
        configuration.
    2 - SSH is the simplest mapping and leverages code that
        already exists on many devices, so this offers the
        lowest implementation hurdle (in developer time,
        code size, etc.) to add NETCONF to a device.
    3 - SSH provides a simple, well-understood interface
        for script writers, so I think this mapping is
        valuable in its own right.

Margaret


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