A Profile for Traffic Origin Authorizations (TOAs)
draft-qin-sidrops-toa-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lancheng Qin , Ben Maddison , Dan Li | ||
| Last updated | 2025-06-25 | ||
| Replaced by | draft-qin-savnet-toa | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-qin-savnet-toa | |
| 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
This document defines a standard profile for Traffic Origin Authorizations (TOAs), a Cryptographic Message Syntax (CMS) protected content type for use with the Resource Public Key Infrastructure (RPKI). A TOA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate traffic using source IP addresses within the address block.
Authors
Lancheng Qin
Ben Maddison
Dan Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)