IETF Logo Mail Archive

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

Kent Watsen <kwatsen@juniper.net> Tue, 30 January 2018 14:58 UTC

Return-Path: <kwatsen@juniper.net>
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 51EEC12D84A for <netconf@ietfa.amsl.com>; Tue, 30 Jan 2018 06:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=juniper.net
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 D81iJNwQjGCi for <netconf@ietfa.amsl.com>; Tue, 30 Jan 2018 06:58:14 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5625213184A for <netconf@ietf.org>; Tue, 30 Jan 2018 06:54:41 -0800 (PST)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0UEoSgi018166; Tue, 30 Jan 2018 06:54:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=FKkVG2PIqK5Yc63lsRpxQAWaVk6aU8aA0SUD5TY+dnM=; b=U9kKg+tVlkRK/UTTMt1yyKpH/WjAbF2r9jWx19EtA8a6B80EKjl9ShczrFwHSA3gKkZD mMLrBPQ192mg3AbLHnWzQbxnWO97PLwHe8oUrGthIq0aXY/+CF91CEzmuJl1hRSAKOmT F1ZJCIZdv2Ha4mZpXeMBXlozJXNAjBRLPg9vpaxAhZdfCFXGuNq44GDxPcWEm/tYMxKH m+ZaeuQcWYxMqZv2HU6uqm02dToqRvnAKd6SB0kMlMq4Q+iGQrSk/3ep4cp8S4XGcCmy LbRRPMk00ru5ctopmvnVqCxN+5CxZSdzbQr6qyXFXf6TsxdE4DtKu3wE/El7bIOf7qA8 4g==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0054.outbound.protection.outlook.com [216.32.180.54]) by mx0b-00273201.pphosted.com with ESMTP id 2ftkvnh821-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 30 Jan 2018 06:54:38 -0800
Received: from DM5PR05MB3484.namprd05.prod.outlook.com (10.174.240.147) by DM5PR05MB3657.namprd05.prod.outlook.com (10.174.190.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.464.6; Tue, 30 Jan 2018 14:54:35 +0000
Received: from DM5PR05MB3484.namprd05.prod.outlook.com ([10.174.240.147]) by DM5PR05MB3484.namprd05.prod.outlook.com ([10.174.240.147]) with mapi id 15.20.0464.008; Tue, 30 Jan 2018 14:54:35 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Shiva Kumar Pathori <pathori@gmail.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] Clarification about additional attributes at Messages(RPC) layer
Thread-Index: AQHTmT4lNT3fBm4m8EqSKaIovJbsFKOMLi6A
Date: Tue, 30 Jan 2018 14:54:35 +0000
Message-ID: <805AA544-8B1D-4F80-999C-AABB3F5D3253@juniper.net>
References: <CAJtYN8LRQb_HzbN7CmXPPwDKnRXK=YhWyrku223cQ-NVZxN6+Q@mail.gmail.com>
In-Reply-To: <CAJtYN8LRQb_HzbN7CmXPPwDKnRXK=YhWyrku223cQ-NVZxN6+Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR05MB3657; 7:yHJxu6CcIzYGf6dn9/jRFfSjd+Yj3vj+nes09v67bx1e3saqd7EmB66PqRpbme33W74xJtK60xJET0MG6fHhvK/ZqivpbSYJd7xdvtCQX3SB8R71KLcPs7ntZ/Y4cHqpim4MnADaIYvtte0cQaCCGXjzbX56Ynm/WXbHGbLIklqAlGqJ30TV/LdWBdQyAePvF0ieCy7rA7pLuNVPL6QNBzTBbJsOUSh3k9mPL3UAe0q7dR9t9+zAoe5ePXcWzyyY
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 68179287-f55f-41c9-eecc-08d567f160f8
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(48565401081)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:DM5PR05MB3657;
x-ms-traffictypediagnostic: DM5PR05MB3657:
x-microsoft-antispam-prvs: <DM5PR05MB365762702ED1A458C30BDB2FA5E40@DM5PR05MB3657.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(10436049006162)(85827821059158)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231101)(944501161)(3002001)(10201501046)(6055026)(6041288)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123562045)(20161123558120)(6072148)(201708071742011); SRVR:DM5PR05MB3657; BCL:0; PCL:0; RULEID:; SRVR:DM5PR05MB3657;
x-forefront-prvs: 0568F32D91
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(39380400002)(366004)(39860400002)(396003)(189003)(199004)(2900100001)(33656002)(316002)(82746002)(53936002)(66066001)(7110500001)(53376002)(97736004)(966005)(14454004)(99286004)(6512007)(83716003)(6486002)(6506007)(19273905006)(54896002)(6246003)(6436002)(86362001)(3280700002)(5660300001)(8936002)(81166006)(6306002)(2906002)(6116002)(7736002)(3846002)(106356001)(105586002)(83506002)(2950100002)(229853002)(58126008)(110136005)(3660700001)(76176011)(606006)(25786009)(2501003)(478600001)(26005)(186003)(68736007)(15650500001)(39060400002)(102836004)(77096007)(8676002)(2420400007)(236005)(81156014)(36756003)(562404015)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3657; H:DM5PR05MB3484.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: pjoCgjxkeXQuEIpeiJYie9g96v7EBDgFwrI1EDTvLhnPdmKQWCysHzAHdbgUnw8SmbhRJY9zXcn5Jp+wgwg4sw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_805AA5448B1D4F80999CAABB3F5D3253junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 68179287-f55f-41c9-eecc-08d567f160f8
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jan 2018 14:54:35.4030 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3657
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-30_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801300187
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/PkRBgXRgTXfBNWj0mqQI8p-4Sh8>
Subject: Re: [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: Tue, 30 Jan 2018 14:58:17 -0000

I believe that this is allowed by [1], but worry about interoperability due to the "config-id" attribute being a proprietary extension.

[1] https://tools.ietf.org/html/rfc6241#section-4.2

Kent  // contributor


Assuming the namespace prefix is there to support

On 1/29/18, 3:17 PM, "Netconf on behalf of Shiva Kumar Pathori" <netconf-bounces@ietf.org<mailto:netconf-bounces@ietf.org> on behalf of pathori@gmail.com<mailto:pathori@gmail.com>> wrote:

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<https://urldefense.proofpoint.com/v2/url?u=http-3A__example.com_schema_1.2_config&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=nAjM7pDWG7HS1viFkN6mWV_1Ii2GVce-FvEqf3h0gfo&s=LQjMxXfz35-ysUajs_4pgqhw9Cmbna4-0672JlBXzNI&e=>">

             <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<https://urldefense.proofpoint.com/v2/url?u=http-3A__sample.com_netconf_ext&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=nAjM7pDWG7HS1viFkN6mWV_1Ii2GVce-FvEqf3h0gfo&s=H__4DCa9XJZJTIQ_Ewl7nAey_4XKXSKLAh-48KhPxMI&e=>" 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