References to draft-daigle-rfc954bis
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
|
draft-dulaunoy-dnsop-passive-dns-cof
As rfc3912 |
Passive DNS - Common Output Format
References Referenced by |
normatively references | ||
|
draft-ietf-opsawg-9092-update
As rfc3912 |
Finding and Using Geofeed Data
References Referenced by |
Proposed Standard | informatively references | |
|
draft-ramseyer-grow-peering-api
As rfc3912 |
Peering API
References Referenced by |
informatively references | ||
|
draft-rosenberg-mimi-discovery-reqs
As rfc3912 |
MIMI Discovery Requirements and Considerations
References Referenced by |
informatively references | ||
|
RFC 3981
As rfc3912 |
IRIS: The Internet Registry Information Service (IRIS) Core Protocol
References Referenced by |
Proposed Standard | informatively references | |
|
RFC 4690
As rfc3912 |
Review and Recommendations for Internationalized Domain Names (IDNs)
References Referenced by |
Informational | informatively references | |
|
RFC 5198
As rfc3912 |
Unicode Format for Network Interchange
References Referenced by |
Proposed Standard | informatively references | |
|
RFC 6650
As rfc3912 |
Creation and Use of Email Feedback Reports: An Applicability Statement for the Abuse Reporting Format (ARF)
References Referenced by |
Proposed Standard | informatively references | |
|
RFC 7020
As rfc3912 |
The Internet Numbers Registry System
References Referenced by |
Informational | informatively references | |
|
RFC 7480
As rfc3912 |
HTTP Usage in the Registration Data Access Protocol (RDAP)
References Referenced by |
Internet Standard | informatively references | |
|
RFC 7481
As rfc3912 |
Security Services for the Registration Data Access Protocol (RDAP)
References Referenced by |
Internet Standard | informatively references | |
|
RFC 7482
As rfc3912 |
Registration Data Access Protocol (RDAP) Query Format
References Referenced by |
Proposed Standard | informatively references | |
|
RFC 7483
As rfc3912 |
JSON Responses for the Registration Data Access Protocol (RDAP)
References Referenced by |
Proposed Standard | informatively references | |
|
RFC 7485
As rfc3912 |
Inventory and Analysis of WHOIS Registration Objects
References Referenced by |
Informational | informatively references | |
|
RFC 7719
As rfc3912 |
DNS Terminology
References Referenced by |
Informational | informatively references | |
|
RFC 8396
As rfc3912 |
Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers (MODERN): Problem Statement, Use Cases, and Framework
References Referenced by |
Informational | informatively references | |
|
RFC 8499
As rfc3912 |
DNS Terminology
References Referenced by |
Best Current Practice | informatively references | |
|
RFC 8805
As rfc3912 |
A Format for Self-Published IP Geolocation Feeds
References Referenced by |
Informational | informatively references | |
|
RFC 9022
As rfc3912 |
Domain Name Registration Data (DNRD) Objects Mapping
References Referenced by |
Proposed Standard | informatively references | |
|
RFC 9082
As rfc3912 |
Registration Data Access Protocol (RDAP) Query Format
References Referenced by |
Internet Standard | informatively references | |
|
RFC 9083
As rfc3912 |
JSON Responses for the Registration Data Access Protocol (RDAP)
References Referenced by |
Internet Standard | informatively references | |
|
RFC 9092
As rfc3912 |
Finding and Using Geofeed Data
References Referenced by |
Proposed Standard | informatively references | |
|
RFC 9255
As rfc3912 |
The 'I' in RPKI Does Not Stand for Identity
References Referenced by |
Proposed Standard | informatively references |