The IDR Working Group, which standardizes BGP in the IETF, is doing last call for the linklocal capability feature.

IPv6-linklocal-only peering is a popular mechanism for some operators who want to avoid uniquely numbering links in network scenarios where the number is irrelevant. This is especially the case for things that are otherwise point to point links. Some people like these in data center use cases!

However, linklocal-only peering has been underspecified and buggy between implementations. This draft fixes that.

Please consider reviewing the draft and providing feedback to the working group mailing list.[1] This can be "yeah, it's ready to go" or "I see a problem here"...

https://datatracker.ietf.org/doc/draft-ietf-idr-linklocal-capability/

#bgp #ietf

Link-Local Next Hop Capability for BGP

To support IPv6 [RFC4291] reachability, BGP [RFC4271] relies on the Multiprotocol Extensions as defined in [RFC4760]. [RFC2545] defines the structure of IPv6 next hops. These IPv6 next hops may contain a Global IPv6 address, and optionally can contain an IPv6 Link-Local address when the BGP peer is directly attached and shares a common subnet with the IPv6 Global address. This document updates [RFC2545] to clarify the encoding of the BGP next hop when the advertising system is directly attached and only an IPv6 Link-Local address is available. A new BGP Capability [RFC5492] is defined to signal support for this updated encoding. This clarification applies specifically to IPv6 Link-Local addresses and does not pertain to IPv4 Link-Local addresses as defined in [RFC3927].

IETF Datatracker
Partage, veille et lecture : Let’s Learn About BGP https://kmcd.dev/posts/bgp-kmcd-dev/ (et son petit site https://bgp.kmcd.dev/ ) #BGP #réseau #Shaarli https://dryusdan.link/shaare/xwcHZQ
Let's Learn About BGP

How a live BGP map evolved into an interactive explainer on internet routing.

kmcd.dev
🪧 Let's Learn About BGP: How a live BGP map evolved into an interactive explainer on internet routing.
https://kmcd.dev/posts/bgp-kmcd-dev/
#Dataviz #Internet-map #Networking #Bgp #Rust #Go #Grpc #Protobuf #Education
Let's Learn About BGP

How a live BGP map evolved into an interactive explainer on internet routing.

kmcd.dev
🪧 Let's Learn About BGP: How a live BGP map evolved into an interactive explainer on internet routing.
https://kmcd.dev/posts/bgp-kmcd-dev/
#Dataviz #Internet-map #Networking #Bgp #Rust #Go #Grpc #Protobuf #Education
Let's Learn About BGP

How a live BGP map evolved into an interactive explainer on internet routing.

kmcd.dev

So far from the technical perspective I like #hostiko the most.

They are so far the only (European) cloud provider that happily and readily offered to do a private #ASN peering between the VPS servers and their infra.

#BGP #peering

The Fast Way to Sweden – BGP Routing Experiments

핀란드 헬싱키에서 스톡홀름 VPS로의 네트워크 지연 시간을 줄이기 위한 BGP 라우팅 실험을 진행했다. 기존 경로들이 지리적으로 비효율적인 경로를 거치고 있어, BGP 커뮤니티를 활용해 트래픽이 스톡홀름 내에서만 흐르도록 제한하는 방식을 시도했다. 이를 통해 ISP 간 피어링과 업스트림 경로를 제어하여 지연 시간을 개선할 가능성을 탐색했다. 본 실험은 AI 인프라 및 네트워크 최적화에 관심 있는 개발자에게 유용한 사례다.

https://alastairbarber.com/Fast-Way-to-Sweden-Optimal-BGP-Prefix-Announcement/

#bgp #networking #routing #ipv6 #internetexchange

The Fast Way to Sweden - BGP Routing Experiments

Learning about selectively announcing prefixes with BGP to get traffic to its destination faster

Quick BGP fixing...

When using Arista, remember to check it before 😬

#NetworkEngineering #Network #Engineer #BGP #Arista #containerlab

If BGP Peering were like modern onlinedating; part 3:

"I am running an unfiltered network and I expect you to neither"

#peering #bgp #sarcasm

Anybody successfully #peering with #iEdon (#AS4242422189) on #DN42? Somehow my announcements get filtered by them while Kioubit accepts the exact same announcements without a problem.

#BGP

https://lg.iedon.net/detail/nl-ams/DN42_4242420323_dn1y5tsgz0

Два Kubernetes-кластера — одна сеть: объединяем через Mesh и межкластерный роутинг

Когда Kubernetes-кластеров становится больше одного, инфраструктура начинает жить по новым правилам. Один кластер развёрнут в основном датацентре, второй — в резервной площадке. Сложности начинаются в тот момент, когда этим кластерам нужно взаимодействовать друг с другом. Сервисы в одном кластере должны обращаться к сервисам в другом, приложениям требуется нормальная маршрутизация, а инженерам хочется управлять этим без набора временных решений вроде iptables и ручных DNS-записей. В качестве сетевого слоя будем использовать Calico , а для межкластерного взаимодействия сервисов — Istio . Первый даст маршрутизацию и связность, второй — discovery, балансировку и управление трафиком на уровне приложений.

https://habr.com/ru/companies/gnivc/articles/1026994/

#calico #bgp #istio #kubernetes

Два Kubernetes-кластера — одна сеть: объединяем через Mesh и межкластерный роутинг

Когда Kubernetes-кластеров становится больше одного, инфраструктура начинает жить по новым правилам. Один кластер развёрнут в основном датацентре, второй — в резервной площадке. Сложности начинаются в...

Хабр