| rfc9319v3.txt | rfc9319.txt | |||
|---|---|---|---|---|
| skipping to change at line 12 ¶ | skipping to change at line 12 ¶ | |||
| Internet Engineering Task Force (IETF) Y. Gilad | Internet Engineering Task Force (IETF) Y. Gilad | |||
| Request for Comments: 9319 Hebrew University of Jerusalem | Request for Comments: 9319 Hebrew University of Jerusalem | |||
| BCP: 185 S. Goldberg | BCP: 185 S. Goldberg | |||
| Category: Best Current Practice Boston University | Category: Best Current Practice Boston University | |||
| ISSN: 2070-1721 K. Sriram | ISSN: 2070-1721 K. Sriram | |||
| USA NIST | USA NIST | |||
| J. Snijders | J. Snijders | |||
| Fastly | Fastly | |||
| B. Maddison | B. Maddison | |||
| Workonline Communications | Workonline Communications | |||
| September 2022 | October 2022 | |||
| The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | The Use of maxLength in the Resource Public Key Infrastructure (RPKI) | |||
| Abstract | Abstract | |||
| This document recommends ways to reduce the forged-origin hijack | This document recommends ways to reduce the forged-origin hijack | |||
| attack surface by prudently limiting the set of IP prefixes that are | attack surface by prudently limiting the set of IP prefixes that are | |||
| included in a Route Origin Authorization (ROA). One recommendation | included in a Route Origin Authorization (ROA). One recommendation | |||
| is to avoid using the maxLength attribute in ROAs except in some | is to avoid using the maxLength attribute in ROAs except in some | |||
| specific cases. The recommendations complement and extend those in | specific cases. The recommendations complement and extend those in | |||
| End of changes. 1 change blocks. | ||||
| 1 lines changed or deleted | 1 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||