[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Issue 13.3.1 -- I say "go for it"
Sorry for this (being "just an observer" on the list) but ...
From the telecomm perspective, lack of an explicit create will make the
integration of netconf based systems with 3GPP systems difficult; as the
3GPP network configuration model uses an explicit create. Just for
completeness, there is a create, a modify, and a delete. The service
providers are used to the explicit creates and the states and notifications
that arise from its existence.
I'll go back to hiding in the shadows now ...
br,
dave raymer
-----Original Message-----
From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org]On
Behalf Of Andrea Westerinen
Sent: Sunday, February 08, 2004 11:31 PM
To: 'Phil Shafer'; 'Eliot Lear'
Cc: 'netconf'
Subject: RE: Issue 13.3.1 -- I say "go for it"
The problem is not in legitimate CREATEs, but catching illegitimate
ones, errors and attacks. Also, there may be a separation of privileges
for create vs modify.
Andrea
-----Original Message-----
From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On
Behalf Of Phil Shafer
Sent: Friday, February 06, 2004 9:05 PM
To: Eliot Lear
Cc: netconf
Subject: Re: Issue 13.3.1 -- I say "go for it"
Eliot Lear writes:
>The notion of a "create" operation is not new, dating back to at least
>O_CREAT/creat(2), and possibly the days of Benjamin Franklin. SNMP has
>it for good reason, and we should have it as well. Do people really
>need to be sold on it?
I'd be against requiring an explicit create. Implicit
creation is fine for >90% of the cases and the other
<10% can do a query to see if the target exists.
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/>
--
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/>