Finally getting around to this project; alot of friends have mentioned / suggested the idea in the past as a project, but I've never had the means to complete it.

Now I do, so I figured better now than never!

Foreword

Explain:

a) Why?

b) What is BGP?

c) Why is BGP needed?

d) Why IPv6?

e) Financial Requirements

f) Other Requirements

Establish a relationship with your local RIR (Regional Internet Registry) ARIN

Explain:

a) RIRs (ARIN)

b) Prefixes

c) ORG (Organization)

d) ASN (Autonomous Systems Number) 

e) Routing Security (Brief, IRR, RPKI)

Design your Network Layout (Split up your prefixes into zones)

Explain:

a) Basic subnetting and CIDR

b) Zoning your CIDR subnets

c) Decide what you want now, because coming back to fix it later is either very difficult, or impossible

d) Leave room for testing subnets, and plan for growth with the remainder of your CIDR subnets 

Acquire a peering partner with IP transit services

Explain:

a) What is peering?

b) What is IP transit? 

Pick your BGP routing software / solution

Explain:

a) Options

• Bird
• PathVector
• Frr
• Hardware (Cisco, Juniper, etc.)

b) Drill down on PathVector + Bird

Announce your prefixes

Explain:

a) Announcing prefixes via upstream bgp peer (transit peer)

b) Verify prefixes are being announced properly via bgp.tools

c) Verify IRR + RPKI is properly setup

Determine your routing plan

Explain:

a) How are you going to route traffic from your bgp router to your hosts?

• Are they directly connected, or available to be connected?
• Can you digitally connect them? i.e. via Wireguard, or other site-to-site VPN solutions?

b) Explain vIXes and how they work.

c) Break down BGP over Wireguard

Routing traffic within your networks

Explain:

a) Install a default route on your router via BGP (Setup BGP on your internal network router)

b) Discuss the pitfalls of asymmetric routing, and how it will create issues.

c) Setup policy based routing

d) Further subdivide prefixes at sites if needed