Re: problems with 'ignore-error' <error-option>

[Steve Berl <sberl@cisco.com>]

Perhaps we can leave the specification of what errors are "ignorable" to be
part of the data model description. It seems to be coupled to the way the
contents of the <config> element are processed.

-steve

On 2/2/06 10:40 AM, "Phil Shafer" <phil@juniper.net> wrote:

> Steve Berl writes:
>> So, to better define the behavior in the netconf spec we need to be clear
>> about the errors that we are choosing to ignore. I think that these are the
>> errors that occur in the processing (not the parsing) of the <config>
>> element in an <edit-config>.
> 
> Clarity may be difficult, given the Twilight Zone of failure cases.
> If the client gives you a <grue> element but a <grue> is only valid
> (or worse, only parsable) if the GRUE FRU is plugged into your box,
> the difference between processing errors and parsing errors becomes
> pretty vague.  Recovery may just be best effort.
> 
> Thanks,
>  Phil

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