There are 2 sides to the bgp conversation for any ASN, and then really 4 sides.
customer -> RAS -> peer (settlement-free)
peer(sfp) -> RAS -> customer
customer -> ras -> transit
transit -> ras -> customer
Depending on the RAS's capabilities or status in their journey to
'fully RAS', it's
Hello 'body,
I'm looking for a NOC contact for AS 19338, the old Telmex Chile AS.
Anybody have anything?
Thanks,
Elmar.
On Fri, 11 Nov 2022 at 14:00, Christopher Morrow
wrote:
> Also, also, possibly the output path on the session(s) here is not
> filtering in an OV fashion.
ROV belongs on the input path, let's not ROV on the output towards
customers / route collectors.
Announcing bigger, ROV valid/unkown aggregat
> ROV belongs on the input path, let's not ROV on the output towards
> customers / route collectors.
8893
randy
This is an automated weekly mailing describing the state of the Global
IPv4 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 and the RIPE Routing WG.
Daily listings are sent to bgp-st...
NANOG Community,
The NANOG Program Committee (PC) would like to remind you that we are
accepting proposals for in-person or live remote presentations at all
sessions of NANOG 87, a hybrid meeting, taking place in Atlanta, Georgia on
13-15 Feb 2023. Below is a summary of key details and dates from
6 matches
Mail list logo