BGPsec Protocol Specification
The work
| Authors | M. Lepinski; K. Sriram |
|---|---|
| Editors | |
| Type | techreport |
| Year | 2017 |
| Also known as | anon2017bgpsec |
| Citekey | lepinski2017bgpsec |
Identifiers
| DOI | 10.17487/rfc8205 |
|---|---|
| OpenAlex | W2525730961 |
Access
| Landing page | https://doi.org/10.17487/rfc8205 |
|---|
From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.
Abstract
This document describes BGPsec, an extension to the Border Gateway Protocol (BGP) that provides security for the path of Autonomous Systems (ASes) through which a BGP UPDATE message passes. BGPsec is implemented via an optional non-transitive BGP path attribute that carries digital signatures produced by each AS that propagates the UPDATE message. The digital signatures provide confidence that every AS on the path of ASes listed in the UPDATE message has explicitly authorized the advertisement of the route.
A copy is held
pdf, 76.7 kB. Not published — it may be under copyright. The facts and links here are.
How it got here
| How it got here | agent via openalex |
|---|---|
| Added | 2026-09-26 10:12 UTC |
| Approved by | a person 2026-10-05 20:33 UTC |
Filed under
Cite it as
@techreport{lepinski2017bgpsec,
title = {BGPsec Protocol Specification},
author = {M. Lepinski and K. Sriram},
year = {2017},
doi = {10.17487/rfc8205},
}
This record lives at https://refs.drheap.org/lepinski2017bgpsec/ and will keep
doing so. It used to be called anon2017bgpsec, and those addresses still resolve to this one.