Re: [j-nsp] Netconf namespaces

I've looked at the PyEZ and ncclient code, and basically they seem to take the approach of just throwing away all namespace information. This seems icky to me, and make me wonder if Netconf is going to be another SOAP - so many implementation errors that interop ends up being a mess of

Re: [j-nsp] Netconf namespaces

On 17/06/14 14:49, Keegan Holley wrote: I've looked at the PyEZ and ncclient code, and basically they seem to take the approach of just throwing away all namespace information. This seems icky to me, and make me wonder if Netconf is going to be another SOAP - so many implementation errors that

Re: [j-nsp] Netconf namespaces

On Jun 17, 2014, at 10:01 AM, Phil Mayers p.may...@imperial.ac.uk wrote: On 17/06/14 14:49, Keegan Holley wrote: I've looked at the PyEZ and ncclient code, and basically they seem to take the approach of just throwing away all namespace information. This seems icky to me, and make me

Re: [j-nsp] EX4550 apparently dropping IPv6 RA

If I had a dollar for every time the systems guys changed something and then cried to neteng... :) Thanks, Morgan On Mon, Jun 16, 2014 at 7:11 AM, John Neiberger jneiber...@gmail.com wrote: This all turned out to be a false alarm. Someone on the server team had changed the configuration on

Re: [j-nsp] EX4550 apparently dropping IPv6 RA

I thought that was standard operating procedure for the systems guys to blame the network? :) On Jun 17, 2014, at 1:59 PM, Morgan McLean wrx...@gmail.com wrote: If I had a dollar for every time the systems guys changed something and then cried to neteng... :) Thanks, Morgan On Mon,

Re: [j-nsp] EX4550 apparently dropping IPv6 RA

Which is why going from system admin into network engineering is the way to go, stop them in their tracks! lol. Thanks, Morgan On Tue, Jun 17, 2014 at 12:02 PM, Scott Granados sc...@granados-llc.net wrote: I thought that was standard operating procedure for the systems guys to blame the