IETF Logo Mail Archive

Re: [Netmod-ver-dt] [netmod-wg/yang-ver-dt] Status obsolete nodes (#2)

"Rob Wilton (rwilton)" <rwilton@cisco.com> Wed, 05 June 2019 08:45 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netmod-ver-dt@ietfa.amsl.com
Delivered-To: netmod-ver-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4569012061F for <netmod-ver-dt@ietfa.amsl.com>; Wed, 5 Jun 2019 01:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Q5EDurom; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=eQ/kzRNa
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 s6Fqms5CSY6I for <netmod-ver-dt@ietfa.amsl.com>; Wed, 5 Jun 2019 01:45:50 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0193A120615 for <netmod-ver-dt@ietf.org>; Wed, 5 Jun 2019 01:45:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11554; q=dns/txt; s=iport; t=1559724349; x=1560933949; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=B3wwxDGuOGy20rXsG5L3G46lX+xbkjqZObFW0lDmMfM=; b=Q5EDuromrbCeuQ9qwOScxlgsAQam6vzvXnBccQ6Yl3HvhVCejTATSPOz /5GQ0mLFvEyWbqhgFtS0ddQtt3JGYWvxOTmDAGnAER0B817tleqZuMs9U gtWiTFdTBjYxtgY/hz3KW79LbLl+9LFEy4b20TJfPFo1rlKp+JOMK6JcD E=;
IronPort-PHdr: 9a23:AQSTyBYcEVcZOaU4DQ1K8bz/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gebRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavwcC0+AMNEfFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BIAAD2f/dc/5BdJa1mHAEBAQQBAQcEAQGBUQcBAQsBgQ4vUANqVSAECygKgkCBSoNHA4RSiiKCV5JehFKBLhSBEANUCQEBAQwBARgBBw0CAQGDekYCF4I9IzQJDgEDAQEEAQECAQRtHAyFSgEBAQQSEQoTAQEMLA8CAQgRBAEBKAMCAgIvARQJCAIEAQ4EAQcVBAGCSjeBHU0DHQECDAMpmlMCgTiIX3GBMYJ5AQEFhQIYgg8DBoEdFwGLWheBQD+BV4JMPoJhAQEBARiBFAESAQkYKwmCVBcbgiaOIIRplgMJAoIOhkGNEZZ7i26BHocOjxoCBAIEBQIOAQEFgU84Z3FwFYMnE4F8g3CKU3IQgRmMP4EiAYEgAQE
X-IronPort-AV: E=Sophos;i="5.60,550,1549929600"; d="scan'208,217";a="569613500"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Jun 2019 08:45:47 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x558jlfG010212 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 5 Jun 2019 08:45:48 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 5 Jun 2019 03:45:47 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 5 Jun 2019 04:45:46 -0400
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 5 Jun 2019 03:45:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=B3wwxDGuOGy20rXsG5L3G46lX+xbkjqZObFW0lDmMfM=; b=eQ/kzRNaPJQwr03q43m+RbPEzrEzmO3q2foZMXikoReRHuKGKJfXPtoN7/4Lx1oP05kCOSWihD44T69O8Vh65DwVOan58qH9jd+ImCDu7JBhrGG5EtLbObWxMJZYt2KYr1cmBLF6r/i60maOVyEeeZAUXKROD2re/C0S0rbajRY=
Received: from BYAPR11MB2631.namprd11.prod.outlook.com (52.135.227.28) by BYAPR11MB3496.namprd11.prod.outlook.com (20.177.226.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.12; Wed, 5 Jun 2019 08:45:44 +0000
Received: from BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::d837:c1dd:cdb1:bb78]) by BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::d837:c1dd:cdb1:bb78%7]) with mapi id 15.20.1943.018; Wed, 5 Jun 2019 08:45:44 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com>, "netmod-ver-dt@ietf.org" <netmod-ver-dt@ietf.org>
Thread-Topic: [netmod-wg/yang-ver-dt] Status obsolete nodes (#2)
Thread-Index: AQHVGsbqOhOp3QJKrkmK2MX4/ZqB7qaLx1hQgAD4YLA=
Date: Wed, 05 Jun 2019 08:45:44 +0000
Message-ID: <BYAPR11MB2631509189C7F34A8E425143B5160@BYAPR11MB2631.namprd11.prod.outlook.com>
References: <netmod-wg/yang-ver-dt/issues/2@github.com> <netmod-wg/yang-ver-dt/issues/2/498628782@github.com> <VI1PR07MB3981384DCEC43089F2E694D89B150@VI1PR07MB3981.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR07MB3981384DCEC43089F2E694D89B150@VI1PR07MB3981.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.56]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 74637946-06c3-4837-80cd-08d6e99232f1
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3496;
x-ms-traffictypediagnostic: BYAPR11MB3496:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <BYAPR11MB349647D0AF5F6206E2D9CE09B5160@BYAPR11MB3496.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 00594E8DBA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(136003)(366004)(346002)(376002)(39860400002)(189003)(199004)(86362001)(74316002)(66066001)(2906002)(99286004)(76116006)(7696005)(296002)(102836004)(478600001)(53546011)(6506007)(76176011)(110136005)(25786009)(7736002)(316002)(26005)(3846002)(11346002)(81166006)(476003)(6116002)(486006)(790700001)(446003)(76236002)(6246003)(33656002)(53936002)(64756008)(66446008)(66476007)(5660300002)(14454004)(52536014)(18926415008)(229853002)(66556008)(73956011)(66946007)(606006)(14444005)(2501003)(236005)(71200400001)(8936002)(71190400001)(55016002)(6436002)(186003)(256004)(8676002)(81156014)(6306002)(733005)(68736007)(9686003)(54896002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3496; H:BYAPR11MB2631.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: mGvXgug7Kb4l7dOXtlbd1jdHmJbdtppt3WyAoWbZqe0XeXEm59hNh/cayuuARJ65AHH8nTz6Vwik7CIitUfiUb1uLMdoaa6xpGAN8G4Ev1+YgthRKuTSEFl0hFOrR35XmC9Wkx4yqEePfuInpt4OAuVAQFP4QZjadxMdU8u5oQGBDtVrxCRtNlsYLiJZIaFCSi3+0YAuad304UDdDHmDWG54t65W3ipaFgGDof5BuK5yC2vlZvzmJD/6fUw81javgUfbn5l8W0dv8ckCo06aiPTJZZ1IP8/Wh2glPSW53xKkfwZRLPXBacyhJ06eAEa1NxO9OK1m+XgBw/V+FBOkka/gFbhNVkBBLPrPtnISBbSh6G0L0NQkdT/0evV6G0XC+04R/QnibIBQ3NkrXWsG3SrSSaCQ/P3l53LD11NFLes=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB2631509189C7F34A8E425143B5160BYAPR11MB2631namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 74637946-06c3-4837-80cd-08d6e99232f1
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2019 08:45:44.6989 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rwilton@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3496
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.27, xch-aln-017.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod-ver-dt/rgjH6CgIBTEHFVNA0g3WvC7EToU>
Subject: Re: [Netmod-ver-dt] [netmod-wg/yang-ver-dt] Status obsolete nodes (#2)
X-BeenThere: netmod-ver-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NetMod WG YANG Model Versioning Design Team <netmod-ver-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod-ver-dt/>
List-Post: <mailto:netmod-ver-dt@ietf.org>
List-Help: <mailto:netmod-ver-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod-ver-dt>, <mailto:netmod-ver-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 08:45:52 -0000

Yes.  At the moment, a server is allowed to implement obsolete nodes that can break a client.

E.g. if an obsolete config node is mandatory, and it is implemented then the client must provide it, and if it is not implemented then the client must not provide it, and there is no way for a client to determine from the server whether it is implemented.

Thanks,
Rob


From: Netmod-ver-dt <netmod-ver-dt-bounces@ietf.org> On Behalf Of Sterne, Jason (Nokia - CA/Ottawa)
Sent: 04 June 2019 18:54
To: netmod-ver-dt@ietf.org
Subject: Re: [Netmod-ver-dt] [netmod-wg/yang-ver-dt] Status obsolete nodes (#2)

I know we wanted a flag for deprecated nodes.  But was there ever confusion about obsolete nodes?

From: Robert Wilton <notifications@github.com<mailto:notifications@github.com>>
Sent: Tuesday, June 4, 2019 7:16 AM
To: netmod-wg/yang-ver-dt <yang-ver-dt@noreply.github.com<mailto:yang-ver-dt@noreply.github.com>>
Cc: Subscribed <subscribed@noreply.github.com<mailto:subscribed@noreply.github.com>>
Subject: Re: [netmod-wg/yang-ver-dt] Status obsolete nodes (#2)


The YANG library changes indicate whether status obsolete nodes are implemented by the server., which I think is as much as we can do in this draft.

Otherwise, this issue can be deferred to YANG.Next. netmod-wg/yang-next#63<https://github.com/netmod-wg/yang-next/issues/63>

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/netmod-wg/yang-ver-dt/issues/2?email_source=notifications&email_token=AETQE732PFQVVSM5ARRJM5TPYZFHTA5CNFSM4G2RIFNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW4HRLQ#issuecomment-498628782>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AETQE7ZX7V35SIKFWU7R3NDPYZFHTANCNFSM4G2RIFNA>.

v2.23.0 | Report a Bug | By Email