I would recommend simply outsourcing it to voip.ms for $2 a month. Port
your fax DID to them.
Incoming fax arrive as PDF in your choice of email inbox.
You can send outbound fax from a predefined list of your own email
addresses, destination to f...@voip.ms. Put the destination phone number in
th
On 06/01/2018 09:37 AM, McBride, Mack wrote:
> For routing whois information there aren't going to be many individuals and
> it would seem
> that the corporations who employee individuals should be the ones protecting
> those individuals
> work emails by providing a generic contact email forward.
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG and the RIPE Routing WG.
Daily listings are sent to bgp-s
The whois guard solution seems workable where the registrar just forwards
information.
It would be nice if there were corporate phone numbers as GDPR doesn't apply to
corporations.
For routing whois information there aren't going to be many individuals and it
would seem
that the corporations who
On Fri, Jun 1, 2018 at 8:47 AM, Stephen Satchell wrote:
> In other words, how do you do your job in light of the GDPR restrictions
> on accessing contact information for other network operators?
>
> Please be specific. A lot of NOC policies and procedures will need to
> be updated.
Publish role
On 1/Jun/18 13:03, Jared Mauch wrote:
> I heard back and they corrected the problem.
>
> Reminder to keep your peering contacts handy :-)
And that max-prefix song :-)...
Mark.
* l...@satchell.net (Stephen Satchell) [Fri 01 Jun 2018, 14:51 CEST]:
How does your shop, Niels, go about making contact with an operator
that is hijacking one of your netblocks, or is doing something weird
with routing that is causing your customers problems, or has broken
BGP?
The same as w
On 06/01/2018 08:47 AM, Stephen Satchell wrote:
On 06/01/2018 05:24 AM, niels=na...@bakker.net wrote:
* h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
The entire whois debacle will only get resolved when some hackers attack
www.eugdpr.org, ec.europa.eu and some other key
On 06/01/2018 05:24 AM, niels=na...@bakker.net wrote:
> * h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
>> The entire whois debacle will only get resolved when some hackers attack
>> www.eugdpr.org, ec.europa.eu and some other key .eu sites. When the
>> response they get wi
On 01/06/2018 15:24, niels=na...@bakker.net wrote:
> * h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
>> The entire whois debacle will only get resolved when some hackers attack
>> www.eugdpr.org, ec.europa.eu and some other key .eu sites. When the
>> response they get will
* h...@efes.iucc.ac.il (Hank Nussbacher) [Fri 01 Jun 2018, 06:56 CEST]:
The entire whois debacle will only get resolved when some hackers attack
www.eugdpr.org, ec.europa.eu and some other key .eu sites. When the
response they get will be "sorry, we can't determine who is attacking
you since tha
I heard back and they corrected the problem.
Reminder to keep your peering contacts handy :-)
- Jared
> On May 31, 2018, at 8:43 PM, Jared Mauch wrote:
>
> We noticed this as well and sent peering@ a note.
>
> - Jared
>
>> On May 31, 2018, at 8:37 PM, Nikolas Geyer wrote:
>>
>> Anybody fro
12 matches
Mail list logo
