[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2.5) <matching> parameter

To: Andy Bierman <abierman@cisco.com>
Subject: Re: Issue 2.5) <matching> parameter
From: Rob Enns <rpe@juniper.net>
Date: Fri, 12 Dec 2003 11:50:40 -0800
Cc: netconf@ops.ietf.org
In-reply-to: <4.3.2.7.2.20031202155332.00b46348@fedex.cisco.com>
Mail-followup-to: Andy Bierman <abierman@cisco.com>, netconf@ops.ietf.org
References: <4.3.2.7.2.20031202155332.00b46348@fedex.cisco.com>
User-agent: Mutt/1.4i

Concur. Axe it.

On Tue, Dec 02, 2003 at 03:54:07PM -0800, Andy Bierman wrote:
> Remove <matching> parameter because it is not documented and 
> therefore not interoperable.
> 
>   - Possibly create data model for this in the future
> 
> 
> --
> 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/>

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

References:
- Issue 2.5) <matching> parameter
  - From: Andy Bierman <abierman@cisco.com>

Prev by Date: Re: Issue 2.4) <notification> wrapper
Next by Date: Re: Issue 2.1) Should the NETCONF protocol support notifications?
Previous by thread: Issue 2.5) <matching> parameter
Next by thread: Issue 2.6) Reliable syslog
Index(es):
- Date
- Thread