RFC 3779: X.509 Extensions for IP Addresses and AS Identifiers

This document defines two X.509 v3 certificate extensions. The first binds a list of IP address blocks, or prefixes, to the subject of a certificate. The…

Read RFC 3779 on the RFC Editor

Incoming relationships (31 related RFCs)

Normatively referenced by — RFC 3971: SEcure Neighbor Discovery (SEND)
Normatively referenced by — RFC 6268: Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)
Normatively referenced by — RFC 6487: A Profile for X.509 PKIX Resource Certificates
Normatively referenced by — RFC 6811: BGP Prefix Origin Validation
Normatively referenced by — RFC 6488: Signed Object Template for the Resource Public Key Infrastructure (RPKI)
Normatively referenced by — RFC 6489: Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)
Normatively referenced by — RFC 6493: The Resource Public Key Infrastructure (RPKI) Ghostbusters Record
Normatively referenced by — RFC 6916: Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)
Normatively referenced by — RFC 6483: Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)
Normatively referenced by — RFC 8209: A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests
Normatively referenced by — RFC 8211: Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)
Normatively referenced by — RFC 9632: Finding and Using Geofeed Data
Normatively referenced by — RFC 6492: A Protocol for Provisioning Resource Certificates
Normatively referenced by — RFC 8360: Resource Public Key Infrastructure (RPKI) Validation Reconsidered
Normatively referenced by — RFC 9092: Finding and Using Geofeed Data
Normatively referenced by — RFC 9582: A Profile for Route Origin Authorizations (ROAs)
Normatively referenced by — RFC 8897: Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties
Normatively referenced by — RFC 9323: A Profile for RPKI Signed Checklists (RSCs)
Normatively referenced by — RFC 9455: Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes
Normatively referenced by — RFC 9977: Publishing End-Site Prefix Lengths
Informatively referenced by — RFC 6481: A Profile for Resource Certificate Repository Structure
Informatively referenced by — RFC 6486: Manifests for the Resource Public Key Infrastructure (RPKI)
Informatively referenced by — RFC 7299: Object Identifier Registry for the PKIX Working Group
Informatively referenced by — RFC 6472: Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP
Informatively referenced by — RFC 9286: Manifests for the Resource Public Key Infrastructure (RPKI)
Informatively referenced by — RFC 7132: Threat Model for BGP Path Security
Informatively referenced by — RFC 4945: The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2, and PKIX
Informatively referenced by — RFC 6907: Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying Parties
Informatively referenced by — RFC 8910: Captive-Portal Identification in DHCP and Router Advertisements (RAs)
Informatively referenced by — RFC 9774: Deprecation of AS_SET and AS_CONFED_SET in BGP
Informatively referenced by — RFC 9829: Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions