Skip to main content

Resource Public Key Infrastructure (RPKI) Origin Validation for BGP Export
RFC 8893

Revision differences

Document history

Date By Action
2020-10-20
Jenny Bui Posted related IPR disclosure Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 8893
2020-09-25
(System)
Received changes through RFC Editor sync (created alias RFC 8893, changed title to 'Resource Public Key Infrastructure (RPKI) Origin Validation for BGP Export', changed …
Received changes through RFC Editor sync (created alias RFC 8893, changed title to 'Resource Public Key Infrastructure (RPKI) Origin Validation for BGP Export', changed abstract to 'A BGP speaker may perform Resource Public Key Infrastructure (RPKI) origin validation not only on routes received from BGP neighbors and routes that are redistributed from other routing protocols, but also on routes it sends to BGP neighbors.  For egress policy, it is important that the classification use the 'effective origin AS' of the processed route, which may specifically be altered by the commonly available knobs, such as removing private ASes, confederation handling, and other modifications of the origin AS.  This document updates RFC 6811.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-09-25, changed IESG state to RFC Published, created updates relation between draft-ietf-sidrops-ov-egress and RFC 6811)
2020-09-25
(System) RFC published