On 2017-12-01 23:41, Randy Presuhn wrote:
Hi -
On 12/1/2017 3:37 AM, Balazs Lengyel wrote:
Hello,
https://tools.ietf.org/html/rfc7950#section-7.21.2
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.
Randy
BALAZS : Disagree. From a client point of view it may look like the
same, but from an operator (company) point of view it is different. If I
am an operator like Vodafone or ATnT, if the restriction is based on
access control, I can change my procedures to permit the usage. However
if something is removed based on deprecated, I have no solution.
--
Balazs Lengyel Ericsson Hungary Ltd.
Senior Specialist
Mobile: +36-70-330-7909 email: [email protected]
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
