[Nsi-wg] ietf NETCONF group

[Bartek Belter]

Hi Guy, all,

The GN2 AMPS (Advance Multi-domain Provisioning System, a federated resource reservation system for Premium IP) also uses this API to configure Juniper routers. And indeed, as Joan Antoni pointed out, this API is used to configure a single network device, not the whole network.

If you have valid GN2 credentials you may take a look at the page: http://wiki.geant2.net/bin/view/SA3/AmpsConfigurationService
This gives a brief overview to the part of AMPS responsible for the configuration of network elements. I can try to dig a bit more, if some of you are interested to get more detailed description.


Best regards,
Bartek

-- 
Bartosz Belter
Poznan Supercomputing and Networking Center
Network Department

tel. +48 61 858 2028
http://www.man.poznan.pl



> -----Original Message-----
> From: nsi-wg-bounces at ogf.org [mailto:nsi-wg-bounces at ogf.org] On Behalf
> Of Joan Antoni Garcia Espin
> Sent: Friday, June 26, 2009 9:39 AM
> To: Guy Roberts
> Cc: NSI WG
> Subject: Re: [Nsi-wg] ietf NETCONF group
> 
> Hello Guy, all,
> 
> i2CAT has practical expertise on Netconf derived from the Manticore
> project (which Lars mentioned).
> 
> Indeed, as Eduard and myself commented on call conf the 17th of June,
> Netconf was born as a new interface API for network *device*
> configuration, not for whole networks. However, it is true that
> Netconf's XML messaging eases network configuration, since the same
> configuration pattern can be replicated on any box implementing Netconf
> iface.
> 
> As a side note, it has to be noted that each manufacturer has its own
> implementation of the messages. Juniper networks have pioneered Netconf
> implementation in their devices and they've got pretty good
> documentation [1].
> 
> I hereby copy an excerpt of RFC 4741 showing the abstract (full text in
> [2]):
> >>
>    The Network Configuration Protocol (NETCONF) defined in this
> document
>    provides mechanisms to install, manipulate, and delete the
>    configuration of network devices.  It uses an Extensible Markup
>    Language (XML)-based data encoding for the configuration data as
> well
>    as the protocol messages.  The NETCONF protocol operations are
>    realized on top of a simple Remote Procedure Call (RPC) layer.
> <<
> 
> My best regards,
> 
> [1] http://www-
> jnet.juniper.net/techpubs/software/junos/junos95/netconf-guide/netconf-
> guide-TOC.html
> [2] http://tools.ietf.org/html/rfc4741
> --
> Joan Antoni Garcia Espin
> CTX, Fundació i2CAT
> 
> 
> 
> El dc 24 de 06 de 2009 a les 11:06 +0100, en/na Guy Roberts va
> escriure:
> > Hi all,
> >
> >
> >
> > Is anyone planning to go to ietf in July?   I am interested in the
> > NETCONF working group as this has some similarities with NSI  (both
> > are web service based interfaces for configuring networks).   From
> > reading the RFCs it seems to me that NETCONF describes a method for
> > configuring individual routers/switches rather than generic network
> > based service requests.  It would be interesting to see if there is
> > any opportunity to learn from their experience or even align our
> work.
> >
> >
> >
> > If anyone is planning to attend ietf please let me know.
> >
> >
> >
> > Thanks,
> >
> > Guy
> >
> >
> >
> > ---------------------------------------------------------------------
> ---------------------------------------------
> >
> > Guy  Roberts,  Ph.D
> >
> >
> >
> > Network Engineering & Planning
> >
> > DANTE - www.dante.net
> >
> > Tel: +44 (0)1223 371 316
> >
> > City House, 126-130 Hills Road
> >
> > Cambridge, CB2 1PQ, UK
> >
> > ---------------------------------------------------------------------
> ---------------------------------------------
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > nsi-wg mailing list
> > nsi-wg at ogf.org
> > http://www.ogf.org/mailman/listinfo/nsi-wg
> 
> 
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/nsi-wg