IETF Logo Mail Archive

Re: [Netconf] [netconf] Editorial change for draft-ietf-netconf-nmda-netconf

Kent Watsen <kwatsen@juniper.net> Thu, 31 May 2018 18:54 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 62B9812E8DB for <netconf@ietfa.amsl.com>; Thu, 31 May 2018 11:54:26 -0700 (PDT)
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 VgKcRixxIWhq for <netconf@ietfa.amsl.com>; Thu, 31 May 2018 11:54:22 -0700 (PDT)
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 A6C1B128896 for <netconf@ietf.org>; Thu, 31 May 2018 11:54:22 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4VIoXxh030621; Thu, 31 May 2018 11:54:17 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : mime-version; s=PPS1017; bh=V3mrzE8rcnnohCk+9S92oULGX9r/zKBLWpVGk4c8Zew=; b=gR7i1FTsuxEXYABmxUDYO9QYoG/gyYEFENKp3ftEp7kjrJtiANo4WtQGM44IFt6fTM1/ ODj+wq1sX8Iqm7jY1+pNXuSXNZHtdOgpRhFUiPnKOYFdozITxSqZG1sSK94eKTpB1VTm GLW5VWpH+1Xh3GmRIibd05NDWQL3IeMJbU+eeeB+gDWefgJNLjrpETtZglLV8WJL5F3s DR4pMSpEMm8exgk327va0jx1I6a6cbCjqW+dQnx8vcFg5J80e9riPyplOPxA3HHijY7M SzrgRrCPsYvSAT4gkUMTCuI1eoiBaW8wse/m4M51u90JsNamWFblbXCG1ANOGVRayXA1 eA==
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp0016.outbound.protection.outlook.com [216.32.181.16]) by mx0b-00273201.pphosted.com with ESMTP id 2jakb20cyj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 31 May 2018 11:54:17 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB4101.namprd05.prod.outlook.com (52.135.199.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.11; Thu, 31 May 2018 18:54:14 +0000
Received: from BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::95f0:e564:96c8:7f1c]) by BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::95f0:e564:96c8:7f1c%2]) with mapi id 15.20.0820.010; Thu, 31 May 2018 18:54:14 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Rohit R Ranade <rohitrranade@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] [netconf] Editorial change for draft-ietf-netconf-nmda-netconf
Thread-Index: AQHT+RDFNF/Mtf3jEE2KduHkXzL3Mg==
Date: Thu, 31 May 2018 18:54:14 +0000
Message-ID: <B67E31B5-9D39-4212-BFAF-9B6C747F4F59@juniper.net>
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; BYAPR05MB4101; 7:pW/ifoVkJyMR+TDIxRBj0/T8v95Qq2e1yoWCv/LaZd+zGesTqUki0ONYoz0qsD6ZsAZ9d1PoWlFhHQ3+GErPudTvF0CPhFiC0SDMGdEr1AcPr1uN7OWgfvVbj6TyS5a2T6vKCuZfwjbyCW4lGIjJZjhUZ/r3VvYT8nH3FMmpRSesKQKL/o1KV4oN7k6cLq9SXx5THdgbtYapXV5Hw7yAiEy3nxGGUMe0bBGyWa3McJlQRg1Q24zO4Ui+7EoazVaj
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4101;
x-ms-traffictypediagnostic: BYAPR05MB4101:
x-microsoft-antispam-prvs: <BYAPR05MB41012E20407903F946A31037A5630@BYAPR05MB4101.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(50582790962513)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB4101; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4101;
x-forefront-prvs: 06891E23FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39380400002)(376002)(39860400002)(366004)(396003)(189003)(199004)(6512007)(81166006)(8676002)(2616005)(186003)(26005)(83716003)(82746002)(81156014)(316002)(106356001)(102836004)(105586002)(53936002)(236005)(54896002)(486006)(2900100001)(2501003)(2906002)(25786009)(68736007)(3280700002)(476003)(33656002)(8936002)(59450400001)(5250100002)(6306002)(6506007)(6246003)(3846002)(6116002)(66066001)(86362001)(99286004)(3660700001)(36756003)(97736004)(5660300001)(6486002)(229853002)(6436002)(58126008)(110136005)(7736002)(14454004)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4101; H:BYAPR05MB4230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 2yBdmVotRvxq+eEDKpwdr1QJytlkD7I2chlY2ekXLqXauc7W6J7lgsl4QIjf13XHD+5FdHJQfwXYt926sebSZ6ykKoxNzUloAW66MPh1tUP3A3f/gjv+xgOVqO1MqlocIn5mVN2vQ46ILNl9NjpIsPWXKaUPYoJV/abrcKy06zf3ZIaKsSEXTvP5eHpTmbyj
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_B67E31B59D394212BFAF9B6C747F4F59junipernet_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 724d6b1e-6924-4871-adcc-08d5c727e7bb
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 724d6b1e-6924-4871-adcc-08d5c727e7bb
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2018 18:54:14.7701 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4101
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_10:, , 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=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805310209
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/eIx-0VsZlmai7Yj0X12uiUs1yvc>
Subject: Re: [Netconf] [netconf] Editorial change for draft-ietf-netconf-nmda-netconf
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: Thu, 31 May 2018 18:54:27 -0000

As a contributor, I agree with this clarification.   As co-chair, I view this as an editorial update that the authors (assuming agreement) can commit/push while waiting for IETF LC to commence.

Kent



On 5/31/18, 4:54 AM, "Netconf on behalf of Rohit R Ranade" <netconf-bounces@ietf.org<mailto:netconf-bounces@ietf.org> on behalf of rohitrranade@huawei.com<mailto:rohitrranade@huawei.com>> wrote:

Change 1:
================
Section 3.1.1

OLD:
The "config-filter" parameter can be used to retrieve only "config
   true" or "config false" nodes.


NEW:
The "config-filter" parameter can be used to retrieve only "config
   true" or "config false" nodes. Note that if “config-filter” is set to “false”,
configuration ancestors (if any) and list key leafs (if any)
are also returned.

Note:
“retrieve only “config false” nodes maybe misleading. So the use-full text written in RFC 8040 in Example 3 can be re-used here.


With Regards,
Rohit R Ranade

v2.23.0 | Report a Bug | By Email