[no subject]

[owner-netconf@ops.ietf.org]

FROM=5FRFC=5FABUSE,
=09DNS=5FFROM=5FRFC=5FPOST,MSGID=5FFROM=5FMTA=5FHEADER,SPF=5FPASS autol=
earn=3Dno=20
=09version=3D3.1.1
Received: from [65.54.246.76] (helo=3Dbay0-omc1-s4.bay0.hotmail.com)
=09by psg.com with esmtp (Exim 4.60 (FreeBSD))
=09(envelope-from <henrypootel@hotmail.com>)
=09id 1GDCtw-000HEi-SE
=09for netconf@ops.ietf.org; Wed, 16 Aug 2006 04:21:08 +0000
Received: from hotmail.com ([64.4.51.41]) by bay0-omc1-s4.bay0.hotmail.=
com with Microsoft SMTPSVC(6.0.3790.1830);
=09 Tue, 15 Aug 2006 21:21:08 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSV=
C;
=09 Tue, 15 Aug 2006 21:21:08 -0700
Message-ID: <BAY107-F31551DE76D5CC2ED22CA9CAA4C0@phx.gbl>
Received: from 64.4.51.220 by by107fd.bay107.hotmail.msn.com with HTTP;=
Sender: owner-netconf@ops.ietf.org
Precedence: bulk

=09Wed, 16 Aug 2006 04:21:05 GMT
X-Originating-IP: [216.93.211.196]
X-Originating-Email: [henrypootel@hotmail.com]
X-Sender: henrypootel@hotmail.com
From: "Henry Pootel" <henrypootel@hotmail.com>
To: netconf@ops.ietf.org
Bcc:=20
Subject: configuration use case question
Date: Tue, 15 Aug 2006 21:21:05 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=3Dflowed
X-OriginalArrivalTime: 16 Aug 2006 04:21:08.0278 (UTC) FILETIME=3D[65B3=
FD60:01C6C0EB]

I have been reading the NETCONF standard and think you people have done=
 a=20
great job!  As I was reading, I thought of a question for which I haven=
't=20
found an answer.  (I did find some posts that mentioned 'operational'=20=

commands when talking about what the WG should work on next---notificat=
ions,=20
or whatever---I hope my question doesn't just re-kindle an unrelated=20=

discussion topic and my question is left un-answered!)  Please help me=20=

understand how this use case should work:

There are commands in network devices, like "sdm prefer routing" on a C=
isco=20
3750, that require a reload.  However, I didn't see any built-in operat=
ion=20
for rebooting a device.  How should this interaction with a device, whe=
n the=20
configuration option requires a reboot, work using NETCONF=3F

I thought of a few options:

0. NETCONF does only configuration--operational commands like "reload" =
are=20
outside the scope.

1. Ooops, we forgot about reload (not likely!) or just haven't got to i=
t=20
yet.

2. It's left to the data model--devices can expose a configuration elem=
ent=20
that results in a reload.  Something like:

<rpc message-id=3D"101" xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.=
0">
   <edit-config>
      <target>
         <running/>
      </target>
      <config>
         <cli xmlns=3D=94http://example.com/schema/1.0/config/=94>
            reload
         </cli>
      </config>
   </edit-config>
</rpc>

The device would respond with a reply of <ok/>, close the NETCONF=20
connection, and then reload.  (After typing this in, it seems really ho=
key.)

3. A device manufacturer can add a capability that adds a new operation=
. =20
Something like this:

<hello xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>
      urn:ietf:params:netconf:base:1.0
    </capability>
    <capability>
      http:/example.com/schema/1.0/reload
    </capability>
  </capabilities>
  <session-id>4</session-id>
</hello>

And then you could send the device a NETCONF rpc with this new "reload"=
=20
operation when required.  The rpc would look like this:

<rpc message-id=3D"102" xmlns=3D"urn:ietf:params:xml:ns:netconf:base:1.=
0">
   <reload/>
</rpc>

The device would respond with a reply of <ok/>, close the NETCONF=20
connection, and then reload.  (If NETCONF doesn't include a native "rel=
oad"=20
operation, then this makes the most sense---to me anyway!)

4. <your idea here...>

How should it work=3F

Thanks!

Henry





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