Hello,
To me, the issue with defaults/no-defaults is not as much an issue
of bandwidth than an issue of "ergonomics"...
If you believe that NetConf will be used by mechanical processes that
will automatically build, send, and analyze messages presumably based on
schema information (I would amost dare say "auto-magically"), then
asking for all details to be specified is not an issue.
If you believe that NetConf will be use as a more formal/neutral CLI macro/mechanization
mechanism then there will be a human behind this and the more things
those humans will have to specify, the less they'll be happy and the more chances
they will have to make mistakes...
Seems to me there is a conflict in NetConf now between formality (XML, no-defaults, ...)
and direct use (SSH, cut&paste of commands, ...) and I still don't know which
side the uptake will be on... As the old saying goes, he who chases two
rabbits at once often loses both...
Thanks
-----Original Message-----
From: Wes Hardaker [mailto:wjhns1@hardakers.net]
Sent: Wednesday, March 03, 2004 3:10 PM
To: Bobby Krupczak
Cc: Wes Hardaker; Andy Bierman; netconf@ops.ietf.org
Subject: Re: comments on version 2 of protocol draft
>>>>> On Wed, 3 Mar 2004 14:10:50 -0500, Bobby Krupczak
>>>>> <rdk@krupczak.org> said:
Bobby> I do not see the point in further arguing over the topic.
Now, that I agree with. We're not going to come to agreement as our needs differ.
Bobby> Do you think to-default or not to-default would make the spec
Bobby> more widely or less widely deployed? I dont think this issue
Bobby> will effect adoption.
I think this, along with other directions that have been taken, will prevent netconf from being deployed in some environments, yes. But I don't work in the same environments you do. We've proven that well enough.
--
"In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find." -- Terry Pratchett
--
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/>