From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 88E003B2A4; Tue, 27 Feb 2024 03:02:48 -0500 (EST) Received: by mail-yb1-xb2c.google.com with SMTP id 3f1490d57ef6-dc23bf7e5aaso4006780276.0; Tue, 27 Feb 2024 00:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709020968; x=1709625768; darn=lists.bufferbloat.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pVJFnJZlEtzjNC/3z8NMriNyWP4HepQRyOt7y1N0nzk=; b=Fu5Q1kU3CzzRZPg3ppxfwvQwRlk4LN4eQhp/0FhtAjBdVzJzp0kpLT03RVK2vy7Ckq 4ZLqvEHa3I00Ym0IK6grnViJBOf8w0mQdSG7+MejJqbw25HgQwIqounbCX4zxbZgkDuy 8Cqwh7D6fM/P8e28GSZARXO8R0VNjdIa/38RtqVwkc/ii28Uf1pblhZWQsE7hek3uRq+ VjXdBzbKTHRQdHKlHvEuhM9V+I/Am0jNq6Lco3bhMUGj52KWAhcYmwzd1YOo/Y6IClNf mgg671F/PdOBlEmrpdCtROa8Fi78Pd7BYAJya1Zsne/R/4jW6t6tAWhHIhUp2f5GiDyS 1xJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709020968; x=1709625768; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pVJFnJZlEtzjNC/3z8NMriNyWP4HepQRyOt7y1N0nzk=; b=BxDuOJtz9b4auFQ686mCI9J3NA2jGdJAMsxTYjfL1pDhJIEy2POoADi5W3oVLxDyzz n9ykxt+4p7D6wSNAH5pZwZBgM2xaQWPbAy8XOJhA+qmy5FaHgrmvblu/vC/VLPtvcPHA Tu0yS3/VUL9lauKqp4J0prGJlgOCPXIL7+Kfd7LDXE6AUA5I8c/5IgTWgktBdtX0uDQq 0BHl4mpGjka1U3b55kIDrzvtcBonCX1q+0FdAaTXyZLbU5XfZdyDD9b6+cDU/ClsC3ov ZBNzJZKuNOegbmUaKnSojpP7ZqfvomcFSsEecHG56a2Yt2BDdcJitqBzoCZL1dIsGHlx V3Sg== X-Forwarded-Encrypted: i=1; AJvYcCWdtVDh37Q+R6eL67rRhOBSOFXqGm9Zak7qG1EaA5R928gIMBevCObsb5C9P1iJ4smzTXB5AwTt0TIxC/sG23ID6Kq5ntvHEHNucQgL3fk= X-Gm-Message-State: AOJu0Ywzes9ky8seS3NYQasGMklDdR/+sU71GIIuAbojrq423l8DBB8R 95AHACJQC2/8dgPo+M2ymu7VAAXyXrSpj4Ses4JNWecbv1XboHw3ZX7A5otkcXOWC0pFBXB6Lgq aXDXVkdRwxd4Jgq2di3DSVTuknhTQVjI1AZFsgA== X-Google-Smtp-Source: AGHT+IGQJvSs6h3gDGjEyUtL4UzQ0b9O3eYVy+2JYtVZ8ti7VOa+WMt8x5dI9QLfLTJb5Ycev8JM8CWAAWAjJ69NWM0= X-Received: by 2002:a25:1457:0:b0:dcd:990a:c02a with SMTP id 84-20020a251457000000b00dcd990ac02amr1179374ybu.63.1709020967253; Tue, 27 Feb 2024 00:02:47 -0800 (PST) Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Tue, 27 Feb 2024 00:02:45 -0800 Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Tue, 27 Feb 2024 00:02:43 -0800 MIME-Version: 1.0 (Mimestream 1.2.6) References: In-Reply-To: From: Fearghas Mckay Message-ID: To: =?UTF-8?Q?Network_Neutrality_is_back=21_Let=C2=B4s_make_the_technical_asp?= =?UTF-8?Q?ects_heard_this_time=21?= Cc: Dave Taht , Starlink Content-Type: multipart/alternative; boundary="000000000000aabe8306125873bd" X-Mailman-Approved-At: Mon, 29 Apr 2024 17:35:04 -0400 Subject: Re: [Starlink] [NNagain] starlink IXP peering progress X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Tue, 27 Feb 2024 08:02:48 -0000 X-Original-Date: Tue, 27 Feb 2024 00:02:45 -0800 X-List-Received-Date: Tue, 27 Feb 2024 08:02:48 -0000 --000000000000aabe8306125873bd Content-Type: text/plain; charset="UTF-8" On 27 Feb 2024 at 14:51:29, Dave Taht via Nnagain < nnagain@lists.bufferbloat.net> wrote: > One of the things I learned today was that starlink has published an > extensive guide as to how existing BGP AS holders can peer with them > to get better service. I am curious if there is a way to see how many > have peered already, how many they could actually peer with?, and > progress over time since inception.... is there a tool for that? > > https://starlink-enterprise-guide.readme.io/docs/peering-with-starlink This is just standard BGP peering over route servers. It is not BGP over your starlink satellite service, you need to have connectivity to an appropriate IXP. It tells you to use Peering dB to find the appropriate locations - https://www.peeringdb.com/net/18747 So if you connect to one of the IXPs linked on that page you can peer with Starlink, just like another BGP network that does public peering over routes. The IXPs may have local data on who has been peering over the route servers. f --000000000000aabe8306125873bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On 27 Feb 2024 at 14:51:29, Dave = Taht via Nnagain <nnaga= in@lists.bufferbloat.net> wrote:
One of the things I learned today was that starlink has published a= n
extensive guide as to how existing BGP AS holders can peer with themto get better service. I am curious if there is a way to see how many
= have peered already, how many they could actually peer with?, and
progre= ss over time since inception.... is there a tool for that?

https://starlink-enterprise-guide.readme.io/docs/peering-with-starlink


This is just standard BGP peering over route servers= . It is not BGP over your starlink satellite service, you need to have conn= ectivity to an appropriate IXP.=C2=A0

It tells you to use Peering dB to find the appropriate location= s -=C2=A0https://www.peerin= gdb.com/net/18747

So i= f you connect to one of the IXPs linked on that page you can peer with Star= link, just like another BGP network that does public peering over routes.= =C2=A0

The IXPs may have l= ocal data on who has been peering over the route servers.=C2=A0

f
--000000000000aabe8306125873bd--