Re: [netmod] Use feature to advertise pre-nmda-support {was: WG Last Call: draft-ietf-netmod-rfc7223bis-00 ]

Andy Bierman <> Sat, 02 December 2017 00:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6C48D127078 for <>; Fri, 1 Dec 2017 16:23:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TkBjZsZoE_Nb for <>; Fri, 1 Dec 2017 16:23:36 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9F418124E15 for <>; Fri, 1 Dec 2017 16:23:35 -0800 (PST)
Received: by with SMTP id e137so13519239lfg.5 for <>; Fri, 01 Dec 2017 16:23:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Zv7z5TJBkxvbg5HF2Uew/0XiEMXCuySXerCwEto8ytk=; b=kVIbBq1qwXz/3QCQPiyesM0Klx5r/uygFKmwQZVGnlseZtkZT0Q9Yt/CbPiKzryYiu LFPCrlgzkLetlOQDAMPf3pcRcJKEHqwwYzpG6Nbki53TZ8tSIqV66mt2bd+zspNUzUsr Uy5npbuwq7va5wFg0pLBFLfILXojvxSBW5Kbi+GO1JfUj60dQhMaNGlQcUN6vWJswvMf EsJWELTvI2xB63s7c8ZXZ6iz0ZsGK8yo/NPYUBisrOLWmFNbqFP3BhMXcuPPfktf72Ad diTu/8HvMzykMLAJBDBpQWFf3y9iJv9vfBkmfWp9GvJD2bo7lHzNPZ/Cugfbm2og9ijY rrGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Zv7z5TJBkxvbg5HF2Uew/0XiEMXCuySXerCwEto8ytk=; b=gnbdKkO4ZOrazizc1grPVXHxZhZCKNEfOtNdJ6ShDZBz89RS2u0LRxut4ty3hLexrd +NxKfXTNmmC/SsUiA3/HpPGFB6HglZNJmg2WYYKfZ4SS+tyxj0M0FBM4sjwq+r4HcZXS TsVRrfBFJuiYpObcraaINlB7H3N0vGfiwvmSmhKYwdHH/cZnvis4WY0WboGn+owsq6lJ eVjBODxrn407F8t+O5bsXMTldWCFzGkeBfu6iZ49FzAt44H8VcMumIux3+qavoXk6Erp WT4n6hVLI0Pf7OfNSejkrcoSnvAZ1SkFRZnOP2/kclce0bzU13P5JO4oqO98lWc3Q+3P GxgQ==
X-Gm-Message-State: AJaThX5JWOrJ4ome2Ht4LckRAYJ93v6RBD1f2nes+PjPy+e6ScVFIkdX pVQzmZF664ts8yemroXHmcL6D38ovC+3aQac71Ltsw==
X-Google-Smtp-Source: AGs4zMZXYAlz9Dg5xkRF9A4HPY4POA410/I8vAa0AHf5fS8x/hS9dD3CrAhg7GCLv1Z5ErPzHKgujrM3Q/GNwTSRZEY=
X-Received: by with SMTP id z1mr6146250ljc.81.1512174213902; Fri, 01 Dec 2017 16:23:33 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Fri, 1 Dec 2017 16:23:33 -0800 (PST)
In-Reply-To: <>
References: <> <> <>
From: Andy Bierman <>
Date: Fri, 01 Dec 2017 16:23:33 -0800
Message-ID: <>
To: Randy Presuhn <>
Cc: "" <>
Content-Type: multipart/alternative; boundary="089e0827ae18dbc859055f507e99"
Archived-At: <>
Subject: Re: [netmod] Use feature to advertise pre-nmda-support {was: WG Last Call: draft-ietf-netmod-rfc7223bis-00 ]
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 02 Dec 2017 00:23:38 -0000

On Fri, Dec 1, 2017 at 2:41 PM, Randy Presuhn <> wrote:

> Hi -
> On 12/1/2017 3:37 AM, Balazs Lengyel wrote:
>> Hello,
>>     o  "deprecated" indicates an obsolete definition, but it permits
>>        new/continued implementation in order to foster interoperability
>>        with older/existing implementations.
>> This means that a node that is deprecated MAY or MAY NOT be implemented.
>> YANG is considered an interface contract,  however "maybe implemented" is
>> unusable in a contract.
> From a client perspective, access control can have similar consequences.
> A contract only outlines some of the kinds of things that
> might possibly exist.  It doesn't tell you what's actually there or
> whether you're allowed to do anything with them.
>From a vendor perspective the issue Balazs is raising can affect support
YANG status-stmt does change the contract for the specific object.
The status deprecated is essentially the same as obsolete. There is
no useful warning that an object can be removed from a server in the future.
The warning says "the object can be removed right now".

The deprecated status could have been defined to be the same as current,
the object will likely go away in the future.  Existing implementations MUST
support the object until it is obsolete.  New implementations SHOULD NOT
include the object.

For YANG linkage issues, new revisions SHOULD NOT add new statements that
deprecated objects. Existing linkage would be reliable to use until the
referenced definition is obsolete.


> _______________________________________________
> netmod mailing list