On Wed, Feb 27, 2019 at 8:48 AM Juergen Schoenwaelder < [email protected]> wrote:
> On Wed, Feb 27, 2019 at 04:09:17PM +0000, Kent Watsen wrote: > > > > > > > On Feb 27, 2019, at 6:16 AM, Balázs Lengyel < > [email protected]> wrote: > > > > > > 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? > > > > This issue is captured here: > https://github.com/netmod-wg/yang-next/issues/27, which was updated as of > this morning with this very example. > > > > Of course, the problem is in RFC 7950: > > > > o "obsolete" means that the definition is obsolete and SHOULD NOT be > > implemented and/or can be removed from implementations. > > > > I recommend replacing "SHOULD NOT be implemented" with "is not > implemented". > > When an IETF WG decides to obsolete something, I am forced to break > old clients because of this decision? Note sure this makes business > sense (says an academic). > > There is a huge difference between modules where the implementors have > change control over the modules and modules where change control is > far outside the implementors hands and where clients and servers are > implemented by different organizations in an open and largely > uncoordinated way. We always have to keep this in mind when we create > rules. > > There is a huge difference between conformance and server capabilities. The status-stmt is about conformance -- the expected usage for any implementation of the particular statement. Whether a server actually implements something that is deprecated or obsolete is a completely different issue. (It is also another issue that YANG got the deprecated status completely wrong) Andy > The SHOULD NOT allows a server implementor to take a well-informed > decision that there are old clients you care about and that this makes > a business case for supporting obsolete definitions on a server. > > Another aspect here is that we do not make a clear distinction between > server and client. It can very well be that "deprecated" and > "obsolete" mean slightly different things to servers and > clients. (Servers tend to have a natural desire to not break clients > unnecessarily.) > > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <https://www.jacobs-university.de/> > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
