Re: notification charter proposal

[Balazs Lengyel <balazs.lengyel@ericsson.com>]

Let us keep netconf truly transport independent as the choice of transport protocol can 
also be dictated by other reasons:
- market acceptance
- available toolkits
Balazs

Juergen Schoenwaelder wrote:
> On Wed, Nov 23, 2005 at 08:13:21PM +0100, Eliot Lear wrote:
>
> > Glenn,
> >
> > What I'm saying is that while it is true that SSH is the "mandatory to
> > implement", you only need to have application-level ACKs in the
> > notification component if THEY are mandatory to implement.  Otherwise
> > you can leave it to the BEEP mapping and be done with it.
>
>
> Again,
>
> lets first decide which semantics we need and then talk about the
> implementation. I personally have bad feelings if sematics associated
> with a netconf protocol operation are determined by the underlying
> transport.
>
> /js

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