From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: [PATCH] override-a3: Remove AS48550 as anycast network
Date: Mon, 05 Sep 2022 10:54:46 +0100 [thread overview]
Message-ID: <CA40AEB3-BCAC-46FC-B18F-EB751AD9914E@ipfire.org> (raw)
In-Reply-To: =?utf-8?q?=3C01070183087aa821-0496c099-0d47-43fb-9434-42180b5ba?= =?utf-8?q?f17-000000=40eu-central-1=2Eamazonses=2Ecom=3E?=
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
Hello Pascal,
Thanks for your submission. I have also seen, that you changed the description of the network in the RIPE database. It used to be "Pascal Mathis trading as SnapServ Mathis” and is now “SnapServ Ltd”:
https://git.ipfire.org/?p=location/location-database.git;a=commitdiff;h=747bfd9545ad5421338c5fe476c93bf4303fc81c
> On 4 Sep 2022, at 13:29, ml+ipfire-location(a)ppmathis.com wrote:
>
> From: Pascal Mathis <dev(a)ppmathis.com>
>
> Signed-off-by: Pascal Mathis <dev(a)ppmathis.com>
> ---
> While AS48550 has once been used for providing an anycast network, it is being
> used as a regular AS since several years. I am responsible for operating this
> network and hereby submit this patch to remove this obsolete override.
> Additionally, the current name of AS48550 is incorrect and should instead
> reflect "SnapServ Ltd", but I suppose this change will be reflected
> automatically once the override is gone and the automatic update triggers?
Yes, this will trigger automatically. However, due to the change in the RIPE database, the name has already been changed, but the anycast flag is still set.
I will leave this patch for Peter to merge - unless he disapproves.
Thank you for helping us to make our database better!
-Michael
> Thanks a lot in advance!
>
> overrides/override-a3.txt | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/overrides/override-a3.txt b/overrides/override-a3.txt
> index b36fbfe..9e7c4d8 100644
> --- a/overrides/override-a3.txt
> +++ b/overrides/override-a3.txt
> @@ -197,11 +197,6 @@ remarks: Generic anycast network [high confidence, but not proofed]
> is-anycast: yes
> country: EU
>
> -aut-num: AS48550
> -descr: Pascal Mathis trading as SnapServ Mathis
> -remarks: Generic anycast network
> -is-anycast: yes
> -
> aut-num: AS50069
> descr: Misaka Network, Inc.
> remarks: Generic anycast network
> --
> 2.37.3
>
next reply other threads:[~2022-09-05 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 9:54 Michael Tremer [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-04 12:29 ml+ipfire-location
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA40AEB3-BCAC-46FC-B18F-EB751AD9914E@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox