RFC 7720
E224045
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7720 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T2002405 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7720 Context triple: [Root Server System, documentedIn, RFC 7720]
-
A.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
B.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
C.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
D.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
E.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 7720 Target entity description: RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
-
A.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
B.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
C.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
D.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
E.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet Standard ⓘ |
| aimsTo |
ensure stable and reliable operation of the DNS root server system
ⓘ
provide clear protocol and deployment requirements for DNS root servers ⓘ |
| area |
Internet
ⓘ
linked to:
the internet
Operations and Management ⓘ |
| author |
George Michaelson
ⓘ
Joao Damas ⓘ John Abley ⓘ Matt Larson ⓘ Paul E. Vixie ⓘ Warren Kumari ⓘ |
| BCPNumber | BCP 40 ⓘ |
| category | Best Current Practice ⓘ |
| defines |
operational requirements for DNS Root Name Service
ⓘ
technical requirements for DNS Root Name Service ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn |
deployment requirements for DNS root servers
ⓘ
operational practices for DNS root servers ⓘ protocol requirements for DNS root servers ⓘ |
| hasNumber | 7720 ⓘ |
| identifier | RFC 7720 ⓘ |
| intendedFor |
DNS protocol designers
ⓘ
network operators ⓘ operators of DNS root name servers ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2870 ⓘ |
| publicationDate | December 2015 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| replaces | requirements specified in RFC 2870 ⓘ |
| specifies |
minimum set of DNS query types that root servers must support
ⓘ
operational best practices for DNS root server operators ⓘ requirements for DNSSEC support at DNS root servers ⓘ support for EDNS(0) by DNS root servers ⓘ use of IPv4 and IPv6 for DNS root servers ⓘ use of UDP and TCP transport for DNS root servers ⓘ |
| standardsTrack | yes ⓘ |
| status | Internet Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| subject |
DNS root name service
ⓘ
linked to:
Root Server System
DNS root server system ⓘ Domain Name System ⓘ |
| title | DNS Root Name Service Protocol and Deployment Requirements ⓘ |
| updates | RFC 2870 ⓘ |
| workingGroup |
DNS Operations Working Group
ⓘ
linked to:
IETF DNSOP
DNSOP ⓘ
linked to:
IETF DNSOP
|
| year | 2015 ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 7720 Description of subject: RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.