On Fri, Apr 06, 2018 at 10:51:48AM +0200, Ladislav Lhotka wrote: > Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> writes: > > > If we would have a mechanism to deviate an identityref to a subset of > > identity values supported by an implementation, we would have solved a > > more generic problem. Yes, the IANA list could be 'nicer' but it will > > never be 'nice'. > > Three mechanisms can be used for this: > > - splitting the identities into separate modules
Whatever module organization you come up with, it won't work for all implementations. > - using features Making every identity a feature will turn the feature system upside down. This is similar to making every leaf a feature. > - using deviations (even though vendors frown on them) If my implementation only supports A and B and C, then a deviation may state exactly that and the problem is solved. Hoping that my specific combination of A and B and C matches a set of modules or some set of features is in my view an illusion. Vendors not shipping proper deviations are essentially telling their customers that they have not yet understood model driven management. We need to change the mindset here instead of polluting our data models with hundreds or thousands of fine grained 'features'. /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 netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
