= le-fay.dn42

welcome to le-fay.dn42, AS4242421495.

[overview]
== overview

* ASN: 4242421495
* location: UK
* contact: ft.dn42@le-fay.org
* networks:
** fd5b:a83:b06b::/48
** 172.23.76.0/26

[peering]
== peering

i am accepting peerings in the UK & Ireland.
please see the link:nodes/[list of nodes] for information about nodes
accepting new peerings.
all nodes support multiprotocol BGP with extended next hop for IPv4 prefixes;
BGP itself is only supported over link-local IPv6 addresses.

peering requests with an excessively high rtt may be rejected to preserve
network quality.

to request a peering, please mail ft.dn42@le-fay.org and include:

* the node you want to peer with
* your DN42 ASN
* your Wireguard endpoint address, port, and public key
* your BGP link-local address
* whether you want IPv4 routes, IPv6 routes, or both
	(note that in any case, BGP peerings are always over IPv6 link local
	addresses)

[communities]
== BGP communities

routes advertised by AS4242421495 may have one or more of the following
communities attached:

[cols="2*"]
|===
|community | meaning

2+h| general
| 4242421495:1:1
| route origin: internal (AS4242421495)
| 4242421495:1:2 [.red]#*#
| route origin: external, Internet (DFZ)
| 4242421495:1:42
| route origin: external, DN42
| 4242421495:4:1 [.red]#*#
| internal route policy: export to Internet peers
| 4242421495:4:2 [.red]#*#
| internal route policy: export to internal peers only
| 4242421495:4:42
| internal route policy: export to DN42
| 4242421495:5:1
| aggregated route (internal route policy: do not install to FIB)

2+h| node-specific
| 4242421495:2:1
| route originated or received by rose
| 4242421495:2:2
| route originated or received by amaranth
| 4242421495:2:3
| route originated or received by ash
| 4242421495:2:4
| route originated or received by oak
| 4242421495:2:9
| route originated or received by willow

2+h| region-specific

| 4242421495:3:1
| route originated or received in UK region
| 4242421495:3:4
| route originated or received in Eden
|===

[.red]#*# - these communities should never be seen on DN42

the node-specific and region-specific communities are only attached when the
route is originated or received from an external peer.  for example, a route
tagged with 4242421495:2:1 was either received by rose from an external EBGP
peer, or was locally originated on that node.  therefore, any route should only
have a single node-specific and region-specific community.