<gh_stars>1-10

@online{hares_border_2006,
  title = {A {{Border Gateway Protocol}} 4 ({{BGP}}-4)},
  author = {<NAME> and Rekhter, Yakov and <NAME>},
  date = {2006-01},
  url = {https://tools.ietf.org/html/rfc4271},
  urldate = {2020-06-11},
  file = {/home/freethink/Zotero/storage/DM7B4KW4/rfc4271.html},
  langid = {english}
}

@online{internet_society_manrs_2019,
  title = {{{MANRS}}},
  author = {{Internet Society}},
  date = {2019},
  url = {https://www.manrs.org/},
  urldate = {2020-06-11},
  abstract = {Mutually Agreed Norms for Routing Security},
  file = {/home/freethink/Zotero/storage/SHZE4CHG/www.manrs.org.html},
  langid = {american}
}

@online{manrs_implementation_2017,
  title = {Implementation {{Guide}}},
  author = {{MANRS}},
  date = {2017-04-26T17:41:23+00:00},
  journaltitle = {MANRS},
  url = {https://www.manrs.org/isps/guide/},
  urldate = {2020-06-11},
  abstract = {To assist you in implementing the steps necessary to be compliant with the Mutually Agreed Norms for Routing Security, the community of MANRS participants developed an~Implementation Guide.~This do…},
  file = {/home/freethink/Zotero/storage/TXM9QSAF/guide.html},
  langid = {american}
}

@online{red_hat_2211_nodate,
  title = {2.2.11.~{{Reverse Path Forwarding Red Hat Enterprise Linux}} 6},
  author = {{Red Hat}},
  url = {https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/security_guide/sect-security_guide-server_security-reverse_path_forwarding},
  urldate = {2020-06-13},
  file = {/home/freethink/Zotero/storage/N3T3LCST/sect-security_guide-server_security-reverse_path_forwarding.html}
}

@online{savola_ingress_2004,
  title = {Ingress {{Filtering}} for {{Multihomed Networks}}},
  author = {<NAME> and <NAME>},
  date = {2004-03},
  url = {https://tools.ietf.org/html/rfc3704},
  urldate = {2020-06-11},
  file = {/home/freethink/Zotero/storage/LG6FZQNE/rfc3704.html},
  langid = {english}
}

@online{serverbuddiescom_disable_nodate,
  title = {Disable {{ICMP Redirect}} and {{Enable IP Spoofing Protection}}},
  author = {{serverbuddies.com}},
  url = {http://blog.serverbuddies.com/disable-icmp-redirect-and-enable-ip-spoofing-protection/},
  urldate = {2020-06-13},
  abstract = {Linux Support Blog, Disable ICMP Redirect and Enable IP Spoofing Protection},
  file = {/home/freethink/Zotero/storage/MGMHIFXC/disable-icmp-redirect-and-enable-ip-spoofing-protection.html}
}

@online{slashrootin_linux_2013,
  title = {Linux Kernel Rp\_filter Settings ({{Reverse}} Path Filtering )},
  author = {{slashroot.in}},
  date = {2013-02-28},
  journaltitle = {slashroot.in},
  url = {https://www.slashroot.in/linux-kernel-rpfilter-settings-reverse-path-filtering},
  urldate = {2020-06-13},
  abstract = {What is reverse path filtering and how to configure rp\_filter in linux: Reduce and minimize spoofing attempts with the help of rp\_filter in linux.},
  file = {/home/freethink/Zotero/storage/I2XRZAGH/linux-kernel-rpfilter-settings-reverse-path-filtering.html},
  langid = {english}
}

@online{villamizar_routing_1999,
  title = {Routing {{Policy Specification Language}} ({{RPSL}})},
  author = {<NAME> <NAME>, Marten and Gerich, Elise and Alaettinoglu, Cengiz and <NAME>},
  date = {1999-06},
  url = {https://tools.ietf.org/html/rfc2622},
  urldate = {2020-06-11},
  file = {/home/freethink/Zotero/storage/6I5ZUPP2/rfc2622.html},
  langid = {english}
}

@inreference{wikipedia_autonomous_2020,
  title = {Autonomous System ({{Internet}})},
  booktitle = {Wikipedia},
  author = {{Wikipedia}},
  date = {2020-05-22T19:02:28Z},
  url = {https://en.wikipedia.org/w/index.php?title=Autonomous_system_(Internet)&oldid=958253122},
  urldate = {2020-06-11},
  abstract = {An autonomous system (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain that presents a common, clearly defined routing policy to the internet.Originally the definition required control by a single entity, typically an Internet service provider (ISP) or a very large organization with independent connections to multiple networks, that adhered to a single and clearly defined routing policy, as originally defined in RFC 1771. The newer definition in RFC 1930 came into use because multiple organizations can run Border Gateway Protocol (BGP) using private AS numbers to an ISP that connects all those organizations to the internet. Even though there may be multiple autonomous systems supported by the ISP, the internet only sees the routing policy of the ISP. That ISP must have an officially registered autonomous system number (ASN).
A unique ASN is allocated to each AS for use in BGP routing. ASNs are important because the ASN uniquely identifies each network on the Internet.
Until 2007, AS numbers were defined as 16-bit integers, which allowed for a maximum of 65,536 assignments.  RFC 4893 introduced 32-bit AS numbers, which the Internet Assigned Numbers Authority (IANA) has begun to allocate to regional Internet registry (RIRs), although this proposed standard has now been replaced by RFC 6793. These numbers are written preferably as simple integers (in a notation sometimes referred to as "asplain") ranging from 0 to 4,294,967,295 (hexadecimal 0xFFFF FFFF), or in the form called "asdot" which looks like x.y, where x and y are 16-bit numbers. Numbers of the form 0.y are exactly the old 16-bit AS numbers. The accepted textual representation of autonomous system numbers is defined in RFC 5396 as "asplain". The special 16-bit ASN 23456 ("AS\_TRANS") was assigned by IANA as a placeholder for 32-bit ASN values for the case when 32-bit-ASN capable routers ("new BGP speakers") send BGP messages to routers with older BGP software ("old BGP speakers") which do not understand the new 32-bit ASNs.The first and last ASNs of the original 16-bit integers (0 and 65,535) and the last ASN of the 32-bit numbers (4,294,967,295) are reserved and should not be used by operators. ASNs 64,496 to 64,511 of the original 16-bit range and 65,536 to 65,551 of the 32-bit range are reserved for use in documentation by RFC 5398. ASNs 64,512 to 65,534 of the original 16-bit AS range, and 4,200,000,000 to 4,294,967,294 of the 32-bit range are reserved for Private Use by RFC 6996, meaning they can be used internally but should not be announced to the global Internet. All other ASNs are subject to assignment by IANA.
The number of unique autonomous networks in the routing system of the Internet exceeded 5,000 in 1999, 30,000 in late 2008, 35,000 in mid-2010, 42,000 in late 2012, 54,000 in mid-2016 and 60,000 in early 2018.The number of allocated ASNs exceeded 92,000 as of August 2019.},
  file = {/home/freethink/Zotero/storage/RA7FJ6BP/index.html},
  langid = {english}
}

@inreference{wikipedia_bogon_2020,
  title = {Bogon Filtering},
  booktitle = {Wikipedia},
  author = {{Wikipedia}},
  date = {2020-05-16T17:12:35Z},
  url = {https://en.wikipedia.org/w/index.php?title=Bogon_filtering&oldid=957033830},
  urldate = {2020-06-11},
  abstract = {Bogon filtering is the practice of filtering bogons, which are bogus (fake) IP addresses of a computer network. Bogons include IP packets on the public Internet that contain addresses that are not in any range allocated or delegated by the Internet Assigned Numbers Authority (IANA) or a delegated regional Internet registry (RIR) and allowed for public Internet use. The areas of unallocated address space are called the bogon space.
Bogons also include reserved private address and link-local address ranges, such as those in 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, and 169.254.0.0/16, which are reserved for private networks, sometimes also known as Martian packets.
Many ISPs and end-user firewalls filter and block bogons, because they have no legitimate use, and usually are the result of accidental or malicious misconfiguration. Bogons can be filtered by using router access-control lists (ACLs), or by BGP blackholing.
IP addresses that are currently in the bogon space may not be bogons at a later date because IANA and other registries frequently assign new address space to ISPs. Announcements of new assignments are often published on network operators' mailing lists (such as NANOG) to ensure that operators have a chance to remove bogon filtering for addresses that have become legitimate.
For example, addresses in 172.16.31.10/8 were not allocated prior to August 2010, but are now used by APNIC. As time goes on, the IPv4 address exhaustion will mean there are fewer and fewer IPv4 bogons.
IANA maintains a list of allocated and reserved IPv4 netblocks.As of November 2011, the IETF recommends that since there are no longer any unallocated IPv4 /8s, bogon filters based on registration status should be removed.
However, bogon filters still need to check for Martians.},
  file = {/home/freethink/Zotero/storage/6HPI44VU/index.html},
  langid = {english}
}

@inreference{wikipedia_border_2020-1,
  title = {Border {{Gateway Protocol}}},
  booktitle = {Wikipedia},
  author = {{Wikipedia}},
  date = {2020-05-22T18:46:52Z},
  url = {https://en.wikipedia.org/w/index.php?title=Border_Gateway_Protocol&oldid=958250881},
  urldate = {2020-06-11},
  abstract = {Border Gateway Protocol (BGP) is a standardized exterior gateway protocol designed to exchange routing and reachability information among autonomous systems (AS) on the Internet. BGP is classified as a path-vector routing protocol, and it makes routing decisions based on paths, network policies, or rule-sets configured by a network administrator.
BGP may be used for routing within an autonomous system. In this application it is referred to as Interior Border Gateway Protocol, Internal BGP, or iBGP. In contrast, the Internet application of the protocol may be referred to as Exterior Border Gateway Protocol, External BGP, or eBGP.},
  file = {/home/freethink/Zotero/storage/DTCL97QB/index.html},
  langid = {english}
}


