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/db-wg@ripe.net/
[db-wg] phone number required for person objects
- Previous message (by thread): [db-wg] phone number required for person objects
- Next message (by thread): [db-wg] phone number required for person objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Wed May 25 21:00:49 CEST 2022
Personally, I think that we should write e-mail into the policy as I do think requiring a policy change to change this is reasonable given how I don't see this changing in the foreseeable future. Sure it might be different in 10 years, but maybe we can be ok with needing to use the PDP if/when that occurs. -Cynthia On Wed, May 25, 2022 at 8:58 PM denis walker <ripedenis at gmail.com> wrote: > > Hi Leo > > On Wed, 25 May 2022 at 20:28, Leo Vegoda via db-wg <db-wg at ripe.net> wrote: > > > > Hi, > > > > On Wed, May 25, 2022 at 10:04 AM Cynthia Revström <me at cynthia.re> wrote: > > > > > > I forgot to mention this > > > > > > > [...], why should we dictate what the mandatory technology is? > > > > > > I kinda agree with you here if you by "we" mean the db-wg, this might be a larger question that should involve multiple other working groups too. But the RIPE community should decide this imo. > > > > I think that the reason phone was mandatory is that it was the > > de-facto standard. I agree that e-mail is now. But will it remain so? > > If we are building for the future then we should consider the > > possibility that the future will look different from today. > > The policy proposal relates to today and going forwards. We can't > guess what tech will be the most widely used tomorrow. So either we > write email into the policy today and change the policy if and when > that changes, or we write into the policy something like "One > mandatory means of contact must be defined in the ROLE object. This > one method will be determined by RIPE community consensus and may be > changed in the future if the community consensus prefers an > alternative method." The wording is a bit clumsy but more generalised > and allows changes to the contact method without a policy update. > > cheers > denis > proposal author > > > > > Regards, > > > > Leo > > > > -- > > > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- Previous message (by thread): [db-wg] phone number required for person objects
- Next message (by thread): [db-wg] phone number required for person objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]