feature oldFeature {
status obsolete;
}
leaf myTimer {
if-feature oldFeature ;
mandatory true;
config true;
status current;
type string;
}
So should I configure myTimer or not? I assume yes, correct?
regards Balazs
On 2019. 02. 27. 11:33, Juergen
Schoenwaelder wrote:
On Wed, Feb 27, 2019 at 10:19:55AM +0000, Balázs Lengyel wrote:
Hello,
The feature statement may have a status substatement. But what does it
mean if a feature is deprecated or obsolete? Some ideas:
* All if-feature statements using it should be removed. But what to do
with "if-feature oldFeature AND otherFeature" ;
* The feature is always considered true/false
* this is a bug in rfc7950, there should not be such a substatement
* something else
Deprecated means the feature is deprecated, you should not use it in
new definitions. A feature is not "true or false", a feature can be
implemented or not. A current definition being conditional on a
deprecated feature may be something tools should warn about.
Obsolete means the feature is obsolete, it likely should only be used
in obsolete definitions. A current definition likely should not depend
on an obsolete feature and if that happens, then likely brainware
needs to look at the situation and resolve it.
/js
--
Balazs Lengyel Ericsson Hungary Ltd.
Senior Specialist
Mobile: +36-70-330-7909 email: balazs.leng...@ericsson.com
|
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
