I think that the XMLConf is describing a mechanism that
uses IP as the transport. Therefore, if a device is to be
supported via the protocol, it must be reachable via IP.
I think this is the only requirement of the device. XMLConf
(at least in the first stage) does not specify anything
about the data model, and thus makes no distinction between
device types.
Bryan
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Monday, March 24, 2003 9:53 AM
To: RJ Atkinson; Andy Bierman
Cc: xmlconf@ops.ietf.org
Subject: RE: Goals for netconf - moving towards the charter description
Ran,
I am confused about the distinction that you are making between 'IP-centric' devices and the rest. To what category belongs a router with different types of interfaces (Ethernet, ATM, Frame Relay, etc.)? Today for example an Ethernet bridge or router is managed via SNMP over IP, not SNMP over Ethernet. I am concerned because it is not clear yet whether we will use one single data model for configuration management, faults management, performance management, etc. (I think we should). What you seem to be saying is that we might even use different protocols for different types of interfaces on the same device. Am I mis-understanding?
Thanks,
Dan
> -----Original Message-----
> From: RJ Atkinson [mailto:rja@extremenetworks.com]
> Sent: Monday, March 24, 2003 3:45 PM
> To: Andy Bierman
> Cc: xmlconf@ops.ietf.org
> Subject: Re: Goals for netconf - moving towards the charter
> description
>
>
>
> On Sunday, Mar 23, 2003, at 21:50 America/Montreal, Andy
> Bierman wrote:
> > Why do you think the NETCONF WG should be concerned with the
> > configuration data for specific technologies? Why would the
> > protocol need to be different to manipulate fault configuration data
> > vs. port configuration data, or any other kind of configuration data
> > for that matter? From the protocol POV, configuration data is just
> > text payload.
>
> IMHO, the key thing is that the proposal(s) here are for moving
> XML-based device configuration data over an IP network, not directly
> moving that data over ATM or ISDN or FDDI.
>
> So the target scope is necessarily limited to IP-centric devices,
> rather than all conceivable telecommunications equipment.
>
> This is slightly different scope than SNMP, which can
> either run over IP or run over different non-IP technologies.
>
> Ran
>
>
> --
> to unsubscribe send a message to xmlconf-request@ops.ietf.org with the
> word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/xmlconf/>
>
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>