A Profile for Traffic Origin Authorizations (TOAs)
draft-qin-savnet-toa-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Lancheng Qin , Ben Maddison , Dan Li , Igor Lubashev | ||
| Last updated | 2026-08-02 (Latest revision 2026-01-29) | ||
| Replaces | draft-qin-sidrops-toa | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Igor Lubashev
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)