This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[ripe-list] Confidentiality, or that lack thereof
- Previous message (by thread): [ripe-list] Confidentiality, or that lack thereof
- Next message (by thread): [ripe-list] Confidentiality, or that lack thereof
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Wed Aug 25 17:17:33 CEST 2021
In message <CAPfiqja8gfitNzuaVCtxFyowvngiSq7Ft8pq8fEWf91+Tq2_YA at mail.gmail.com> Leo Vegoda <leo at vegoda.org> wrote: >On Tue, Aug 24, 2021 at 5:18 PM Ronald F. Guilmette ><rfg at tristatelogic.com> wrote: >> As you will see from my immediately prior post however I am of the opinion >> that there is a clear and bright line between THAT sort of "sensitive" >> information (which might be used, misused, or abused if it were to fall >> into the hands of some business competitor) and the mere national corporate >> registration document which all prospective new members that are not natural >> persons must provide to NCC prior to even being accepted as new members. >> >> There is no question in my mind that the former category of information MUST >> be held in confidence by RIPE NCC. The latter category, maybe not so much. > >Are you making a proposal for the RIPE NCC to change the way it >operates, or something else? I only wish that I could even answer that question. Sasdly, I cannot, for the simple reason that the various RIPE legal, policy, and procedure documents which I have seen so far, and which other people have been kind enough to point me to, have not served to clarify what the current policy with respect to corporate registration documents, or if there even exists a current policy with respect to those documents. (My sense is that there currently exists -no- policy relating to those documents.) It would be technically inaccurate, I think, and a misuse of the English language to say that I desire to see a change to something which does not now even exist. Regards, rfg
- Previous message (by thread): [ripe-list] Confidentiality, or that lack thereof
- Next message (by thread): [ripe-list] Confidentiality, or that lack thereof
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]