User Tools

Site Tools


peering-toolbox:manrs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
peering-toolbox:manrs [2022/08/18 21:54] – created philippeering-toolbox:manrs [2022/08/26 17:17] (current) philip
Line 1: Line 1:
 ====== MANRS ====== ====== MANRS ======
  
-The Mutually Agreed Norms for Routing Security, known as MANRS, is an industry initative supported by the Internet Society to improve routing hygiene on the global Internet.+The Mutually Agreed Norms for Routing Security, known as MANRS, is an industry initiative supported by the [[https://www.internetsociety.org|Internet Society]] to improve routing hygiene on the global Internet.
  
 The [[https://www.manrs.org|MANRS]] website has full information about what this initiative is all about. The [[https://www.manrs.org|MANRS]] website has full information about what this initiative is all about.
Line 10: Line 10:
   - coordination and collaboration between networks   - coordination and collaboration between networks
  
-[[route_origin_authorisation|Route Origin Authorisation]] and the information contained in the [[the_internet_routing_registry|Internet Routing Registry]] go a long way to helping solve the problem of incorrect routing information appearing on the global internet.+[[route_origin_authorisation|Route Origin Authorisation]] and the information contained in the [[the_internet_routing_registry|Internet Routing Registry]] go a long way to helping solve the problem of incorrect routing information appearing on the global internet. Implementation of EBGP filters on all EBGP sessions (as discussed in [[https://www.rfc-editor.org/rfc/rfc8212|RFC8212]]), by default, will also ensure that no operator using BGP will accidentally propagate routes without purposely creating filters to do so.
  
-Traffic with spoofed source addresses can be blocked, at origin, by network operators implementing anti-spoofing filters, as noted in the [[hardware#packet_filtering|Packet Filtering]] section discussing router hardware. Anti-spoofing filters can be even more efficiently implemented by using a technique known as [[https://bgp4all.com/pfs/_media/workshops/03-urpf.pdf|Unicast Reverse Path Forwarding]].+Traffic with spoofed source addresses can be blocked, at origin, by network operators implementing anti-spoofing filters, as noted in the [[hardware#packet_filtering|Packet Filtering]] section discussing router hardware. Anti-spoofing filters can be even more efficiently implemented by using a technique known as [[https://bgp4all.com/pfs/_media/workshops/03-urpf.pdf|Unicast Reverse Path Forwarding]] which is implemented in hardware on most access router platforms today.
  
-Coordination and Collaboration between networks is achieved at least by keeping contact information in [[the_peering_database|PeeringDB]] entries and [[the_internet_routing_registry|Internet Routing Registry]] objects up to date.+Coordination and Collaboration between networks is achieved by ensuring that each network has direct contact with their upstream or peer network's Network Operation's Centre (not Customer Support), and keeping contact information in [[the_peering_database|PeeringDB]] entries and [[the_internet_routing_registry|Internet Routing Registry]] objects up to date.
  
-[[:peering-toolbox/how-to-peer| Back to "What I need to Peer" page]]+[[:peering-toolbox/how-to-peer| Back to "What is required for Peering" page]]
peering-toolbox/manrs.1660823642.txt.gz · Last modified: 2022/08/18 21:54 by philip