IETF Logo Mail Archive

[Netconf] Clarification about additional attributes at Messages(RPC) layer

Shiva Kumar Pathori <pathori@gmail.com> Mon, 29 January 2018 20:17 UTC

Return-Path: <pathori@gmail.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F3612EB2A for <netconf@ietfa.amsl.com>; Mon, 29 Jan 2018 12:17:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1L9HthHZxMx9 for <netconf@ietfa.amsl.com>; Mon, 29 Jan 2018 12:17:04 -0800 (PST)
Received: from mail-ot0-x241.google.com (mail-ot0-x241.google.com [IPv6:2607:f8b0:4003:c0f::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D44512FB3B for <netconf@ietf.org>; Mon, 29 Jan 2018 12:17:04 -0800 (PST)
Received: by mail-ot0-x241.google.com with SMTP id t35so7758956otd.13 for <netconf@ietf.org>; Mon, 29 Jan 2018 12:17:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xRo4mTR7mmLP0or0XOoaA0G8WDRFF8Oo/lZ1Oe/kvo0=; b=lC1ktIr6ZKvuN90JjuDABIJVpZFID1nqiYu6yVYxAHLWpDIXFVuWAZD0UPSBw5tf+Z vthAqKqHUSe6DUiLDkJqdkBPCJ8Y/xWkzmSi9YJvyYSEAQZ2Dtho8hxSKNpjK4kWDsS4 PjURgKcwMTl6l9nejfj5HWJyfY23Nfw7a2ReUwcptWA1uc79x6sQ1C5h5x4LujfFU9zp L0gEfG8ySezPFiArQQQywHAC8eb1zOWd+sv9erO9wsnhwK3sv+uXO38EXiL6r2PH3aA5 2kISFZezyof1RPUFfCUaW72p2z/WRc/B+11d3ElSEzX7IXT3YYZDVpzBp+GnYDSf+cTf XUsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xRo4mTR7mmLP0or0XOoaA0G8WDRFF8Oo/lZ1Oe/kvo0=; b=KXOIGDkMLpA3x6Ols/F8o+kqKoijwPquigOshudUjov5bMkA5TniEYP13IK2MuvAd3 SMOJorcgiMsK9Jc9zb3a+6GCgJShcz5SHbDTirmPrPvahkGSVtyI0wF71c1o3wlbVvb2 IhnbtgDQLAu/NP0wBHvGFXq0957Htewr3EG+Q40Q0receRrq7j0I9dxJrEJwdJvaPLaT 9t95IrB5zANWyh5fBBvIqP556YSG199tbwV1TrF0XHr3V1xQVgtlroEtKNua/aubOfG4 sUF8uamNSQrq+gJFN/Bh1zrs7aHL65XIrh97f5Gnz+tl1eDIn778pghIuTgxJ58hqigP ljJQ==
X-Gm-Message-State: AKwxytf5iNE+FxqaqNPRNEHTBDCIE3IzM1D7321KO8BkOKatgfdcIcs/ GPK2/v1QDLS7TNvzuFGNlAi4Crh1eqdMn2bJz5jCVF0Z
X-Google-Smtp-Source: AH8x225ZWaY9Bjek/+xp+AgH9YgFV7gzmL0NZV5xbUccN6kJzW44ABg66GNxHQD7pQ6E3Df4jJ/BW72fDr/xYhf446I=
X-Received: by 10.157.68.102 with SMTP id f35mr1592152otj.227.1517257023071; Mon, 29 Jan 2018 12:17:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.50.229 with HTTP; Mon, 29 Jan 2018 12:17:02 -0800 (PST)
From: Shiva Kumar Pathori <pathori@gmail.com>
Date: Tue, 30 Jan 2018 01:47:02 +0530
Message-ID: <CAJtYN8LRQb_HzbN7CmXPPwDKnRXK=YhWyrku223cQ-NVZxN6+Q@mail.gmail.com>
To: netconf@ietf.org
Content-Type: multipart/alternative; boundary="001a1148c9d0e4a9550563efed17"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/S9_hxnVA6uksNAgdX1eZWf_zeSw>
Subject: [Netconf] Clarification about additional attributes at Messages(RPC) layer
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jan 2018 20:17:06 -0000

Hi,
Can somebody clarify below <rpc-reply> sent by the NETCONF server will
break the NETCONF client functionality. Additional attribute information is
shown in RED color.

<rpc message-id="101"
          xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
       <edit-config>
         <target>
           <running/>
         </target>
         <config>
           <top xmlns="http://example.com/schema/1.2/config">
             <interface>
               <name>Ethernet0/0</name>
               <mtu>1500</mtu>
             </interface>
           </top>
         </config>
       </edit-config>
     </rpc>


<rpc-reply message-id="101"
          xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"

          *xmlns:nc-ext="http://sample.com/netconf/ext
<http://sample.com/netconf/ext>" nc-ext:config-id="1"*>
       <ok/>
     </rpc-reply>


I have just tried with MG SOFT NETCONF browser and worked fine, I think MG
SOFT browser ignored these attributes.

v2.23.0 | Report a Bug | By Email