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] IRT object postal address
- Previous message (by thread): [db-wg] IRT object postal address
- Next message (by thread): [db-wg] IRT object postal address (denis walker)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friaças
cfriacas at fccn.pt
Sat Jul 23 20:16:09 CEST 2022
Hi, (please see below) On Wed, 20 Jul 2022, Cynthia Revström via db-wg wrote: (...) > This question is not really an "essential point" in my opinion as > there is a big difference between hiding postal addresses and hiding > abuse email addresses and route(6) objects. > I would argue that a postal address is very rarely needed in the > context of networks while abuse email addresses and route(6) objects > are important to the operation of many networks. "very rarely" doesn't mean it is never needed. After phone calls don't work, e-mails which aren't answered, the last resort is to send a letter with delivery notification to a postal address. And yes, we already had to do that before "pulling a cable", just to be totally in line with our local/national laws. The postal address is the "last line". It can be argued if it could be optional or mandatory, but it should undoubtably be part of the database's structure. Best Regards, Carlos (Security Team/CSIRT hat=on)
- Previous message (by thread): [db-wg] IRT object postal address
- Next message (by thread): [db-wg] IRT object postal address (denis walker)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]