%% You should probably cite draft-ietf-sidr-pfx-validate instead of this I-D. @techreport{pmohapat-sidr-pfx-validate-07, number = {draft-pmohapat-sidr-pfx-validate-07}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-pmohapat-sidr-pfx-validate/07/}, author = {Prodosh Mohapatra and John Scudder and David Ward and Randy Bush and Rob Austein}, title = {{BGP Prefix Origin Validation}}, pagetotal = 11, year = 2010, month = apr, day = 29, abstract = {A BGP route associates an address prefix with a set of autonomous systems (AS) that identify the interdomain path the prefix has traversed in the form of BGP announcements. This set is represented as the AS\_PATH attribute in BGP and starts with the AS that originated the prefix. To help reduce well-known threats against BGP including prefix mis-announcing and monkey-in-the-middle attacks, one of the security requirements is the ability to validate the origination AS of BGP routes. More specifically, one needs to validate that the AS number claiming to originate an address prefix (as derived from the AS\_PATH attribute of the BGP route) is in fact authorized by the prefix holder to do so. This document describes a simple validation mechanism to partially satisfy this requirement.}, }