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/[email protected]/
[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 ]
David Conrad
drc at virtualized.org
Wed May 25 21:39:21 CEST 2022
Hi, On May 25, 2022, at 10:01 AM, Cynthia Revström via db-wg <db-wg at ripe.net> wrote: > The reason behind this is that email is the de facto standard for internet communication, especially between organizations. IIRC, the original point of multiple methodologies of contact was due to the desire to avoid single points of failure. That is, it was deemed (back in the day) unlikely that a network operator would be able to bork both their email and their phone (and their fax) at the same time, particular given phone/fax was based on different technology. Of course, since most phone/fax is now IP-based, that logic may not hold. Still, in keeping with the original intent of SPOF avoidance, I’d imagine a mandatory email + one other (technology neutral) would make sense. Regards, -drc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: </ripe/mail/archives/db-wg/attachments/20220525/a2534cbc/attachment.sig>
- 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 ]