RE: do we need filtering or some such

["Chen, Weijing" <wchen@tri.sbc.com>]

In our approach, you can have

<perform-request id="101" transaction="stop-on-error"
                 xmlns="http://ietf.org/xmlconf/1.0/protocol";
                 xmlns:example="http://example.com/schema/1.2";>
  <operation id="1" target="/root">
    <example:root>
      <example:running>
        <example:users operation="get">
          <type>admin</type>
        </example:users>
      </example:running>
     </example:root>
  </operation>
</perform-request>

for all the 20 or so attributes of "users"

And have the following

<perform-request id="101" transaction="stop-on-error"
                 xmlns="http://ietf.org/xmlconf/1.0/protocol";
                 xmlns:example="http://example.com/schema/1.2";>
  <operation id="1" target="/root">
    <example:root>
      <example:running>
        <example:users operation="get">
          <type>admin</type>
****      <username/>
        </example:users>
      </example:running>
     </example:root>
  </operation>
</perform-request>

for only the "username" attribute of the "users".

You may also take the Enns draft approach and use the following:

       <rpc id="101" xmlns="http://ietf.org/xmlconf/1.0/base";>
         <get-config>
           <source>
             <running></running>
           </source>
           <config xmlns="http://example.com/schema/1.2/config";>
             <users>
               <type>admin</type>
****           <username/>
             </users>
           </config>
           <format>xml</format>
         </get-config>
       </rpc>

for the attribue "username".  However, there is problem with this one: what
if there is another XML elements named "users" as in
"/running/acme/level1/users" besides "/running/users"?  What does this
"get-config" means? Which "users" is the "get-config" wants?



--
Weijing Chen


> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Friday, May 23, 2003 10:00 AM
> To: netconf@ops.ietf.org
> Subject: do we need filtering or some such
> 
> Someone asked me a question. Assume the examples around
> page 20 of the enss draft.
> If I did send a
> 
>        <rpc id="101" xmlns="http://ietf.org/xmlconf/1.0/base";>
>          <get-config>
>            <source>
>              <running></running>
>            </source>
>            <config xmlns="http://example.com/schema/1.2/config";>
>              <users>
>                <type>admin</type>
>              </users>
>            </config>
>            <format>xml</format>
>          </get-config>
>        </rpc>
> 
> Then what I really want to see is the user names that are administrators.
> What I will get back (or at least as I understand the examples) is
> a list of users, with all their attributes. So if users had like
> 20 or so attributes, how could I then specify to only get the
> usernames for the administrators and not all the other details?
> 
> Is there any guidance we can give on that?
> 
> Thanks,
> Bert
> 
> --
> 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/>