Peering API
draft-ramseyer-grow-peering-api-06
Document | Type |
Replaced Internet-Draft
(grow WG)
Expired & archived
|
|
---|---|---|---|
Authors | Carlos Aguado , Matt Griswold , Jenny Ramseyer , Arturo L. Servin , Tom Strickx | ||
Last updated | 2024-12-06 (Latest revision 2024-11-04) | ||
Replaced by | draft-ietf-grow-peering-api | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-grow-peering-api | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
We propose an API standard for BGP Peering, also known as interdomain interconnection through global Internet Routing. This API offers a standard way to request public (settlement-free) peering, verify the status of a request or BGP session, and list potential connection locations. The API is backed by PeeringDB OIDC, the industry standard for peering authentication. We also propose future work to cover private peering, and alternative authentication methods.
Authors
Carlos Aguado
Matt Griswold
Jenny Ramseyer
Arturo L. Servin
Tom Strickx
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)