Hi > On 24 May 2018, at 07:37, Patrick Mevzek <p...@dotandco.com> wrote: > > In short my main problem, and why I can not support this, is that I do not > see the use case, besides for one registry that needs it to handle resellers, > I doubt having seen another registry saying it will use it, so we are just > paving the way to enable storing more data, where the world goes instead > towards storing less or more carefully (see the current dramas around GDPR)
I think this discussion will never end. There are 2 opinions (or maybe more) and everyone sticks to their own. Anyway, as a community, we managed to think of a specification which covers the needs of both camps. If you don't need roles, only allow the reseller role. I think that's the beauty of the solution. Regarding storing more data. Maybe, yes, there are rumours that registries will become more and more thin, but this can take a long time (or never happen) and meanwhile, there are specific business needs to fulfil. I just know about one GDPR drama, and I don't know whether it is a drama because of GDPR or the approach. But besides that, yes, we need to take into account policies and regulations. Therefor we need to think very careful when writing specs, but it should not hold us back of writing them. I think in this particular case, we did a pretty good job. > > Not everythint that can be done should be done. This is the main point I will > try to address in a separate email since it is a generic issue, not > specifically related to this proposal. I agree with you, do not write specs just to have your name on an RFC. But again, as discussed in another conversation, it is very difficult, if not impossible to judge on the real needs of the community if there is very low participation (which is the main issue). Hence the importance of discussion groups like techops and others which are a valuable input for this group Pieter > > -- > Patrick Mevzek > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
