What would a "better" system mean

["Cullen Jennings" <fluffy@cisco.com>]

I would not get too hung up on what has been deployed because pretty much
every combination of SOAP/XML/HTTP/SSH/Telnet/Corba has been deployed in
some non trivial way.

I think the start is focusing on what the hard problems are. Then figure out
how to make them so easy that people building equipment find it easier to
build in the standard thing, than building in some half baked home grown
CLI. This may be impossible but it seems to be the key item to making this
useful in the long term.

I have yet to been to a meeting planning the development schedule for a new
product where someone said "We could shave 1 month off the schedule if, in
the first version of the product, we only supported SNMP instead of CLI. We
can add in CLI on version 2." Ok, so I have been sniffing something, but if
there was something that reduced development effort and still solved the
real problems - it would be fairly popular.

Cullen


> -----Original Message-----
> From: owner-xmlconf@ops.ietf.org [mailto:owner-xmlconf@ops.ietf.org]On
> Behalf Of RJ Atkinson
> Sent: Wednesday, June 26, 2002 7:48 AM
> To: Eliot Lear
> Cc: xmlconf@ops.ietf.org
> Subject: Re: Deja vu Again
>
>
>
> On Wednesday, June 26, 2002, at 10:39 , Eliot Lear wrote:
>
> > sshv2 could certainly be added to the list, but it doesn't provide
> > sufficiently
> > rigorous syntax for transactions.  it's like doing mail through telnet,
> > and then invoking sendmail.
>
> It is already *implemented* and operators are experimenting with
> *deploying*
> XML/SSHv2+glue.  In my mind, having folks actually looking into deploying
> something makes that approach very seriously interesting.
>
> And the transaction support is handled using XML in the current stuff,
> or so I'm being told.
>
> Ran
> rja@extremenetworks.com
>
>
> --
> to unsubscribe send a message to xmlconf-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/xmlconf/>
>


--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>